Osterman Research WHITE PAPER O - Datto

OOsterman Research

WHITE PAPER

White Paper by Osterman Research Published September 2020 Sponsored by Backupify

Migration to Microsoft 365: A Step-by-Step Guide

©2020 Osterman Research, Inc. 1


Executive Summary The migration of an organization’s email, archiving or other systems to Microsoft 365 is not for the faint of heart. There are several important decisions to make before migrating to a new platform, and the migration process itself requires very careful planning and execution over weeks or months in order to avoid chain-of-custody problems, corrupted data, loss of sensitive data, violation of privacy statutes, and ensuring a minimal impact on employees’ ability to do their work. There is a sequence of activities that must be planned, agreed upon by all stakeholders, and executed properly in order for the migration to be successful. Moreover, a migration process may include use of a variety of third-party products and services that can make the process simpler, faster and easier while decreasing the risk of human error during the migration. KEY TAKEAWAYS There are a number of important steps that must take place for a successful migration to Microsoft 365 or any other platform: • Decision makers must determine how Microsoft 365 or the new platform will be

used.

• Because organizations can choose any of a variety of plans under Microsoft 365, decision makers must establish the specific plans that will be used.

• The specific limitations of Microsoft 365 and how they will impact current

workflows, work practices, corporate culture, etc. will need to be seriously considered prior to the migration.

• Decision makers must determine a number of things before the migration can

begin, such as what content needs to be migrated, if there is adequate bandwidth available in all of the organization’s locations, whether or not there is corrupted data in the data to be migrated, and whatever dependencies might exist within legacy systems, among many other decisions.

• Ensure that in-house staff have the adequate skill sets to complete the migration

properly, or ensure that consultants, vendors, etc. will be able to fill the gaps.

• Make sure that decision makers understand compliance requirements as they relate to the migrated data.

• Develop a detailed and thorough plan for the migration.

• Ensure that all data types can be migrated successfully without losing chain-of-

custody, violating privacy obligations, or otherwise corrupting data.

• Properly research all of the available third-party tools that will assist both in the migration effort and following deployment of the new platform as a production system.

ABOUT THIS WHITE PAPER This white paper was sponsored by Backupify; information about the company is provided at the end of this paper.

Issues to Consider for a Migration There are a variety of reasons that organizations will migrate to a new platform, although, based on an Osterman Research survey, the most common reasons are: • Improving cyber security

Properly research all of the available third-party tools.



• Improving organizational communications • Managing corporate records • Improving user productivity • Reduce the cost of or streamlining IT operations • Gaining certainty over costs • Improving how data chain-of-custody is managed • The need to respond to a regulatory mandate

MIGRATION IS A COMPLEX PROCESS Almost every organization is up against a significant planning exercise when evaluating the shift to any new communication, collaboration or archiving platform. This is because of the impact of a migration on existing business processes, and their current and planned on-premises or cloud infrastructure, among other factors. There are lots of important decisions to make while planning the migration, including how to achieve value from doing so, the best approach to take, whether to use third parties, and the selection of third-party migration tools. While the most difficult parts of a migration will vary depending on the organization, its experience with migrations in the past, the technical expertise of its staff, etc., an Osterman Research survey found that these are the most difficult parts of a migration project: • Ensuring that all links and access to all shared resources continue to work for all

of the sources and target users. • Managing co-existence of email during the migration process.

• Educating and supporting users during the migration.

• Pre-migration planning.

• Configuring the migration solution.

• Organizing the groups to migrate first.

• Managing multiple email domains during the migration process.

• Tracking the process of the project. HAVING THE RIGHT TOOLS IS KEY Migration itself requires the appropriate mindset, the right approach, and a set of skills, tools, and experiences that are not always available in an organization’s IT department. Further, some firms migrating their email, archive and other systems have discovered that these skills are lacking even among some consultants and other third parties. However, getting it right is absolutely essential: If the migration process doesn’t work properly, there can be a number of consequences, including employees not being able to access email, their calendar or tasks; assistants and other proxies won’t be able to manage other calendars; and chain-of-custody for information can be lost, making it useless in legal matters or to satisfy a regulatory audit. BACKUP IS AN ESSENTIAL ELEMENT The best practice “3-2-1 Rule” (three copies of data, two on different platforms/media, one in a remote location) has been the norm of data protection for decades. However, native capabilities to protect data within Microsoft 365 employ the platform itself to provide data protection, which is not in keeping with the 3-2-1 Rule. As a result, the use of an external service or platform to protect Microsoft 365 data is much more in line with best practices – and is recommended by Microsoft itself in its service agreement. We discuss more about backup later in this paper.

