Getting Started with MigrationWiz

From five seats to 50,000, MigrationWiz is equipped to quickly transfer data to your new environment at scale. Migrate hundreds of users concurrently - even run mail and document projects side by side if Source bandwidth allows. With project sharing and action logging features, multiple engineers can work together to manage projects. Increase visibility and efficiency for migrations of all sizes.

MigrationWiz is a fully automated, 100% SaaS migration solution that can be accessed at any time from anywhere. No specialized training or certifications necessary, and no hardware or software to install and maintain. MigrationWiz is 100% SaaS with a single UI and flow for all project types. MigrationWiz doesn't need to be installed on the environment, simply log in via your dashboard and run your migration on your time. 

BitTitan datacenters are compliant with ISO/IEC 27001/ 27002:2013, SOC 1, Type 2 and SOC 2 Type 2, PCI DSS Level 1, HIPAA/HITECH, CJIS, CSA CCM, FERPA, and more.

With MigrationWiz, you can:

  • Easily launch new migration projects
  • Sort and filter projects
  • Confirm project Source and Destination
  • Quickly transition between different projects
  • Confirm the line item is subscribed
  • Verify credentials
  • Launch pre-stage and full migrations

MigrationWiz allows you to migrate mailboxes, documents, public folders, and other workloads across a wide variety of migration endpoints. Each migration scenario, as well as each migration workload, has specific prerequisites, as well as variations in what is (and what is not) migrated. Each of the supported migration scenarios has a corresponding migration guide.

MigrationWiz may be configured via Advanced Options and Support Options

Notes:

  • Not all migration scenarios have migration guides.  If you do not see a migration guide for your specific migration, select one that has instructions for your source and also one that has instructions for your destination.  Use those to set up the migration.  The instructions for running the migration itself are very similar across all migration guides.
  • MigrationWiz now supports the capability to share migration projects across a Workgroup. Migration projects are no longer tied to individual accounts, they are tied to Workgroups. When Workgroup Administrators turn on the Project Sharing feature, all Agents besides those who are Inactive are able to view all migrations projects.  For more information see Project Sharing in MigrationWiz.

 

Prerequisites

  • Fully qualified domain name (FQDN) OR IP address. Both must be accessible via the internet.
  • Administrative access to your source and destination environments

 

Migration Types

MigrationWiz supports the following migration types. Each type may be run from and to a wide variety of common enterprise environments, which are outlined below the migration type. 

Our Help Center contains migration strategy guides for each common migration, ie. G Suite to Office 365, with guidelines for project set-up, licensing, and communication, as well as the specific steps needed to use MigrationWiz. 

Mailbox

With over 10 years and 13 million mailboxes to its name, MigrationWiz ensures users and data are migrated to the new environment with minimal disruption to users or workflow. 

 

Document

Migrate without impacting your customer’s work. Move documents and files while maintaining file hierarchy and permissions, whether on-premises or in the cloud. Document migrations take only minutes to set up, and they go as fast as the servers they’re migrating to and from will allow. With a low learning curve and simple set up, anyone on your team can perform the migration.

 

Public Folder

Automation removes the manual work and looming complications of large folder sizes, multiple file types in one folder, and hybrid deployments. Save customers from lengthy downtime and costly disruption. Maintain existing folder hierarchy, translate permissions, and mitigate lost and unrecoverable data.

Archives

 
Discover, collect, and migrate personal archive files without customer downtime. Maintain message functionality so end users can reply to email that is being exported and archived. Satisfy customers' legal and IT departments with secure, centralized personal archive storage, and reduced security risk.

Collaboration

Microsoft Teams is one of the hottest business solutions on the market today. Migrate Teams instances as part of a merger or acquisition! 

Migration Types & Environments

Supported Migration Types

  • PST (Portable Storage Tables) - Azure Storage Account or BitTitan Storage Account required
  • Mailbox
  • Document
  • Collaboration
  • Hybrid
  • Archive

We do not support migrations to or from:

Google Shared Drives (AKA Teams Drives)

Journal-based PST files

Supported Sources

Box

  • Box for Teams
  • Box Drive
  • Box Notes

Dropbox

  • DropBox Business

