Migration

We are experts in cloud migration, especially email

Important for companies


AUTOMATE has a specialized team to handle the most diverse scenarios for migrating environments, mailboxes, systems and data across platforms such as Exchange, Office 365, Google and other solutions.

With a totally customized template for each project, our engineering team uses tools that automate and considerably reduce the time of the migration process, as well as enable the movement of messages, contacts, tasks and calendar depending on the source platform.


Automate Migrações

Migration Models

We have the know-how and technology available and suitable to your specific scenario!


  • By design Microsoft (Trust) with Stagging
  • Coexistence
  • Hybrid Environment
  • Synchronization via IMAP protocol
  • Export / Import of PST's
  • EWS and other solutions

What can we migrate?

Depending on the migration model, we can extract various types of content:



Messages

Calendar

Tasks

Data

PST’s

Public Fodlers

Scenarios and Platform supported

We have expertise in complex migrations and project with hundreds of users:


SOURCE DESTINATION
Dedicated Exchange 2007/10/13 Dedicated Exchange 2007/10/13/16
Dedicated Exchange 2007/10/13 Hosted Exchange 2013/16
Dedicated Exchange 2007/10/13 Office 365 Exchange 2013
Hosted Exchange 2010/13/16 Office 365 Exchange 2013
Office 365 Exchange 2013 Hosted Exchange 2013/16
Office 365 Exchange 2013 Dedicated Exchange 2013/16
Google Office 365 Exchange 2013
Google Hosted Exchange 2013/16
Google Dedicated Exchange 2013/16
Zimbra/Open Source Office 365 Exchange 2013
Zimbra/Open Source Hosted Exchange 2013/16
Zimbra/Open Source Dedicated Exchange 2013/16

Important informations


  • Administrative access to source/destination environments;
  • VPN or dedicated internet link;
  • Available accesses (firewall, passwords, etc.);
  • Licensing in quantity available at destination;
  • Available environments and access;
  • Environment properly updated (last Cummulative Update applied – table of available updates);
  • In Exchange 2007, folders may not contain more than 20,000 items;
  • In Exchange 2010+ folders may not contain more than 100,000 items;
  • Message size limits on the source output and destination input may impact. Usually the limit is 35mb per message, and can be changed depending on the level of access and configuration of the environment;
  • Public Folders will be analyzed on a case-by-case basis.
  • Environments of origin and destination must be functional;
  • It must be able to create the same amount of accounts from Source at Destination;
  • It must have the same capacity (or higher) in the Destination (size in use of the box in the Source <= max limit in the Destination). Consider that there may be an increase in the size of boxes since each system compacts and organizes attachments differently. Then after the migration it is common for the box in the Destination to be larger than in the Source;
  • "Suspended" Google Apps modes are not supported;
  • In some cases, depending on the analysis, it may be necessary to use a routing domain, eg. contax@migration.client.com;
  • Coexistence in Office 365 Small Business plans is not supported since there is no multiple domains option;
  • There may be "re-download" of the messages in the stations after the e-mails have been turned on, causing higher consumption in the Customer's network. It is suggested that it has a control (QoS) or strategies to mitigate these situations;
  • In order for us to make interventions, client's DNS service access must be granted.

Consult us for other models and types of Migration

Active Directory (AD) Migration;

Migration of documents;

Migration and environment upgrades (Exchange / Lync (Skype for Business) / Windows Server / SQL Server/ Hyper-V).