Native capabilities to protect data within Microsoft 365 employ the platform itself to provide data protection, which is not in keeping with the 3-2-1 Rule.



A Step-by-Step Guide to Migration While there are a number of methods that can be used to migrate to a new messaging and collaboration platform, such as Microsoft 365, Osterman Research recommends the following approach: STEP 1: DETERMINE HOW MICROSOFT 365 WILL BE USED Microsoft 365 provides a growing array of capabilities for enabling communication, collaboration, and compliance. A key, initial task to complete in evaluating the shift to the platform is determining how the organization will make use of the capabilities on offer. For example, will specific capabilities from Microsoft 365 be used, or will the entire suite of capabilities be employed? Will a hybrid approach of cloud-based and on-premises services be used, or will everything be delivered via the cloud? If a hybrid approach is used, will it be for a definite period or be continued indefinitely? How will business value be derived from Microsoft 365 and/or the new hybrid deployment? In addition to deciding how to use Microsoft 365, it’s essential to understand if there are competing or complementary IT initiatives being undertaken within the organization that could impact the scope or timeline for a migration to Microsoft 365, such as a refresh of end-user devices or deployment of mobile devices. Current litigation or in-progress evaluations of possible acquisition targets could also impact the ability to move particular mailboxes to Microsoft 365 and the organization’s ability to migrate their email archives. STEP 2: DETERMINE IF MICROSOFT 365 WILL BE

“RIGHTSIZED” One of the fundamental advantages of Microsoft 365 is that Microsoft offers a number of SKUs for different capability levels and industries. For example, Plan E3 offers fewer capabilities than Plan E5, but at significantly lower cost. Plans can generally be mixed and matched to drive down the cost of Microsoft 365 – even if third-party capabilities are added, the cost can often be less than by going with the “full meal deal” for all employees. Among the considerations here to keep in mind: • An organization that will want to use a hybrid configuration between on-premises

servers and Microsoft 365 should select a plan that supports Azure Active Directory to enable administration tasks and seamless identity management between the two environments.

• Organizations with a variable number of staff over the course of a year might

choose to forego the less expensive Microsoft 365 plans that require an annual commitment and instead sign up for a plan that requires only a monthly commitment. This allows an organization to optimize its cost commitment to Microsoft, but does require active management to achieve.

• Organizations with a global footprint or strict data sovereignty requirements need to decide between a single tenant or the use of multiple tenants. While an organization can set up multiple, cooperative tenants to comply with data sovereignty and address other practical issues, a multi-tenant approach comes with added complexities.

• While most plans include the right to install the latest version of Microsoft applications on computers and mobile devices, some applications are excluded from this right.

STEP 3: UNDERSTAND THE LIMITATIONS IN MICROSOFT 365 Every platform has limitations and Microsoft 365 is no exception. Some of these limitations might cause issues during migration, while others create ongoing issues afterwards. Some of these limitations include maximum attachment sizes, blocked file types, migration throttling, the default and maximum retention period for deleted

Every platform has limitations and Microsoft 365 is no exception.



items, the length of file names for upload to SharePoint Online or OneDrive for Business, or unsupported characters in file names. Most of these issues can be mitigated, but they first have to be identified. It is also important to ensure that all data is backed up prior to the migration, and that backup capabilities are in place as the initial set of content enters Microsoft 365. It’s important to note that even Microsoft recommends that “you should have a regular backup plan1”, clearly stating that a third-party solution is needed since Microsoft does not intend to provide a reliable and complete backup of your data in all data-loss scenarios.

Following migration, issues that can arise include Microsoft’s approach to anti-malware and anti-phishing attacks, compliance and e-Discovery, and the inclusion of archived email in the same system as day-to-day transactional email. Many of the issues in this category can be mitigated, usually by embracing third-party tools that offer organizations more design control. STEP 4: A PRE-MIGRATION CHECKLIST A smooth migration to Microsoft 365 or another platform can be reasonably straightforward after all of the planning work has been accomplished. In fact, most organizations will (and probably should) spend more time planning their migration than actually accomplishing it. Here are the important tasks to consider in developing a plan for migration: • Determine if all existing content needs to be migrated

