How do I configure a Quick-Switch migration?

​​​​​​​​​​How do I configure a Quick-Switch migration?​

Answer:

This multi-pass migration strategy will allow you to accelerate a transition to your new system by moving all recent mailbox data first before MX records are cut over, and then performing Full/Delta Migration passes to retrieve all older remaining email:

screenshot​​

Use cases:

  • This is useful when you want instant data availability because the first migration pass is very quick, but note that not all email is available for end users at the time of cutover.  An example case would be if the Source server was unstable, and you wanted to migrate from it ASAP.
  • This is also useful if you want to migrate a large number of mailboxes very quickly, all in one go. An example case would be after an acquisition, and you wanted to migrate all mailboxes at once (since you cannot set up forwarding because you may not have access to the Source environment).

In most other cases, we recommend following a Pre-Stage Migration strategy, as described in How do I configure a Pre-Stage Migration?

A Quick-Switch migration strategy is more complicated to set up than a Pre-Stage Migration strategy. It requires working with the project level Advanced Option date filters. Here are the exact steps to follow:

 

There are two migration filters which you will have to properly adjust between passes:

  • Date range filter in Advanced Options (optional).

  • Object type filter when starting your migration.​


​1. Submit the first pass for Quick-Switch Migration:

Because the date range filter is applied not only to email, but also to calendars, contacts, journals, notes and tasks, the first pass for a Quick-Switch migration in fact consists of two steps:

  • Migrate all items except email.
  • Migrate last 30 days of email only.

1.1. Migrate all items except email:

All calendars, contacts, journals, notes and tasks will be accessible immediately at time of cutover by users.

Submit the "first step" of the first pass of a Quick-Switch multi-pass migration for one or more mailboxes:

  • Select one or more configured mailboxes.
  • Click on Start.
  • From the drop-down list, select Full Migration.
  • Select all items except Mail.

all_but_email.png 

You can also delay your migrations to a future date and time.
delay_the_migration.png

  • Click on Start Migration.

1.2. Migrate last 30 days of email only:

  • ​Click on Edit Project, click on Advanced Options, ​and under Filtering, select Specify earliest date from which to migrate.
  • Set this date to be 30 days in the past.

 

  • Set the folder filter if you want to select folders that should not be migrated first.

Submit the "second step" of the first pass of a Quick-Switch multi-pass migration for one or more mailboxes but this time deselect all items except Mail on the Start Migration screen.

  • Select one or more configured mailboxes.
  • Click on Start.
  • From the drop-down list, select Full Migration.
  • Deselect all items except Mail.

only_email.png 

You can also delay your migrations to a future date and time.
delay_the_migration.png

  • Click on Start Migration.
     

2. Perform MX Record Cutover:

MX records are used purely for email delivery by SMTP. When you are ready to cut over to your new Destination email platform, you must switch over the MX records on your DNS providers portal so that email gets delivered to the new messaging system.

Changing MX records in DNS to point to the new system is not effective immediately, and is subject to replication delays. You will have to wait for the TTL (aka Time To Live) to expire. Until then, email systems on the Internet may continue delivering to your old system.

Using this tool for your source Domain, you will find what the TTL parameter is set to. It will take those <TTL> hours/minutes to take effect.

To allow for faster switching of email delivery from Source to Destination, we recommend reducing the TTL value for the DNS record ahead of time. That way, when you cut over MX records in DNS to point to the Destination, the effect should be almost immediate.

Once MX changes replicate, new incoming email will be redirected to the new Destination system. At this point, your end users should start working with their new Destination mailboxes.

3. Submit the Full/Delta Passes (up to 9):

A Full/Delta migration pass allows you to resubmit a mailbox so as to perform a differential migration pass. MigrationWiz will automatically find items that haven't yet been migrated since the first pass, and migrates only those. In other words, a Full/Delta pass will find and migrate residual items. In most cases, a Full/Delta pass will complete much faster than the initial pass.​

In a Full/Delta pass, MigrationWiz will continue the migration from where it left off with no duplicates, which means that all items which were not migrated in the first pass or were created after/during the first pass will be migrated.

First, ensure that no date filters are set in Advanced Options (to enter Advanced Options, click on Edit Project in top left of your dashboard, and then select Advanced Options from the drop-down list). De-select the checkboxes under the filtering section. This ensures that the entire date range will be included in this migration pass.

 

  • Click on Save Options in bottom right of screen.
  • Click on Save Project to enter the page that lists your mailboxes.

 

​To submit the Full/Delta pass for one or more mailboxes:

  • Select one or more configured mailboxes.
  • Click on Start.
  • From the drop-down list, select Full Migration.
  • Select all items to ensure everything is migrated:

Note: Your Pre-Stage Migration settings may still be set to migrate only mail. It is very important to check all boxes during this Full/Delta pass. This will ensure that all your items are now migrated.

  • Note that you can delay your migrations to a future date and time.

  • Click on Start Migration.

Notes:

Mailbox migration licenses allow up to 10 passes to be made per mailbox, 

MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because we do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict res​olution without user interaction.

Here is what would happen after a Full/Delta pass if items previously migrated to the Destination have been:

  • Deleted at the Source: then the Destination will keep containing these deleted items. We cannot propagate deletes (e.g., if an item is archived at the Source, it will look like a delete and we can’t delete the item at the Destination).
  • Moved from folder A to folder B: then these items will be duplicated at the Destination, they will be both in folder A and in folder B at the Destination.
  • Updated at the Source: then these items will not be updated at the Destination. There is no process by which the calendars, contacts, tasks, etc. can be updated. This would require conflict resolution which is only possible with a synchronization solution.

Was this article helpful?
0 out of 0 found this helpful