IBM Lotus Notes

  • IBM Lotus Notes versions 6.5 through 9.0.1 Lotus Notes versions after 9.0.1 are not supported.

G Suite/Gmail

  • G Suite
  • G Suite for Business
  • G Suite for Education
  • Google Drive for Business
  • Google Apps Premier Edition (GAPE)

IMAP

  • America Online
  • Courier IMAP server
  • Dovecot IMAP server
  • Kerio Connect (formerly known as Kerio MailServer)
  • Yahoo
  • IBM Verse
  • or any other IMAP system

Microsoft Exchange

  • Microsoft Exchange Server 2003 - Mailbox
  • Microsoft Exchange Server 2007+ - All migration types. Exchange Server 2016 Cumulative Update 1 (CU1) is not supported at this time due to instability issues.
  • Microsoft Hosting Messaging and Collaboration (HMC)
  • Microsoft Live@Edu
  • Microsoft Small Business Server

Microsoft SharePoint

  • Microsoft SharePoint Server 2010+
  • Microsoft OneDrive for Business

Note: Unfortunately, we no longer support migrations to or from GoDaddy hosted OneDrive.

Novell GroupWise

  • Novell GroupWise 7+ 

Office 365

  • Office 365 Business
  • Office 365 Business Premium
  • Office 365 Business Essentials
  • Microsoft Teams

Open-Xchange

  • Open-Xchange

POP

  • Hotmail
  • MSN
  • Windows Live
  • or any other POP system

VMware Zimbra Server

  • VMware Zimbra Server 6+

Supported Destinations

Dropbox

  • DropBox Business

G Suite/Gmail

  • G Suite
  • G Suite for Business
  • G Suite for Education
  • Google Drive for Business
  • Google Apps Premier Edition (GAPE)

IMAP

  • America Online
  • Courier IMAP server
  • Dovecot IMAP server
  • Kerio Connect (formerly known as Kerio MailServer)
  • Yahoo
  • IBM Verse
  • or any other IMAP system

Microsoft Exchange

  • Microsoft Exchange Server 2003 - Mailbox
  • Microsoft Exchange Server 2007+ - All migration types. Exchange Server 2016 Cumulative Update 1 (CU1) is not supported at this time due to instability issues.
  • Microsoft Hosting Messaging and Collaboration (HMC)
  • Microsoft Live@Edu
  • Microsoft Small Business Server

Microsoft SharePoint

  • Microsoft SharePoint Server 2010+
  • Microsoft OneDrive for Business

Note: Unfortunately, we no longer support migrations to or from GoDaddy hosted OneDrive.

Novell GroupWise

  • Novell GroupWise 7+ 

Office 365

  • Office 365 Business
  • Office 365 Business Premium
  • Office 365 Business Essentials
  • Microsoft Teams

Open-Xchange

  • Open-Xchange

POP

  • Hotmail
  • MSN
  • Windows Live
  • or any other POP system

VMware Zimbra Server

  • VMware Zimbra Server 6+

Supported Cypher Suites

  • ​​TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA
  • TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_RC4_128_SHA
  • TLS_RSA_WITH_RC4_128_MD5

 

Litigation Hold Migrations

We do support Litigation Hold migrations, but with some important known limitations.

Be aware of these limitations since, for obvious reasons, Litigation Hold tends to have a 100% fidelity requirement.

All emails in the primary mailbox will indeed be migrated
Note:
 MigrationWiz is unable to migrate Litigation Hold data from the Archive Mailbox. If Litigation Hold data is in the Archive Mailbox, it must be moved to either the primary mailbox or the Recoverable Items.

Folders created in Litigation Hold are considered to be "email folders" but this is not necessarily the case. Therefore, all the special Litigation Hold items (whose type is not email) fail to migrate due to a known limitation in EWS (which is what MigrationWiz uses for migrations, when migrating from Exchange 2007+ as the source).

Several of these are considered to be email folders by EWS, even though they are not. Due to a bug in EWS, if you try to create a non-email item within those folders, it reports an error stating: "the item type does not match the folder type".

For example, if a contact is deleted, it will be stored in the /Purges folder. When we try to migrate this contact to the destination mailbox's /Purges folder, it reports an error.