Some organizations will choose not to migrate all content because the cost and complexity is simply not worth migrating it, particularly for content with a fairly short life span. As part of the early stages of a migration, stakeholders should determine what content should and should not be migrated to the new platform.

• Check bandwidth availability

A very common migration effort today is migrating from on-premises email to cloud-based email (usually Microsoft 365), or from on-premises archiving to a cloud-based archiving solution. Migrating to a new email, collaboration or archiving solution is likely to be a bandwidth-intensive task in because hundreds of gigabytes or even terabytes of data are shifted from on-premises servers to the cloud. Migration planners must check that there is adequate bandwidth available for the migration and should explore alternatives for moving current and historical data without using an Internet connection. Microsoft offers the option of delivering data on hard disks directly to Microsoft for upload into the customer’s account at the data center, and some third-party migration tools support faster upload to Microsoft 365 by moving data into Azure first. Amazon uses its “Snowball” technology, which consists of on-site, physical storage to which customers can transfer data for delivery to an Amazon data center. For very large data transfers, Amazon will send a tractor-trailer to a customer’s site to transfer multiple petabytes of data. It's important to note that, at least in the case of Microsoft, there are data throttling approaches in place that limit the amount of data an organization can upload each day, so a bigger pipe is unlikely to unilaterally solve the problem. This needs to be taken into account in establishing the timeline for the migration effort.

• Review the bandwidth design

Remote offices with sub-optimal bandwidth connections can cause problems when migrating to new platforms because of the length of time required to move data across the Internet. Decision makers must understand the bandwidth that exists in each remote location across the organization and determine whether a higher bandwidth connection is needed during and after the migration for these locations. Moreover, good bandwidth design for the entire organization is worth

1 https://www.microsoft.com/en-us/servicesagreement

Some organizations will choose not to migrate all content because the cost and complexity is simply not worth migrating it.



revisiting if key business processes and applications will be moved to the cloud. If an organization does not currently have redundant network links, it might be worth implementing those to ensure reliability. This is especially true for organizations that will be doing archiving and backup in the cloud and cannot afford gaps in this content.

• Determine the health of Active Directory Osterman Research surveys have found that about a quarter of all mid-sized and large organizations that are migrating to Microsoft 365 will maintain hybrid deployments for long periods, if not indefinitely. This is particularly for large organizations that have significant amounts of legacy infrastructure. A hybrid deployment will require highly reliable interaction between Active Directory and Azure Active Directory, and so it’s essential to determine the current health of the Active Directory setup and resolve any issues before the migration begins.

• Determine the health of SharePoint Server

Microsoft SharePoint is a complex solution, and so organizations that have taken advantage of its custom development capabilities will likely to need to re-think their approach to SharePoint when embracing SharePoint Online. For example, they must consider how they have used customizations and other design approaches that work on-premises, but are not supported on SharePoint Online.

• Explore dependencies that exist with key applications It will also be important to explore which applications and systems rely upon maintenance of the existing environment or that will need to be rewritten for the new one. An on-premises archiving system that works with the on-premises environment may need to be updated or replaced. Organizations that are migrating from IBM Notes/Domino for email are likely to have mail-enabled and workflow-enabled Notes applications that must be replaced or reworked. CRM systems that integrate with existing solutions might need different integration capabilities. Scanners and multi-function machines that send scanned documents through the email or collaboration system will need a rethink.

• Evaluate the current firewall architecture Review the current firewall architecture, since Microsoft 365 requires certain firewall rules to be established. Organizations with multiple, independent firewalls across their network will require a method of coordinating rule additions, changes and deletions over time.

STEP 5: ENSURING THE RIGHT PEOPLE ARE AVAILABLE A proper migration depends on having the right skill sets available, either in-house or via consultants, vendors or other third parties:

• Ensuring the right skill sets are available

Organizations that undertake a migration must determine if the skills of their IT staff are adequate, including their ability to backup and archive all relevant content. While some organizations have IT staff who have experience with migrations, most don’t because migration is not a task that occurs with sufficient frequency to build a robust skill set among IT employees. Most will need to bolster their IT staff skill with the technical assistance of an external IT consulting firm or individual consultants. That said, Osterman Research has found that the vast majority of organizations still rely heavily on their internal staff members to prepare for a migration and implement new solutions. However, a majority of organizations also use outside consultants, while more than one-third use third-party vendors and their professional services to assist in the planning and migration efforts.

When selecting a third party for the migration, it’s important to ensure that they have specific expertise in migrations with the same setup and constraints in place in the organization that is to become their customer. It’s also important to

Large organizations that are migrating to Microsoft 365 will maintain hybrid deployments for long periods, if not indefinitely.



ensure that existing backup and archiving routines are not interrupted during the migration given the essential nature of both best practices. It’s important to note that moving from on-premises infrastructure to the cloud does not magically render IT staff irrelevant or unnecessary. On the contrary, it simply changes the kinds of work that they do, albeit with some important role reassignments in some cases. It’s important to determine the retraining that may be required to ensure that current staff members can manage new cloud services, or in conjunction with on-premises infrastructure in a hybrid deployment. New administration and management tools often streamline the execution of these tasks over time, as well, and these are worthy of evaluation.

• Determine how much current staff know about the new platforms IT, security and other staffers will need to be trained on the new platforms if they don’t know them already, and so it’s essential to determine the appropriate training resources as part of the migration planning effort. This is key to enabling a smooth transition to the new platform(s).

STEP 6: UNDERSTANDING COMPLIANCE REQUIREMENTS It’s essential that decision makers under compliance requirements, particularly in light of newer requirements like the European Union’s General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). These are essential regulations to understand because they have important implications for how data is managed and protected. These regulations raise the following questions that must be addressed:

• How will an organization manage its email archives? Will it move them to the

new platform (e.g., native archiving in Microsoft 365), move them to a different cloud archiving solution, leave them on-premises, leave legacy data on-premises and start archiving cloud content in the cloud, etc.?

• If the decision is made to move archives somewhere else, how will chain-of-

custody be maintained? How will data be migrated with violating the integrity of the data owners’ privacy, which is absolutely essential under the GDPR, CCPA and other privacy regulations?

• If encrypted data will be migrated, how will this be accomplished without

breaking the current encryption safeguards?

• Will data that is migrated need to be stored physically in specific geographical areas (or, conversely, not in specific geographical areas)? Will the cloud providers selected for the migration be able to accomplish this and provide assurance that all applicable statutes are satisfied?

Organizations that do not have specific compliance requirements (and there are relatively few of them) can move faster and more easily to new platforms. However, those with significant compliance mandates need a solid approach to ensure that their organization is not opened to the legal risks and financial fallout that can accompany a poorly executed migration. It’s also important to check the data privacy requirements for data that would be stored in Microsoft 365. The migration team must evaluate how Microsoft 365 handles data that would be subject to privacy requirements (such as Social Security numbers and credit card numbers), and if the automatic encryption capabilities in the platform will be sufficient for their requirements. If not, a third-party add-on encryption service may be required. Some organizations will deliberately select the location of their Microsoft 365 tenant to be outside of the United States to prevent US government access to cloud-based data under anti-terrorism legislation.

It’s essential that decision makers under compliance requirements.



STEP 7: COMING UP WITH PROPER PLANS The next step is for decision makers to develop proper migration, backup/recovery and continuity plans: • Develop a plan for migration

After establishing a good understanding of the current state of the IT and security infrastructure, the business goals that decision makers hope to accomplish from the migration, and the manner in which the new platform will be leveraged, decision makers need to develop a solid migration plan. This plan should include: o Understanding of how the migration will be conducted in phases, especially

the order in which departments and divisions will migrate to the new platform. Phasing will need to be coordinated for some users in order to make sure they have uninterrupted delegate access for mailboxes and calendars.

o The timeframes for consulting with all relevant stakeholders, including business and content owners, about content deletion, archiving, and migration activities.

o The identify and bona fides of the third-party IT consultant(s) and the internal staff members who will be working on the migration project.

o The capabilities, features and functions in the new platform that will be made available to employees over specific timeframes. For example, if an organization is migrating to Microsoft 365, which plans will be adopted for which users? One of the benefits of Microsoft 365 is the ability to “rightsize” plans for different users so that costs can be minimized.

o In addition to the point above, determine which third party solutions will be used with the new platform.

o Determine if the organization can respond to a legal discovery request or a regulatory audit during the migration and, if not, why not? Since that’s a distinct possibility, particularly for larger organizations, a plan to do so must be part of the migration effort.

• Develop a robust continuity plan

Cloud services like Microsoft 365 are normally quite reliable and suffer few system-wide outages, but they do have fairly frequent localized outages. These can render employees unable to do their work, and so a continuity plan should be established, supported by the appropriate technologies to ensure that employees can keep working during outages.