Here are some known folders in the recoverable items mailbox:

  • Versions: If Litigation Hold (or for that matter, In-Place or single item recovery) is enabled, this subfolder contains the original and modified copies of the deleted items. Note: This folder is not visible to end users.
  • Purges: If either Litigation Hold (or single item recovery) is enabled, this subfolder contains all items that are hard-deleted. Note: This folder is not visible to end users.
  • Discovery Holds: If In-Place Hold is enabled, this subfolder contains all items that meet the hold query parameters and are hard-deleted.
  • Audits: If mailbox audit logging is enabled for a mailbox, this subfolder contains the audit log entries. Note: This folder is not migrated with MigrationWiz.
  • Calendar Logging: This subfolder contains calendar changes that occur within a mailbox. Note: This folder is not available to users.
  • Deletions: This subfolder contains all items deleted from the Deleted Items folder. (In Outlook, a user can soft-delete an item by pressing Shift+Delete.) This subfolder is exposed to users through the Recover Deleted Items feature in Outlook and Outlook on the web.

The folders indicated above will, by default, be migrated into a folder at the Destination, named "Deletions". Any mail items within these folders will be migrated. The non-email items will return an error in the MigrationWiz portal, but will not prevent the migration from completing. Typically there are only a few extra errors caused when performing Litigation Hold migrations (since most items in these folders are, in fact, email items) so the error count threshold will not need to be adjusted.

Note: The migration process includes a folder discovery, plus it attempts to retrieve items from within each folder. If the attempts fail, this folder will be excluded during the migration, so that the migration can continue.

If you prefer to have the folders in the recoverable items mailbox migrated into their own corresponding folders at the Destination, and not migrated into a folder named "Deletions", you must add the Advanced Option (under the support section): OverrideRecoverableItemsFolderMapping="^SourceFolder->DestinationFolder" to your project before performing your migration. Note: KB005100 provides more information on how to add Advanced support options to your project.

Examples below:

OverrideRecoverableItemsFolderMapping="^Audits->Audits"

The above will migrate the Audits folder into a folder named Audits at the Destination. As explained above, without this folder mapping, the Audits folder would be migrated into the Deletions folder.

OverrideRecoverableItemsFolderMapping="^Purges->Versions"

The above will migrate the Purges folder into a folder named Versions at the Destination. As explained above, without this folder mapping, the Purges folder would be migrated into the Deletions folder.

Here are the recommended step-by-step directions for performing a migration that includes mailboxes set for Litigation Hold:

  • Create a regular mailbox migration project, set the advanced options and submit mailboxes for migration. Follow directions under the migration guide for the appropriate scenario. All migration guides can be found in the MigrationWiz category of the BitTitan Help Center.
  • Once the mailbox migrations have completed, create a new mailbox migration project specifically for Litigation Hold.
  • Set the project advanced options for this Litigation Hold project, so that the Source: Migrate from: parameter is set to Recoverable Items, as per the screenshot below.

    Note: This will automatically set the Destination: Migrate to: parameter to be set to Recoverable Items.

  • Return to the regular mailbox migration project dashboard, select completed migrated items, and move these items to the Litigation Hold project. Follow directions for moving items in KB004860.
  • Now, from the Litigation Hold project, submit items for migration. These will then migrate all items under the recoverable items folder at the source into the recoverable items folder at the destination.
  • Once complete, move items back to the regular mailbox migration project.

Notes:

  • All emails will be migrated.
  • Users will not be able to see anything that they should not be able to see.
  • Mailbox migrations allow up to 10 passes per mailbox. Therefore, migrating mailboxes under the Litigation Hold project will not consume any additional licenses, provided that the items were moved between projects.
  • Do not add new mailboxes under the Litigation Hold project. Instead, move items into this project. This way all project statistics and license history will be retained.​
  • When migrating to recoverable options, it is recommended to increase the retention period for deleted items folder. The default retention period is 14 days. This should be increased to the maximum, which is 30 days. Steps for this are included in this TechNet article: https://technet.microsoft.com/en-us/library/dn163584(v=exchg.150).asp
Was this article helpful?
3 out of 6 found this helpful