• Develop a good backup and recovery plan Because of shared-responsibility models, cloud-based solutions, such as Microsoft 365, do not offer the more traditional concept of backing up servers and data at a point in time so that administrators can enable recovery or roll-back under disaster scenarios, the ability to recover individual files, or data over longer periods than is available by default. Many third-party vendors offer backup and recovery services that are much better, adding an essential level for the management of corporate data.

STEP 8: MIGRATING TO MICROSOFT 365 In this white paper, we are discussing migration in a way that that can be applied to any communication, collaboration or archiving solution. However, we are primarily discussing migration to Microsoft 365 in particular because such a large number of migrations involve a move to Microsoft 365.

Cloud-based solutions, such as Microsoft 365, do not offer the more traditional concept of backing up servers and data at a point in time.



A migration to Microsoft 365 can be an involved process, requiring a set of coordinated activities over several weeks or months (or longer, depending on the size of the organization and the volume of mailboxes and data to migrate). Staff members will need to: • Run a pilot of the migration

Those on the migration team should test the preferred migration option by first migrating test accounts and mailboxes, followed by a small number of actual user mailboxes. Once some of these actual mailboxes have been migrated successfully, it’s good to stop for a couple of weeks to see if any issues come up. If that’s the case, it’s easier to resolve any issues for a small number of mailboxes instead of trying to rein in the issues across a much larger number of them. Third-party backup tools can assist with a pilot migration.

• Select the right migration option The migration team should select the option that makes most sense for their organization. These options include Cutover Migration, IMAP migration, or a hybrid approach that enables coexistence between an on-premises Exchange Server (if it will continue to be operated) and Microsoft 365.

• Migrate active user mailboxes IT staff can migrate active user mailboxes in light of available bandwidth and the data throttling that Microsoft applies to migration activities. Many organizations will migrate just a few hundred mailboxes each night to stay within these limits.

• Sync Active Directory and assign the licenses correctly Organizations that opt for a hybrid approach need to synchronize Active Directory with Azure Active Directory because it creates the users in Microsoft 365. Once they have been created, these licenses can be assigned. It’s helpful to implement third-party backup capabilities prior to moving data.

• Consider the management of unused mailboxes It’s not uncommon to have unused mailboxes on the Exchange Server that still contain important information, but for which users have long since left the organization. Microsoft 365 uses inactive mailboxes to support this situation. If a mailbox needs to be moved for legal or compliance reasons, a user account can be created for each mailbox. Simply attach the two, leave the account to sync to Azure AD, assign an Exchange Online license, migrate the unused mailbox to Exchange Online, place the mailbox on legal hold, and then delete the user account. The user account will be deleted, the license freed up for future use, and the mailbox data held until the hold is removed.

STEP 9: MIGRATING .PST FILES, AND MIGRATING FILES TO

ONEDRIVE Organizations that maintain .PST files must determine what information should be migrated into Microsoft 365. This requires an analysis of content inside of these files to identify data that might be subject to compliance requirements, a task in which legal and compliance teams will need to be involved. Third-party vendors offer tools that greatly streamline and simply the processing, analysis, and migration of the right data into Exchange Online or an archive.

Microsoft offers OneDrive for Business as the venue for storing and sharing files and documents. It provides users with a cloud storage solution that can synchronize to various devices, while also giving IT administrative oversight of these files. While there are numerous file sync and share solutions in use across most enterprises, OneDrive should be seriously considered because it offers the dual benefit of robust file sync and share with IT management of data, something lacking in many solutions currently in use. File shares, data on corporate desktop and laptop computers, and other devices need to be migrated from their current locations into OneDrive for Business or another new location within Microsoft 365.

Third-party vendors offer tools that greatly streamline and simply the processing, analysis, and migration of the right data into Exchange Online or an archive.



Things to Consider With Third-Party Tools Organizations that migrate to Microsoft 365 and other, newer solutions should evaluate the use of third-party tools that can improve the migration experience. Some of these solutions include: • Tools to do proper backups

As part of a migration effort, but especially afterwards for ongoing management of Microsoft 365, it is essential to have a proper backup capability. Because Microsoft 365 contains such a large proportion of corporate data for most organizations that have deployed it, it has become a system of record for these organizations. As a result, it is essential to have in place a reliable backup and recovery plan for the various types of Microsoft 365 data managed within the platform, since Microsoft does not provide this capability to its customers. There are several reasons to seriously consider deployment of a robust backup and recovery solution from a third-party vendor:

o Data within Microsoft 365 can be corrupted or lost for a number of reasons,

such as malicious conduct on the part of disgruntled employees, updates that don’t work as planned, or problems with applications that interface with Microsoft 365, among others.

o Mistakes can be made, such as accidental deletion of data, users accidentally overwriting or modifying good data, and other errors.

o Ransomware can delete or corrupt data, and so having recent, complete backups that are protected from corruption during a ransomware attack is an essential element of recovering from such an incident.

In short, good backups and the ability to access them reliably enables organizations to recover from a variety of problems with a minimum of downtime.

• Tools to ensure continuity Capabilities that enable continuity during outages are a critical element for any communication or collaboration system, but they can also provide value during the migration process itself. Ensuring that users will continue to have access to their email and other data resources during a migration can improve employee productivity and mitigate at least some of the risks associated with migration difficulties.

• Tools to help address compliance obligations Tools that will improve the compliance capabilities in Microsoft 365 and other platforms can be useful if they strengthen the data loss protection, native encryption and archiving capabilities in these platforms. For example, the use of third-party encryption can make data more secure by encrypting data before it reaches Microsoft’s data centers. In the event that a data center is breached, or if the cloud provider is subpoenaed by a government, customer data will still be protected.

• Tools to improve security

A variety of third-party tools will add additional layers of security to Microsoft 365, or deepen the capabilities already available natively. Examples include a second layer of defense for malware, phishing, and spam, in addition to what’s available with Exchange Online Protection and Advanced Threat Protection. Another example is more comprehensive data loss protection that addresses Microsoft 365 directly plus other non-Microsoft services in use at the organization. Third-party encryption capabilities can also provide important

There are several reasons to seriously consider deployment of a robust backup and recovery solution from a third-party vendor.



benefits to bolster the security available in the platform. Finally, some tools report on security issues with orphaned content and ex-employees who still have access to Microsoft 365.

• Tools to make administration simpler and easier Some third-party tools will streamline the ongoing IT administration of hybrid deployments and Microsoft 365 services. Examples include analyzing license usage, content restructuring in SharePoint Online, providing a single administration console that hides the complexity of the multiple administration consoles in Microsoft 365, and managing the interaction between Active Directory and Azure AD.

Summary Key among the capabilities needed within a Microsoft 365 environment is a way to reliably back up all content, since Microsoft has not designed its system to provide backups for its customers. Any organization that uses Microsoft 365 should have a reliable, third-party backup capability that is separate from Microsoft 365, both for the initial migration to the platform, as well as for ongoing management of Microsoft 365.

About Backupify For IT teams that need reliable, automated, and secure backup of Microsoft 365 and Google G Suite data, Backupify is the product of choice. Protecting over 4.6 million users, Backupify reduces risk, cuts costs and recovers emails, files and sites from all forms of SaaS data loss. With simplified setup in minutes and three times daily backups, you can feel confident that your cloud data is protected against accidental or malicious deletion, departing employees, external hackers, and ransomware attacks. In December of 2014, Backupify was acquired by Datto, Inc., is the leading global provider of business continuity and disaster recovery, managed networking, business management, and file backup and sync solutions. With data stored in Datto’s private cloud - purpose built for backup - Backupify saves company data from accidental or malicious deletion, canceled employee accounts and ransomware, all from an easy to use web dashboard.

Key among the capabilities needed within a Microsoft 365 environment is a way to reliably back up all content, since Microsoft has not designed its system to provide backups for its customers.



© 2020 Osterman Research, Inc. All rights reserved. No part of this document may be reproduced in any form by any means, nor may it be distributed without the permission of Osterman Research, Inc., nor may it be resold or distributed by any entity other than Osterman Research, Inc., without prior written authorization of Osterman Research, Inc. Osterman Research, Inc. does not provide legal advice. Nothing in this document constitutes legal advice, nor shall this document or any software product or other offering referenced herein serve as a substitute for the reader’s compliance with any laws (including but not limited to any act, statute, regulation, rule, directive, administrative order, executive order, etc. (collectively, “Laws”)) referenced in this document. If necessary, the reader should consult with competent legal counsel regarding any Laws referenced herein. Osterman Research, Inc. makes no representation or warranty regarding the completeness or accuracy of the information contained in this document. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED REPRESENTATIONS, CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE DETERMINED TO BE ILLEGAL.

Documents

Osterman Research WHITE PAPER O - Datto