BitTitan FAQs

How do I create the Public Folder mailbox and database on Office 365?

Answer:

Log in to the Microsoft Office 365 portal as the user in the migration project. Make sure the user is an administrator. (You can easily tell, as there will be an Admin tab present in the upper right menu).

If the user is not an admin, then assign the user the global admin role.

From the Admin tab, select Exchange. Click on the Public Folder option in the left panel. Click on the Public Folder Mailboxes topic in the top menu.

Create a Public Folder mailbox to hold the Public Folders being migrated.

Click on the Public Folder topic in the top menu. Click on the ... (More) button from the set of actions, and then select Root Permissions. Make sure that the admin user is listed as an owner.

If the admin user is not listed as an owner, then add them and apply the change to all subfolders.

Make sure there is an Outlook tab.

If there is no Outlook tab for the admin user, then assign the user an Office 365 license.

Verify the mailbox can be viewed by clicking on the Outlook tab.

Go back to the Office 365 Admin Dashboard.

Click on the Users and Groups option in the left panel.

Select the admin user and ensure the following:

The admin user is a valid active user.

The admin user has an Office 365 license assigned.

The admin user name is not misspelled.

Cannot connect to Admin API - Users: Google.Apis.Requests.RequestError Domain cannot use APIsCannot connect to Admin API - Users: Error:"unauthorized_client", Description:"Unauthorized client or scope in request.", Uri:""Answer:

This error occurs when MigrationWiz is unable to connect to the Google Drive Admin API. You should confirm that API access is enabled by performing the following steps:

Go to https://admin.google.com and authenticate as a domain administrator.

Click on Security.

Click on API reference.

Confirm that the checkbox Enable API access is checked.

What email address will MigrationWiz email messages come from?Answer:

MigrationWiz email messages will come from [email protected] on behalf of your BitTItan user account.This setting cannot be customized.

Error Message: Cannot create item: [filepath] ---> One or more errors occurred. ---> [invalid_account_type/feature/...]

Description: Large Dropbox migrations may sometimes be blocked by a Cannot create item error.

Cause: A standard Dropbox account allocates 25,000 upload calls via the API for any given month. This limit is reset on the 1st of every month. If the total API Upload calls made exceeds 25,000 calls, you will need to contact Dropbox to purchase an unlimited API license for the team account. You may then resubmit the migration.

Resolution: Contact Dropbox to purchase an unlimited API license for the team account. Once that is processed, resubmit the migration.

How do I find my AWS Access Key and Secret Access Key?

Answer:

In order for MigrationWiz to access your Amazon Web Services (AWS) account automatically, the Access Key and the Secret Access Key are required. The Access Key and the Secret Access Key are not your standard user name and password, but are special tokens that allow our services to communicate with your AWS account by making secure REST or Query protocol requests to the AWS service API.

To find your Access Key and Secret Access Key:

Log in to your AWS Management Console.

Click on your user name at the top right of the page.

Click on the Security Credentials link from the drop-down menu.

Find the Access Credentials section, and copy the latest Access Key ID.

Click on the Show link in the same row, and copy the Secret Access Key.

Introduction

This is the complete onboarding task flow for migrating public folders from a multi-tenant hosted Exchange environment running Exchange 2007 or later, to public folders on Office 365.

This guide should be followed if the total size of the public folders on the source is less than 20GB. If larger than 20GB, refer to Public Folder Migration Guide From Hosted Exchange To Office 365 > 20GB.

Complete each step in the order listed. If additional instructions are required, a link to a corresponding Knowledge Base article is provided.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare Source Environment

Ensure migrating admin account has permission on all Public Folders (owner access rights need to be permitted to the account being used for migration). For more information refer to How do I ensure the admin account being used for Public Folder migration has permissions on all Public Folders?

Note: You will not be able to run the PowerShell commands on your Hosted Exchange environment. Ask the Hosted Exchange provider to add this permission to the account that is being used for migration. If they do not want to provide "owner" access rights, ask them to add "read" access rights instead.

When migrating from a multi-tenant Hosted Exchange environment, the Public Folder structure on that hosted environment is under a top-level Public Folder, and not under the root folder. Additionally, the Hosted Exchange provider will not grant access to the root of their Public Folders, since this is a shared environment. Therefore, ask the provider to run the PowerShell script below so that we can obtain the unique identifier for the customer's top-level Public Folder. Then add that to the MigrationWiz project, under Advanced Options (this step is included in the MigrationWiz section below). This is the PowerShell script that your Hosted Exchange provider must run in order to obtain that PublicFolderRootEntryId:

Get-PublicFolder "\the path of the PF" | fl entryid*

Note: Record the output of this script. This needs to be entered under the MigrationWiz project's Advanced Options (as indicated in the MigrationWiz Steps section below).

Split up large Public Folders; if any Public Folders contain more than 20,000 items (if Source = Exchange 2007), or 100,000 items (if Source = Exchange 2010 or later), these should be split into multiple Public Folders. This will speed up your migration.For more information refer to How do I find the size of Source Public Folders?

Prepare Destination Environment

Set up the Office 365 tenant.

Add users and assign Office 365 licenses (if permissions are being migrated, this is required).

Create a public folder mailbox and assign root permissions to this public folder mailbox, to the administrator account being used for the migration. For more information refer to How do I create the Public Folder mailbox and database on Office 365?

MSPComplete Steps

Create customer. For instructions see View, Add, and Edit Your Customers

Create the Source and Destination endpoints (select Exchange Server Public Folder forthe source endpoint, and Office 365 Public Foldersfor the destination endpoint). For more information see View, Add, and Edit Customer Endpoints

Launch public folder migration (select All Products> Public Folder Migration).

MigrationWiz Steps

Set up the Project.Read the How do I create a new migration project? article for more information.

Set Project Advanced Options. See What project Advanced Options are available?

Add:RemoveFilterBasedOnFolderType=1 This flag is required if Public Folders contain items other than mail, such as calendar and contact items. For more information see How do I migrate a Public Folder with multiple item types?

Add: PublicFolderExportRootEntryId=xxxxxxxxxxxxxxxxxxxxx Notes:

The name of the Advanced Option is case-sensitive and should be entered exactly as shown above.

The PublicFolderExportRootEntryId option should contain the EntryId of the Source top-level Public Folder.

Replace the "x"s with the ID that was obtained when running the PowerShell script provided in the "Prepare Source Environment" section of this Migration Guide.

After entering this text, click the "+" sign to save the entry.

Under Licensing: Set the maximum number of licenses to consume per item per pass. Default value = 1. This allows up to 10GB to be migrated. For example: If migrating all Public Folders, using a forward slash ( / ), and the total data size = 39GB, then increase this value to 4, otherwise, the migration willstop at 10GB. See How do I enable consumption of multiple licenses for a single item?

Under Performance: Set thePreferred BitTitan Data Center For fastest migration speeds, select the Data Center that is closest to your Office 365 Destination tenant. See How do I specify the data center to use for my migration?

Set thePreferred BitTitan Data Center. For fastest migration speeds, select the Data Center that is closest to your Office 365 Destination tenant. See How do I specify the data center to use for my migration?

Import Public Folders into the dashboard. Options:

Choose to migrate all Public Folders for the customer, from the root down. Select Add/Quick Add and enter a forward slash ( / ) within the Root Folder Path field. We recommend this because it will migrate all Public Folders, and you will only need one Public Folder license per 10GB of data, regardless of the number of top-level Public Folders. This will then migrate all Public Folders, based on the PublicFolderRootEntryId that has been added into the project's Advanced Options. For more information see How do I select to migrate all my Public Folders from the root level down? OR

Add individual Public Folders through Quick Add, and enter each root folder path. Note: You cannot use the Autodiscover option when migrating from Hosted Exchange environments. If Autodiscover is tried, it will time out, since it will attempt (unsuccessfully) to discover all Public Folders from the top-level root folder, which is protected.

Run Verify Credentials. For more information, see How do I verify credentials?

Purchase Public Folder licenses. For more information, see How do I purchase licenses?

To obtain an estimate of the number of Public Folder migration licenses required foryour migration project, follow the directions in How do I estimate the number of Public Folder migration licenses required?.

Perform a Full Migration pass.For more information, see How do I start a migration?

Perform afinal Full Migration pass using the Advanced Option AllowAllMailboxTypesForPFPermissions=1 in order to migrate all Security Group Permissions. If you do not run the second pass, none of the Security Group Permissions will migrate.

Click the pie chart on the MigrationWiz dashboard to receive an email containing all the project migration statistics. For more information see How do I request statistics for my migration project?

Note:If you have multiple email addresses assigned to the Public Folder on the Source, and want to migrate them to the Destination, use the instructions in this article: Migrating mail enabled Public Folder email addresses.

Can you reply to migrated emails?

Answer:

Yes. Some versions of Exchange use legacy DNs as email addresses for internal delivery. Here is an example of a legacy DN email address: /o=Org/ou=Department/cn=Recipients/cn=user. This format is also sometimes referred to as X400 or X500 address.

Most migration solutions migrate email as-is. Any email whose recipients use the legacy DN format cannot be replied tounless the legacy DN matches Active Directory information in the new environment (which is very common). To solve this problem, MigrationWiz automatically converts legacy DNs into SMTP email addresses to ensure migrated emails can be replied to.

The account does not have permission to impersonate the requested user.

This error indicates that the specified administrative account does not have permissions to impersonate users and log in to their mailboxes for migration purposes.

When migrating to Office 365, we automatically execute remote PowerShell commands to grant the admin account impersonation rights. However, those PowerShell commands can time out before they complete. In this case, it will be necessary to manually grant permission using remote PowerShell. There is no need to install any additional software in order to do this. Please be patient; the remote PowerShell commands below can take several minutes to complete.

Resolution:

Make sure the admin account is a global admin.

Click on the Windows Start button.

Search for Windows PowerShell (PowerShell should already be installed).

Start PowerShell under an administrator context (right-click -> run as administrator)

Run the following PowerShell commands (one at a time):Set-ExecutionPolicy Unrestricted$LiveCred = Get-Credential$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirectionImport-PSSession $SessionEnable-OrganizationCustomizationNew-ManagementRoleAssignment -Role "ApplicationImpersonation" -User [email protected]

Notes:

Enable-OrganizationCustomization command can take a very long time to run.

Ignore any error such as "This operation is not available in current service offer."

Ignore any error such as "The assignment of the management role 'ApplicationImpersonation' [...] won't take effect until user is migrated."

Make sure to replace "[email protected]" in the last PowerShell command above with the global admin account used for migration.

Do you support migrations from Exchange archive mailboxes?Answer:Yes. This is considered a personalarchive migration project.Note: Archive migrations are supported only from Exchange 2010 SP1 and later.

For more information about personal archive migrations options, refer to KB004910.

How do I set the

view in Outlook to see attachments?Answer:In Outlook 2010 to 2016, from the top navigation bar, click on View, then Change View.Note: In Outlook 2016, there are Advanced View Settings. Compact Advanced View can include filters which can be set to block the view of attachments. In the menu, changing the view by clicking view, reset view, will restore the view.In Outlook 2010+, the conversation view may be collapsed, with attachments not visible. Toviewfull conversations, click on View, Conversation Settings,Always Expand Conversations. In conversation mode, to find the attachment within a message, you will need to expand the parent email byclicking on the parent email and then click on theWhite Triangle. This will expand the email chain. Click on theWhite Triangle again to show all emailand attachments within the email chain.

BitTitan now supports a new v2 Endpoint when OneDrive for Business or SharePoint Online is the destination for your migration. Because we still have the regular (v1) endpoints for both scenarios, this guide should help you understand when to use which Endpoint.

What's the difference between the two endpoints?

The v2 Endpoints use the Microsoft Migration API.

For the Migration API, Microsoft leverages Azure storage to maximize speed & bypass throttling. Using the v2 Endpoints results in a faster migration.

Because these Endpoints use Azure storage, MigrationWiz requires an Azure Storage Account Name & Azure Access Key as inputs if you are using your own Azure storage. These are not required if using the Microsoft provided Azure storage.

If using Microsoft-provided Azure storage, you don't need to enter the Azure Storage Account Name & Azure Access Key. These will be provided automatically in the Microsoft system and will not be shown in MigrationWiz.

These Endpoints can only be selected when OneDrive for Business or SharePoint Online is the destination.

Both v1 and v2 Endpoints can comfortably support approximately 200 concurrent migrations.

The v2 Endpoints supports syncing items. You can use the SyncItems=1 Advanced Option if required.

Important, the v2 connectors do not support invalid XML characters. The list of migration items will need to be checked for these characters and items with invalid characters will either need to be renamed or migrated using a v1 connection instead of v2.Note: The invalid characters are:<>"'&

Note: For v2, the Azure BLOB storage would need to be scaled for the whole data set.

When should I use the regular (v1) Endpoints, and when should I use v2?

v1

Best used for smaller volume migrations (20GB and under). Because v1 uses an older API, the chances of throttling are increased when dealing with large volumes.

If you do not have access to Azure Storage, or you do not want to set up Azure storage, use the v1 Endpoint.

v1 must be used when OneDrive for Business or SharePoint Online is not the destination. For example, you cannot use the v2 Endpoint in a OneDrive for Business to Google Drive migration scenario.

v2

Best used for medium/large migration projects (20GB and over). You won't hit the same throttling limits as you would with v1.

If you have access to Azure Storage, and you're confident in the Azure Storage Costs, we recommend using the v2 Endpoint.

v2 can only be used when OneDrive for Business or SharePoint Online is the destination.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond: We were unable to connect to the server.

Resolution:

Check and ensure thatthe server is up and running. If it is possibleto connect tothe server from the internet, this may have been an intermittent network problem. Submit the mailbox in Retry Mailbox Migration Errors mode after the mailbox has successfully migrated.

For Google migrations, this means that IMAP is disabled for either the account or the entire tenant. You will need to enable IMAP access for MigrationWiz to connect. This can also occur if the Terms of Service have not been accepted.

Request Premium Phone Support Our customers are important to us. We offer 24/7 email support, as well as Premium Phone Support, a robust Knowledge Base, and community forums. Our support engineers are experienced with our products and are the front line in addressing bugs and errors.

Each support ticket is scoped to a single issue. This enables us to quickly and thoroughly respond to all issues without one issue getting lost in a more complex discussion or fix. It also helps our engineers track, support, and address issues that you might encounter.

We are always working to improve our support and resolution systems. If you have any questions or concerns, please let us know.

Support Options

In addition to browsing the Help Center and Community siteto find answers to your questions, product support is available via email and Premium Phone Support. Before submitting a support request, check the system status pageto determine if there are known system issues that might be impacting your project.

All support requests are scoped to a single issue or error. Additional errors or issues will require a new support request. This is to prevent any miscommunication, keep all troubleshooting in a single ticket for accurate resolution and to help improve our products with accurate reporting.

Note: Before using the options below to get assistance, it is recommended that you be signed into your BitTitan account to prevent a later sign-in from interrupting the support request process.

Request Assistance

This process will walk you through our Guided Assistance program and show you how to open a ticket with us. For Premium Phone Support, please scroll to the bottom of the page.(Or go straight to Submit a Ticket.)

To start your support request process, navigate to the main Help Center page and click on Contact Support (the ambulance) in the bottom right:

This will bring you to a product menu. This helps us understand what issue you might be experiencing so that we can suggest some common fixes or resources.

Select which product you would like help with, or click onOpen Tickets to view or update previously opened tickets.

The Guided Assistance program will walk you through a few more options. This narrows down the issue you might be having so that we can suggest the most useful articles.

Continue selecting appropriate options in each of the next couple of steps.

Once you've chosen the product, migration type, and topic, you will be presented with a list of Suggested Articles, or notified if there aren't any suggested articles. You will also be offered, at each step of the process, the option to change any of your chosen options.

At this point, you will be offered the option of opening a new ticket. Please fill out the ticket as thoroughly as possible so we can help you quickly. Our support agents will triage the ticket and reach out to you to begin your support process.Email support is available 24 hours a day, 7 days a week.

Fill in each field in the ticket form. Attach any screenshots, log files, or other attachments using the Attachment field.For missing items, include ascreenshot of the items at the Source and the expected location on the Destination. Note: If you have more than one attachment, it is recommended to include all the attachments together inside a zip file, then attach the zip file.

In the Message box include these specifics:

A full, detailed summary ofthe issue, any error messages, andthe user experience ("Need urgent help" and "Call ASAP" don't give our engineers enough information to work off of.)

A list of the troubleshooting steps performed so far

The name of the project or activation code

The mailbox(es) impacted

Your Name

The best time for contact

Your time zone

Response times vary, based on the volume of requests, as well as the complexity of the issues that require investigation. Our Service Level Agreement(SLA)response time for normal priority support requests is 24 hours from the time the request is received by our system.

Note:Support is available in English and Japanese.

Request Premium Phone Support

If you have a critical incident that requires direct access to Support Engineers, you can buy one or more Premium Phone Support licenses.A Premium Phone Support license will guarantee that Support Engineers will call you back within two hours from the time the request is received by our system. They will work with you until the problem has been resolved.

Follow these steps to purchase Premium Phone Support licenses:

SelectPurchasefrom the top right menu of MSPComplete or MigrationWiz.

In theServicessection of the bottom of the page, select Premium Support Single IncidentorPremium Support Five-Incident Pack to access the Purchase Support Escalation licenses form.

Select the number of licenses and click Buy Nowto fill out the billing information.

Once purchased, your Premium Phone Support license(s) will appear in the24/7 Premium Phone Supportfield of the Contact Support form.

Follow these steps to use your purchased Premium Phone Support license:

Go through the Guided Assistance form as described above. You may find the answer to your question without needing to use the Premium Support license.

If none of the presented articles answer your question, click the Submit a Ticket button to access the support form.

On the support form, in the 24/7 Premium Phone Support field, select the checkbox Request a Call-Back.

Your purchased Premium Phone Support license(s) will appear to the right. Selecting the checkbox will consume a Premium Support Ticket license and convert the support ticket to a Premium ticket.

Note:Premium Phone Support is only available in English.

Introduction

This is the complete onboarding task flow for migrating mailboxes from IMAP systems to On-Premises Exchange.Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

Due to API limitations, IMAP migrations will only migrate mail items.

The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.

DeploymentPro can possibly be used to configure the Outlook profiles, however, it is not officially supported for use with Exchange.

Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

We can only migrate mail items that are stored on the IMAP server. Verify that a copy of the mail remains on the server. If there is no mail on the IMAP server and it's stored in a local PST, use the PST migration process. If the data is stored in a local Outlook OST file (Outlook 2013 and Outlook 2016), export the mailbox to a PST and use the PST migration process.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prerequisite

There are many different versions of IMAP mail systems available. For this reason, we recommend running a trial migration on one or more mailbox(es) prior to the actual full migration project. Note: Once the trial migration completes, check on the folder structure at the Destination to ensure that the directory structure is as desired. KB004671

Prepare the Source Environment

Test connectivity to the IMAP server by going here. Fill in the form, and click the Test button.

Export user list to a CSV file. Notes:

Administrator accounts with at least read rights can export a user list.

If you do not have an administrator account, you will need to ask your IMAP host to provide you with a complete user list, in CSV file format.

This CSV file will be used to bulk add users into your MigrationWiz mailbox project.

Prepare the Destination Environment

Set up user accounts.

Create an admin account for migration that has full access permissions to all mailboxes. KB004725

Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights

FullAccess -Automapping $false -User MigrationWiz Notes:

In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.

Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.

Set up a remote PowerShell session with Exchange 2010+. KB005111

To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:

Disable throttling against the admin account. Refer to Option 1 in KB004945.

Verify mailbox accessibility, using EWS. KB004304

If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

Increase message size limits. KB004613

Increase maximum accepted content length. KB004609

Increase maximum receive message size. KB004532

Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610

MSPComplete Steps

Create the customer. KB005421

Create the Source and Destination endpoints. KB005427

Click EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select IMAP.

Server Name should follow format: imap.example.com

Enter server port. As a general rule, the server port will be either 143 or 993 (if using SSL). Note: If using SSL, checkmark the Use SSL box.

Click EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+

Enter the OWA URL KB004392

Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.

For the Source endpoint:

For the Destination endpoint:

Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:

How do I purchase licenses?

Migration License Types

Apply User Migration Bundle licenses to the Customer's Users

Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:

Via Group Policy Object (GPO). Note: This is the recommended methodology because no end user interaction is required. KB005412

Via email. KB005411

DeploymentPro Steps

Launch DeploymentPro.

Enter the Domain.

Select the Destination endpoint.

Checkmark the Auto-populate box.

In the Client Interface Configurations section, upload your company logo and add supporting text. Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.

Save and continue.

Go to All Products > Device Management, then clickDeploymentProon the far left and follow the prompts to launch.

Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.

Configure the customer DeploymentPro module:

Activate DeploymentPro module for users.

Either select all users (by check-marking the box to the left of the Primary Email column heading) or select the individual users (by check-marking the boxes to the left of the user email addresses). Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

Click the Schedule Cutoverbutton.

Schedule the profile cutover date.

Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutoverbutton. Notes:

The DeploymentPro module will install on user devices immediately and then run silently until this date.

The profile cutover date should be set to a date and time that is shortly after MX record cutover

On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

MigrationWiz Steps

Create the Mailbox Migration project.Read the How do I create a new migration project? article for more information.

Add the accounts (also referred to as items) that will be migrated to the project. KB004842

If you have an admin account on the Source IMAP system, the format will be as follows. Note: Most IMAP systems do not support administrative credentials. Refer to KB004344 for a list of supported IMAP systems.

Source Email: SMTP email address.

Source Login Name: Consists of two combined names: the user name of the person whose email is being migrated, and the user name of the mailbox admin account. For example, for Exchange IMAP: Domain/Admin_UserName/User_UserName. Important: To determine the correct format to follow for this value, refer to KB005830.

Source Password: Enter the administrator's password.

If you do not have an admin account, enter the Source Email addresses in the Source Email column, and checkmark the I don't know the login name and password for the Source mailboxes box. Note: Users will then be requested to provide their credentials during the migration process.

For the Destination, you only need to enter the Destination email address of each user.

Use Bulk Add, with a CSV file that contains your user list.

Source:

Destination:

Set the Project Advanced Options. KB004834

Run Verify Credentials. KB004511

Notify users that a migration is occurring. Send email to all users, telling them the time and date of the migration.

Pre-Stage pass: Select the users > Click the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. KB004938

MX Record Cutover. Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.

Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.

Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. KB004938

Run Retry Errors. KB004658 Note: If errors are listed in the MigrationWiz dashboard with the following error message: "Unexpected extra arguments to Examine Context: FolderNameWithQuote", then follow the steps below to add the support option flag AllowQuoteInFolder=1 at the item level, and run retry errors. KB005859

Steps: Click the Edit Item icon to the right of the item that you wish to edit > Under the Support section, enter the support option: AllowQuoteInFolder=1 > Click Save Item > Select the line item in your MigrationWiz dashboard > Click Start > Retry Errors

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support. KB004529

If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

Introduction

This is the complete onboarding task flow for in-place archive mailboxes from Office 365 to in-place archive mailboxes on Office 365.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

We recommend that the mailbox migration project is performed first, before migrating archives. For guidance, refer to the migration guide that matches your scenario.Examples:

If you are changing the domain name when migrating from Office 365 to a different Office 365 tenant, refer to the Office 365 to Office 365 Migration Guide - While Changing the Domain Name article.

If you are keeping the domain name when migrating from Office 365 to a different Office 365 tenant, refer to the Office 365 to Office 365 Migration Guide - While Keeping the Same Domain Name article.

If a mailbox migration project has already been performed, the same administrative credentials that you used during your mailbox migration project can be used for this project, and it is likely that you have already performed all of the steps in each section, other than the MigrationWiz Steps. In that case, proceed to the MigrationWiz section of this guide.

More information on Office 365 in-place archives can be found in the How users access their archive mailboxes article from Microsoft.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Exchange Environment

Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed.

Set up an administrator account for migration on the Source Exchange mailbox server. Read the How do I create an administrator account for login? article.

EWS must be working on the Source Exchange server. Read the How do I verify if my OWA URL is correct? article.

Test mailbox access. Read the How do I test mailbox access? article.

Disable the Exchange throttling policy during migration. Read the How do I disable the throttling policy on Exchange? article. Notes:

This is only relevant for Exchange 2010+. Exchange version 2007 and earlier do not have throttling policies.

If you are running Exchange 2010 and later, we highly recommend disabling the Exchange throttling policy in order to speed up your migrations.

Follow the instructions under Option 1 in the How do I disable the throttling policy on Exchange? article to disable throttling for just the admin account, rather than for all users.

Prepare the Destination Environment

Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed.

Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the How do I create an administrator account in Office 365, and then use this during migration? article.

Set up accounts on Office 365 and assign licenses. These can be created in several ways:

Manually, one at a time. Read the Add users individually or in bulk to Office 365 article from Microsoft.

By bulk import, via CSV file. Read the Add several users at the same time to Office 365 article from Microsoft.

By PowerShell script. Read the Create user accounts with Office 365 PowerShell article from Microsoft.

By DirSync, AAD Sync, or AAD connect. Read this very important Knowledge Base article before running synchronization. Read the How do I synchronize my Azure Active Directory objects to Office 365? article.

Prepare the tenant to send and receive large mail items. Read the How do I migrate large mail items to Office 365? article.Note: This step is only required if your Source environment will support migration speeds that are faster than the Destination.

MSPComplete Steps

Note: If you have completed a mailbox migration project against this Source environment, these steps will already have been completed. The endpoints that were created for your mailbox migration project can be used for your in-place archive migration project.

Create the customer. Read the View, Add, and Edit Your Customers article.

Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints article.

Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:

How do I purchase licenses?

Migration License Types

Apply User Migration Bundle licenses to the Customer's Users

MigrationWiz Steps

Create an In-Place Archive Migration project.Important: Remember that this is anin-place archive migration project. It is not a mailbox migration project. Read the How do I set up a migration project? article.

Add the accounts (also referred to as "items") that will be migrated to the project. Read the How do I add items to my migration project? article.Important: If the domain name is remaining the same, it is important to use the tenantname.onmicrosoft.com addresses for both the Source and Destination usernames, rather than the vanity names. If the accounts are added with the vanity domains initially, you can use the Change Domains button at the top of the project to change the domains to the onmicrosoft domain.

Set the Project Advanced Options. Read the What project Advanced Options are available? article.

The following options are the most valuable for this migration scenario:

Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. Read the How do I migrate to Exchange or Office 365 using impersonation? article.

Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. Read the How do I migrate to Exchange or Office 365 using impersonation? article.

Set your preferred Destination.Note: The default is to migrate into mailboxes, rather than archives, at the Destination. To change this, set Destination: Microsoft Office 365 > migrate to: Archive. Read the What are my mailbox or archive migration options? article.

If this is a large migration project, the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g., 250.Note: There is no limit for this value (for cloud to cloud migrations), if using impersonation.

If the domain name is changing at the Destination, add the following:

Under Support/Support Options, add the following: RecipientMapping="@sourcetenantname.onmicrosoft.com->@destinationdomainname.com"Read the How do I add Recipient Mappings to a project? article.Notes:

The RecipientMapping above is just an example; do not copy this verbatim. It needs to be changed to reflect the sourcetenantname.onmicrosoft.com account name and the customer Destination domain name.

More than one remapping expression can be used.

This is a very important step for Office 365 to Office 365 migrations. It ensures that archived email has the ability to be replied to after migration because it will be mapped to the new Destination domain name rather than using the old sourcetenantname.onmicrosoft.com account name (which will no longer be available, once the tenant is retired).

Run Verify Credentials. Read the How do I verify credentials? article.

Perform a Full migration pass. Read the How do I start a migration? article.Notes:

For archive migrations, we recommend only running a Full Pass Migration, rather than following the Pre-Stage Migration strategy (typically used with mailbox migration projects).

Since the archive migration project is typically performed after the mailbox migration project has been completed (or at the same time), this guide does not include the steps for MX record cutover.

Run Retry Errors. Read the How do I retry failed items? article.

Look through the user list and click any red "failed migration" errors. Review information and act accordingly.

If problems persist, contact Support. Read the How do I get support for your products? article.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article.

This article describes the limitations that apply to SharePoint Online and OneDrive for Business, which you might need to account for if you plan to migrate to one of those services.

File path limitation

SharePoint Online and OneDrive for Business have a 400 character limit that applies to file paths and file names. See What would I use the Advanced Option IncreasePathLengthLimit=1 for? for more information. Character limits might not be enforced in other document storage services, like Google Drive or Dropbox. When migrating from one of those platforms to SharePoint Online or OneDrive for Business, you might need to shrink file paths and file names. Use the ShrinkFoldersMaxLength advanced option as described in the How do I auto shrink the folder path when migrating to OneDrive for Business or SharePoint Online? article.

File and folder name extension limitation

There is a list of file extensions that are not allowed to be created inside of SharePoint Online and OneDrive for Business.

Read the following articles for more information:

Types of files that cannot be added to a list or library

Information about the characters that you cannot use in site names, folder names, and file names in SharePoint

Contributors are not permitted to upload SWF files onto SharePoint 2010

Notes:

The list currently contains: .ashx, .asmx, .json, .soap, .svc and .xamlx.

This may be changed at any time by Microsoft.

This list cannot be changed by an administrator in SharePoint Online and OneDrive for Business.

Additionally, an administrator may add other extensions to this list.

In addition, folder names may not end with any of the following strings: .files, _files, -Dateien, _fichiers, _bestanden, _file, _archivos, -filer, _tiedostot, _pliki, _soubory, _elemei, _ficheiros, _arquivos, _dosyalar, _datoteke, _fitxers, _failid, _fails, _bylos, _fajlovi, _fitxategiak

File created inside shared folders limitation

If you plan to migrate from Google Drive, there may be a scenario where a user creates a folder and shares it with another user. The other user then creates a file within that shared folder. Use the "moderate migration mode" to migrate those files, as described in the How does Google Drive to Microsoft OneDrive with Moderate Mode work? article.

Multiple files with the same name limitation

Some environments, such as Google Drive, allow the user to create multiple files of the same name in the same folder. This is not supported by OneDrive for Business. Use the RenameConflictingFiles=1 advanced option as described in the How do I migrate multiple files with the same name into OneDrive? article.

For more information: Read the Restrictions and limitations when you sync files and folders article from Microsoft.

Introduction

This is the complete onboarding task flow for migrating folders and documents from Google Drive to Box.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

The Source must be a paid version of Google Drive. Free Google Drive accounts are not a supported Source.

Items and folders in "Shared with Me" will not be migrated. Only items in "My Drive" will be migrated. To migrate "Shared with Me" items, they must be added to "My Drive".

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

Enable OAuthentication 2.0 in your Google admin portal, to grant MigrationWiz access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.Notes:

If you are migrating from multiple domains, repeat the steps for each domain.

Make sure there are no spaces before or after the scope entry. This will cause the authorization to fail.

OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts, G Suite Legacy free accounts, or Google Apps Legacy free accounts. Unfortunately, migrating any Google Legacy free accounts is not supported.

Enable API Access. Log in to Google Admin portal > Security > API Reference > checkmark the Enable API Access button.Note: This extra step is mandatory when migrating from Google Drive.

Export mailboxes to CSV file(s). From Google Admin portal > Click Users > Click (3 vertical dots) > Download Users > Download All Users > Click OK > Save.

Prepare the Destination Environment

Create an administrator account on Box to be used for migration.

Set up accounts on Box. More details can be found here.Important: If you are migrating permissions, the part of the usernames before the "@" sign on your Destination must match the part of the username on your Source before the "@" sign, e.g., [email protected] on the Source must follow the same format before the @ sign on the Destination, and so must also equal "john.smith" on the Destination. The domain name, however, can be different. KB004843

Set up groups on the Destination. If permissions were assigned to groups on the Source, and you want these to be migrated, the group names on the Destination must match the group names on the Source. KB004843. More details on creating and managing groups on Box can be found here.

If you are not using Box.com admin credentials, let users know they will receive an email during migration, requesting their Box.com credentials. If using Box.com admin credentials, skip this step, since users will not be receiving an email. Note: To use Box.com admin credentials, there must be a Box.com Business account with a minimum of three (3) seats in the account.

MSPComplete Steps

Create the customer. KB005421

Create the Source and Destination endpoints. KB005427

For the Source endpoint:

Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Google Drive.

Enter the Google admin account email address and domain name in the appropriate fields.

For the Destination endpoint:

Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Box, and select Provide Credentials.Notes:

Under this endpoint type, there are no fields to enter admin account and password.

There will be an API Authorization Request screen prompt when you set up your MigrationWiz project later in the process.

MigrationWiz Steps

Create the Document Migration project.Read the How do I create a new migration project? article for more information.

Note:At the Authorization tab, click the Request Access Token button. Within the Box - API Request Authorization page, enter the email address and password for the Box admin account and click the Allow button on the next screen.

Add the accounts (also referred to as "items") that will be migrated to the project. KB004842

Set the Project Advanced Options. KB004834

Under Support/Support Options add:

InitializationTimeout=8 - This increases the initialization timeout window to eight hours. KB005099 Note: There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.

Set the Advanced Option to send a notification to end users after the migration pass completes.

Notifications > Send successful migration and notification to: > Source email address (if users are still using G Suite Gmail) or Destination email address (if users have already migrated from the G Suite Gmail platform).

Customize the notification email. Put a checkmark in the Customize "successful migration" email box. Add your own customization text and company name to this email.Note: Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-stage migration strategy, only set this up prior to the final Full (Delta) pass.

Run Verify Credentials. KB004511

Run an assessment to calculate the number of licenses required for your migration. KB005237

Purchase User Migration Bundle licenses.Refer to these articles for more information:

How do I purchase licenses?

Apply User Migration Bundle licenses to the Customer's Users

Migration License Types

Notify users that a migration is occurring. Send email to all users telling them the time and date of the migration. During this time, they should not modify any documents in their Google Drive accounts, because any modifications will not be included in the migration.

Perform the migration, using one of the following strategies:

Full Migration strategy. For more information, see How do I start a migration?

For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.

Pre-Stage Migration Strategy:

Pre-Stage pass. For more information, see How do I start a migration?

Full (Delta) pass. For more information, see How do I start a migration?

For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626

Post-Migration Steps

To prevent users from inadvertently logging in and using their Google Drive accounts, decommission the Google Drive user accounts, or change their passwords.

Notify users once the migration has completed.Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion. Assist them with setting up access to their Box accounts.

Provide training to your users on Box.

Device Management is an MSPComplete component that allows you to monitor and assess your customers computers, as well as resources such as workstations, users, and groups. To enable Device Management, you download and install a lightweight, non-intrusive application, the Device Management Agent (DMA), on each of your customer's computers.

The list below represents a set of key articles to help you get started with using Device Management.

Introduction to Device Management

System requirements for the Device Management Agent?

How do I access the Device Management Overview?

Information Collected by Device Management

View Device Management services and statistics

How do I view the Device Management Agent status for users and computers?

How do I deploy the Device Management Agent with a Group Policy Object?

How do I deploy the Device Management Agent through email?

Install the Device Management Agent on terminal servers

Create an MSI Package to Deploy DMA

How do I deploy the Device Management Agent on computers that use a proxy?

What servers and ports need to be configured to allow access to the Device Management Agent?

Troubleshoot connectivity between the Device Management Agent and MSPComplete

Introduction

This is the complete onboarding task flow for migrating folders and documents from Box to OneDrive for Business. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

The Destination must be OneDrive for Business, not the personal OneDrive version.

If migrating to an Office 365 Small Business Tenant account, the processes will be very similar. However, you will not be able to use administrator credentials for your Destination endpoint, and will instead be using end user credentials. For more information see Why does my Document Migration keep failing with Office 365 Small Business Tenant?

Note: We no longer support migrations to or from GoDaddy-hosted OneDrive.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare Source Environment

Create a Box user account that will be used for the migration, and grant main administrator privileges to that user. For more information see Transferring Admin Privileges to Another User.

Create a list of the Box user accounts that need to be migrated from the Source. This can be done by exporting the list of Box user accounts to a CSV file. Box has instructions to run various reports on this page. It may also be possible to use these instructions: From the administrator console, click the Users and Groups icon. Under the Managed Users tab, click Export Users.

Prepare Destination Environment

Create an administrator account in Office 365 to be used for migration, or use the global administrator account for the tenant. For more information see How do I create an administrator account in Office 365, and then use this during migration? Important: The administrator account must have a full license assigned to it, in order to be able to provision OneDrive profiles for each user during the migration process.For more information see Personal Site is not instantiated = PermissionsUserNotLicensed

Set up App-based Authentication. For specific instructions, see App-Based Authentication.

Set up accounts on Office 365, and assign licenses. These can be created in several ways.

Manually, one at a time.

By bulk import, via CSV file. See this article for instructions on creating a CSV of user information: Microsoft instructions.

By PowerShell script. See this Microsoft article for more information: TechNet article

By DirSync, AAD Sync or AAD connect. For more information see How do I synchronize my Azure Active Directory objects to Office 365?

Notes:

MigrationWiz can provision a OneDrive (SharePoint) profile for each user being migrated, if the user does not already have a OneDrive profile created. However, it does not create the user accounts; they need to have already been created.

MigrationWiz cannot provision a OneDrive profile for blocked users. If a user is blocked, this will result in a provisioning or access error.

MSPComplete Steps

Create the customer. For more information see View, Add, and Edit Your Customers

Create the Box Source and Office 365 Destination endpoints. View, Add, and Edit Customer Endpoints.Notes:

When setting up the Box endpoint, leave the radio button for Provide Credentials selected.

The OneDrive for Business endpoint will be set up using the App-based Authentication created during the Prepare the Destination steps.

Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. Refer to these articles for more information:

How do I purchase licenses?

Migration License Types

Apply User Migration Bundle licenses to the Customer's Users

MigrationWiz Steps

Create the Document Migration project. Read the How do I create a new migration project? article for more information.

After creating the project, click the Save button. This will take you back to the Authorization page. Click the Request Access Token button. Enter the email address of the Box.com administrator, and the password of this Box.com account. Click the Authorize button. Click Grant Access to Box. Once the Source Authorization completes, click Save Project.

Add the accounts (items) that will be migrated to the project. For more information see How do I add items to my migration project?

Set the Project Advanced Options. For more information see What project Advanced Options are available?

Under Support/Support Options add:

InitializationTimeout=8 - This increases the initialization timeout window to eight hours. For more information see Cannot get folders from My Drive.

RenameConflictingFiles=1 - This automatically rename the files that have the same name. This will rename the files to their original file names, followed by an unique identifier hash so it does not interfere with the original name and search. For more information see How do I migrate multiple files with the same name into OneDrive?.

If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information on this setting, see MigrationWiz - SyncItems Migration Option. Note: There are no spaces on either side of the "=" sign, and the entries are case-sensitive so pay special attention to the capital letters in the commands above.

BitTitan has no limitations to the number of Folders per migration. Any folder limits will be set by Microsoft.

Run Verify Credentials. For more information see How do I verify credentials?

Notify users that a migration is occurring. Send email to all users letting them know the time and date of the migration. During this time, they should not modify any documents in their Box accounts, because any modifications will not be included in the migration.

Perform the migration, using one of the following strategies:

Full Migration strategy. For more information, see How do I start a migration?

For small migration projects that are less than 50 users, we recommend a Full Migration strategy. This is a single, full-pass migration.

Pre-Stage Migration Strategy:

Pre-Stage pass. For more information, see How do I start a migration?

Full (Delta) pass. For more information, see How do I start a migration?

For large migration projects that are more than 50 users, we recommend Pre-Stage Migration strategy. This is a multiple-pass migration.

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? for more information.

Post-Migration Step

To prevent users from inadvertently logging in and using their Box accounts, decommission the Box user accounts, or change their passwords.

How do I find the URL for my SharePoint Library or OneDrive for Business?

Answer:

You can find the URL from the Microsoft Admin Portal.

The steps to find the specific URL are below:

Log into your Microsoft Admin Portal with your Administrator credentials. Use the same Administrator credentials as you are using the in tenant for which you are setting up the endpoint; i.e., use the source Administrator credentials to log in if you are setting up the source endpoint, or the destination credentials if setting up the destination endpoint.

Click on Admin.

Click on Admin centers on the left. (You may need to click Show More to see Admin centers.)

Click on SharePoint.

In the SharePoint admin center, you will find a list of the URLs.

For SharePoint endpoints select the URL that contains your Document Library.This may be different than the actual name that has been set for the Document Library. The examples below help explain this:

If the document library is named "Documents" and the URL is listed as "xxxxxx.sharepoint.com/Documents/", enter Documents as the document library name.

If your document library is named "Documents" but the URL says "xxxxxx.sharepoint.com/Shared Documents/", the name of the document library that needs to be entered is Shared Documents.

For OneDrive for Business endpoints select the URL containinghttps://XXXXX-my.sharepoint.com where XXXXX is the domain of the Destination tenant.

Howdo Iprevent Outlook from asking for credentials, after manually creating an Outlook profile?Answer:If Outlook profiles are created manually or by using Exchange AutoDiscover, usersmay beprompted for theirExchange credentials when launching Outlook.Inthese cases,aWindows Security dialog box will pop up after Outlook launches, as in the screen shot below. Normally this can be fixedby checking theRemember my credentialscheckbox after entering your credentials, and clicking theOKbutton.

However, in somecases, it asks for Exchange credentials every time when launching Microsoft Outlook, but there is no option forRemember my credentialsin theWindows Security dialog box. To prevent Microsoft Outlook from asking for Exchange credentials each time when launching, you can change some Exchange settings underAccount Settings.Follow these steps:

Open the Account Settings dialog box:

In Outlook 2007,clickTools>Account Settings.

In Outlook 2010+, clickFile>Info>Account Settings>Account Settings.

In the Account Settings dialog box,go to theE-mailtab >click to highlight the Exchange account that asks for logon credentials every time Microsoft Outlook is opened> click theChangebutton.

In the new dialog box of Change Account, click theMore Settingsbutton.

In theMicrosoft Exchange dialog box, go to theSecuritytab > Uncheck the optionfor

Always prompt for logon credentials > click theOKbutton.

At theChange Account dialog box,click on theNextbutton > click ontheFinishbutton.

Click theClosebutton to exit the Account Settings dialog box.

Introduction

This is the complete onboarding task flow for migrating mailboxes from one Office 365 tenant to another Office 365 tenant.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

This guide is only valid if the domain name is staying the same at the Destination. If the domain name is changing, refer to the Office 365 to Office 365 Migration Guide - While Changing the Domain Name.

The MSPComplete section includes the steps to deploy the Device Management Agent (DMA) to users. This is an Agent which includes modules for HealthCheck for Office 365 and DeploymentPro. Deploying DMA to end users is a prerequisite if you will be using HealthCheck for Office 365 and/or DeploymentPro. The steps for HealthCheck for Office 365 have been omitted from this guide because your end users are already using Office 365.

DeploymentPro can be used to configure the Outlook mail profiles after the migration. Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 resolution without user interaction.

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Office 365 to Office 365 migrations that are keeping the same domain name differ from the standard approach followed in other migration guides, because Microsoft only allows a domain to reside in one tenant at a time. For this reason, the following extra steps are included in this guide:

Adding a recipient mapping, under Advanced Options, to ensure that all email retains the ability to be replied to, post-migration.

Removing the domain from the Source tenant.

Verifying the domain on the Destination tenant.

The users should first be added to MSPComplete using the vanity domain name. An MSPComplete subscription can then be added to each user. However, before beginning the migration, the user addresses should be changed to use the .onmicrosoft.com domain names at both the Source and Destination, rather than the vanity domain names. Notes:

There will be some email downtime with this migration due to the time required to remove the domain on the Source tenant and add it on the Destination tenant. This is because Microsoft only allows the same domain to exist on one Office 365 tenant at a time. Exchange Online Protection (EOP) can't route email for the domain during the period of time when the domain is removed from the Source tenant and added to the Destination tenant, assuming the MX record is pointed at EOP. This results in senders getting a non-delivery report (NDR). Read the Move domains and settings from one EOP organization to another EOP organization TechNet article for options to queue email during this time.

Use of RecipientMapping is always recommended but is mandatory if you delete the domain before you start your Delta migration pass.

Prepare the Source Environment

Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the How do I create an administrator account in Office 365, and then use this during migration? article for more information.

Test mailbox access. Note: Test access to the tenantname.onmicrosoft.com addresses, not to the domainname.com addresses. Make sure that the tenantname.onmicrosoft.com account is attached to each mailbox in Office 365. By default, it should be attached, but if not, it will need to be added as an alias to each account. This can be done through the Office 365 admin portal or via PowerShell scripts. Read the How do I test mailbox access? article for more information.

Prepare the Destination Environment

Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. Read the How do I create an administrator account in Office 365, and then use this during migration? article for more information.

Set up accounts on Office 365 and assign licenses. These can be created in several ways:

Manually, one at a time. Read the Add users individually or in bulk to Office 365 article from Microsoft for more information.

By bulk import, via CSV file. Read the Add several users at the same time to Office 365 article from Microsoft for more information.

By PowerShell script. Read the Create user accounts with Office 365 PowerShell TechNet article for more information.

By DirSync, AAD Sync or AAD connect. Read the How do I synchronize my Azure Active Directory objects to Office 365? article for more information.

Using the BitTitan Sync Tool. Read the BitTitan Sync Program article for more information.

Test mailbox access. Note: Test access to the tenantname.onmicrosoft.com addresses, not to the domainname.com addresses. Make sure that the tenantname.onmicrosoft.com account is attached to each mailbox in Office 365. By default, it should be attached, but if not, it will need to be added as an alias to each account. This can be done through the Office 365 admin portal or via PowerShell scripts. Read the How do I test mailbox access? article for more information.

Prepare the tenant to send and receive large mail items. Read the How do I migrate large mail items to Office 365? article for more information.

MSPComplete Steps

Create the customer. Read the View, Add, and Edit Your Customers article for more information.

Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints

article for more information.

For the Source endpoint:

Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.

Click the Provide Credentials radio button, and enter the admin account credentials. Notes:

This should be a global admin account. If creating a separate admin account for the purpose of migration, refer to the Office 365 section in the How do I create an administrator account for login? article.

You should use the tenantname.onmicrosoft.com address, for the admin account domain name.

For the Destination endpoint:

Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.

Click the Provide Credentials radio button, and enter the admin account credentials. Notes:

This should be a global admin account. If you are creating a separate admin account for the purpose of migration, refer to the Office 365 section in the How do I create an administrator account for login? article.

You should use the tenantname.onmicrosoft.com address for the admin account domain name.

Add users to your MSPComplete customer. From your MSPComplete customer dashboard, click Users > Add Users > Add Users Through an Endpoint (Recommended).

Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:

How do I purchase licenses?

Migration License Types

Apply User Migration Bundle licenses to the Customer's Users

Deploy DMA to users. Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by either of these options:

Via Group Policy Object (GPO). Note: This is the recommended methodology because no end user interaction is required. Read the How do I deploy the Device Management Agent with a Group Policy Object? article for more information.

Via email. Read the How do I deploy the Device Management Agent through email? article for more information.

DeploymentPro Steps

Launch DeploymentPro.

Go to All Products > Device Management, then click on DeploymentPro on the far leftand follow the prompts to launch.

Select a customer from the list by clicking on the customer name. Note: The status column will show Enabled when a customer account has had DMA deployed to users.

Configure customer DeploymentPro module:

Enter the Domain.

Select the Destination endpoint.

Checkmark the Auto-populate box.

In the Client Interface Configurations section, upload your company logo and add supporting text. Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.

Save and continue.

Activate DeploymentPro module for users.

Either select all users (by putting a checkmark in the box to the left of the Primary Email column heading) or select the individual users (by putting a checkmark in the boxes to the left of the user email addresses). Note:DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.

Click the Schedule Cutover button.

Schedule profile cutover date.

Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutoverbutton. Notes:

The DeploymentPro module will install on user devices immediately and then run silently until this date.

The profile cutover date should be set to a date and time that is shortly after MX record cutover.

On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

MigrationWiz Steps

Create a Mailbox Migration project.Read the How do I create a new migration project? article for more information.

Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.

Add the accounts (also referred to as "items") that will be migrated to the project. Read the How do I add items to my migration project? article for more information. Important:

Select Add > Add from MSPComplete.Note: This will import the MSPComplete subscribed users into your MigrationWiz project.

Change the domain names for each user at both the Source and Destination to the tenantname.onmicrosoft.com.

To bulk change the Source addresses to the tenantname.onmicrosoft.com, follow the directions in How do I bulk change the domain name in migration email addresses? article. Note: This will be used for migration rather than the vanity name. This is important because, after the Pre-Stage migration pass, the vanity domain name from the Source must be removed. There will still be a Full (Delta) migration pass after domain removal, which is the reason for using the tenantname.onmicrosoft.com domain name.

To bulk change the Destination addresses to the tenantname.onmicrosoft.com, follow the directions in the How do I bulk change the domain name in migration email addresses? article.Notes:

This is the only domain name that initially exists on the Destination tenant, so it must be used during migration.

You can manually change source and/or destination addresses on a one by one basis, by clicking on the pencil icon on the right-hand side of the line item that you want to edit, and then changing the address in the email address field for either source or destination.

Set the Project Advanced Options. Read the What project Advanced Options are available? article for more information.

The following options are most valuable for this migration scenario:

Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. Read the How do I migrate to Exchange or Office 365 using impersonation? article for more information.

Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. Read the How do I migrate to Exchange or Office 365 using impersonation? article for more information.

If this is a large migration project, the value for maximum concurrent migrations, under Advanced Options, should be set to a maximum value of 25 concurrent migrations, in order to gauge the tenant migration capabilities. If successful, this value may be increased incrementally.

Under Support/Support Options, add the following: RecipientMapping="@sourcetenantname.onmicrosoft.com->@destinationdomainname.com" Read the How do I add Recipient Mappings to a project? for more information. Notes:

The RecipientMapping above is just an example; do not copy this verbatim. It needs to be changed to reflect the sourcetenantname.onmicrosoft.com account name and the customer Destination domain name.

More than one remapping expression can be used.

This is a very important step for Office 365 to Office 365 migrations. It ensures that emails have the ability to be replied to, even after the Full (Delta) migration has occurred because they will be mapped to the new destination domain name, rather than using the old sourcetenantname.onmicrosoft.com account name (- which will no longer be available, once the tenant is retired).

Run Verify Credentials. Read the How do I verify credentials? article for more information.

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration.

Pre-Stage pass: Select the users > Click the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. Read the How do I start a migration? article for more information.

Remove Domain from Source. Note: This should only be done after the Pre-Stage migration pass has completed. Typically, it is done late on a Friday night.

If you need instructions for removing a domain, refer to this document from Microsoft: Remove a domain from Office 365 Notes:

If there are several domains in the Source tenant being moved to the new tenant, all of them need to be removed.

In the admin portal, change the UPN of the admin account to the onmicrosoft.com address. Note: After domain removal, users will not be able to access their email, unless they know and log in with their tenantname.onmicrosoft.com email addresses.

After removal, wait 30 minutes for domain removal replication to complete.

Send an email to the users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to the Sample email to send to users before their Outlook profile is reconfigured article for some sample text and screenshots that can be included in this email.

Verify Domain at Destination. These actions are performed from within the Tenant 2 (Destination) admin portal.

Verify the domain in the Destination Office 365 account. We recommend the use of the wizard in Office 365 for this since once the domain is verified with the Text record, it offers to change all the users to the new Default Domain. Note: Since the domain was previously added to the account, all that needs to be done is to click the Verify button. If the domain is unable to be verified, and there is an error saying the domain already exists on another account, contact Microsoft Support at 1-866-291-7726 (US Toll-Free, other numbers are also available), and tell them that the domain needs to be manually deprovisioned from Forefront.

Confirm that every user has the Destinationdomain.com domain name added to their mailbox. Add if necessary.

The step above should have added the domain to every user. Download the add_new_domain.ps1 PowerShell script to check for this and add the domain name. This is only necessary if the users do not have the new default domain added to their account.

MX Record Cutover. On the DNS provider's portal, change the primary MX record to reflect the DNS settings for the new Office 365 organization. DNS settings to change include Autodiscover, MX, and SPF records. Also, remove the old settings for Tenant 1. These settings can be found in the Office 365 admin portal, by following these steps:

Inside Office 365, click Admin in the header.

On the Admin page, click Domains in the left pane.

Click the domain name to be set up, and then click the DNS Settings tab. This page lists the DNS records necessary to set in order to use the Office 365 services.

Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. This migration will complete quickly since most data is migrated during the Pre-Stage migration; Office 365 to Office 365 migrations have high bandwidth available. Read the How do I start a migration? article for more information.

Run Retry Errors. Read the How do I retry failed items? article for more information.

Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

If problems persist, contact Support. Read the How do I get support for your products? article for more information.

If not using DeploymentPro, users must create new Outlook profiles, and set up their signatures again, and reattach any PST files that were attached to their previous profile.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.

How do I import files from Azure into my MigrationWiz project?

Answer:

Once you havefiles in either BitTitan storage or your ownAzure storage account,you can add them to your MigrationWizproject by following these steps:

From your project dashboard:

Choose Quick Add to manually add the names of thefiles that have been uploaded into Azure into your project. If using Quick Add,define the full path to yourfiles (filename included), for example: Filename.pst or Foldername/filename.pst.

Notes:

Do notinclude the URL from BitTitanstorage.

File names in Azure are case-sensitive.

Or

Click on the AutoDiscover Items green bar to AutoDiscover,and import the names of thefiles from BitTitan storage. AutoDiscover is the recommended and easiest option to choose. The steps below provide more detail on using AutoDiscover:

Click on the blue Start Auto Discovery bar in the left-hand panel.

Once the PST files have been discovered,click on the green + Import Items button.

Now choose the Destinationto ingest each file into.For example,for PST migrations you will edit the Destination mailbox. To do this, follow the directions here. For OneDrive migrations, you will choose the Office 365 account to ingest into.

In order for DeploymentPro to configure Outlook to connect to Office 365, each device must meet these system requirements:

Microsoft Windows 7 or later (With latest Windows updates)

.NET Framework version3.5.1 or later (4.5 starting Jan 1st, 2019)

These versions of Outlook:

Microsoft Outlook 2016 (with March 2016 PU)

Microsoft Outlook 2013 SP1 (with December 2015 PU)

Microsoft Outlook 2010 SP2 (with October 2015 PU, April 2015 PU).Note: Read the Outlook Updates article from Microsoft for more information.

Additional Information

Linux and Mac operating systems are not supported.

Microsoft Outlook 2007 is not supported.

Microsoft Outlook 2019 is not supported.

Starting Jan 1st, 2019, .NET Framework 3.5.1 will not be supported anymore. Please install Windows Updates on your devices to automatically upgrade to a more recent version of the framework (at least 4.5).

How do I deploy the Device Management Agent through email?

Answer:

To deploy the BitTitan Device Management Agent (DMA) through email, you ask users to manually install the agent.

We recommend installing DMA through a group policy object because its automated and non-intrusive.

To deploy DMA through email:

Click Customers on the navigation sidebar.

Click the customer name for which you wish to deploy DMA.

Click Users.

Add a checkmark next to the user(s) that should receive the email.

Click the Enable Device Management Through Emailbutton.

In the Enable Device Management via Email panel, enter your email address in the Reply-To Addressfield.

Confirm that all of the users you chose are listed in the To field.

To personalize the email message that the customer's users will receive,type your changes into the message body text box.If the customer's computers use a proxy,you must addinstructions to run theDMA installer withcommand lineparametersthat ensure DMA is able to transmit data through the proxy. Read the How do I deploy the Device Management Agent on computers that use a proxy? article for more information.

Click Send AgentEmail.

The customers users will receive theemail asking them to manually install the agent.The users and their computer information will start populating in MSPComplete under the customers context soon after the agent is installed and running.

MSPComplete is your end-to-end solution for delivering managed IT services. This article guides you toward the informational resources youll need to use MSPComplete to its full potential.

Sections in this article:

Fundamentals

Manage your Subscriptions, Agents, Teams, and Workgroups

Manage your Customers, their Users, Groups, and Endpoints

Manage Runbooks, Services, and Tasks

Manage Customer Computers, Resources, and Gateways

Fundamentals

First, learn the basics of what MSPComplete does, how its laid out, and how it operates. After you have covered these basics, youll be ready to dive deeper.

Article

Description

Onboarding Guide: Get Organized

Get started with the MSPComplete Get Organized subscription plan.

Onboarding Guide: Get Automated

Review this onboarding guide for an initial set of steps and instructions to get you going with the Get Automated plan.

MSPComplete Features Overview

Overview of major features. Read this to get a sense of how you can use MSPComplete within your organization.

MSPComplete Subscription Plans

Overview of the MSPComplete subscription plans.

MSPComplete Interface Tour

Interface walkthrough that illustrates the panes, navigation elements, and forms used to enter information.

MSPComplete Hands-on Tutorial

This tutorial gives you hands-on experience with MSPComplete by walking you through structured exercises.

Using MSPComplete with MigrationWiz

Information for MigrationWiz users about updating practices to use MSPComplete effectively.

MSPComplete Glossary

Explanation of key terminology for MSPComplete.

Manage your Subscriptions, Agents, Teams, and Workgroups

MSPComplete is a multi-user system that all the IT professionals in your organization can use collaboratively: Subscriptions, Agents, Teams, and Workgroups Overview

From the articles listed on this landing page, youll learn how to:

Invite agents to join MSPComplete.

Organize people into teams to aid with service delivery.

Set up a billing method for purchasing subscriptions.

Purchase subscriptions for agents.

View information about the state of service delivery.

Manage your Customers, their Users, Groups, and Endpoints

With your team in place, youre ready to add customers: Introduction to Managing your Customers

Using the articles linked to this landing page, youll learn how to:

Bring on a new customer, using a variety of methods for creating user records.

Combine a customers users into groups to facilitate service delivery.

Create endpoints to upload customer information and manage cloud-based services.

View resource utilization information gathered from customer computers.

Manage Runbooks, Services, and Tasks

Youve assembled your team,you'vebrought customers onboard, now its time to get down to work: Runbooks, Services, and Tasks Overview

From these articles, youll understand how to:

Plan service delivery effectively.

Schedule tasks and run services.

Create Runbooks that can be customized and reused.

View the pending service tasks assigned to your IT professionals.

Manage Customer Computers, Resources, and Gateways

MSPComplete not only enables cloud-based services, but it also allows you to evaluate your customers devices: Introduction to Device Management

These articles explain how to:

Deploy the Device Management Agent to customer hardware.

Gather statistics on hardware inventory, operating systems, and browser versions.

Receive alerts about resource management before hardware problems become critical.

Evaluate customer resources to help ensure that cloud migrations go smoothly.

Shared mailboxes migrate ina similar wayto a regular mailbox migration.

If migrating with administrative credentials: Fromthe MigrationWiz dashboard,click on the Quick Add button, and enter the email address of the shared mailbox atthe Source, and the email address of the shared mailbox at the Destination. When the migration is performed, it will migrate with the administrative credentials added when creatingthe project. The administrator account must have full access permissions to the shared mailbox in order to perform the migration. If performing a Bulk Add of users,simply include the shared mailboxes intheCSV file that is used to import the mailboxes intothe MigrationWiz dashboard.

If migrating without administrative credentials: From the MigrationWiz dashboard, click on the Quick Add button, and enter the email address of the shared mailbox at the Source, and then the login name and password of either the owner of that shared mailbox or an account that has full access permissionsto the shared mailbox. Also enter the email address of the shared mailbox atthe Destination, and then the login name and password of either the owner of that shared mailbox or an account that has full access permissionsto the shared mailbox.

The screen shot below using the fictitious acme.com provides an example of how toadd theshared mailbox into the MigrationWiz dashboard, for the Destination.

Note: The login name and password can only be added if the MigrationWiz project is createdwithout administrative credentials.

Create a shared mailbox

Notes:

Refer to the article from Microsoft for more information about how to create and use shared mailboxes in Office 365.

As with a regular mailbox migration, it is necessary to purchase mailbox migration licenses or User Migration Bundle licenses in order to performthe migration.

Shared mailboxes make it easy for a specific group of people to monitor and send email from a common account, like public email addresses, such as [email protected] or [email protected]. When a person in the group replies to a message sent to the shared mailbox, the email appears to be from the shared mailbox, not from the individual user.

Shared mailboxes are a great way to handle customer email queries because several people inan organization can share the responsibility of monitoring the mailbox and responding to queries. The customer queries get quicker answers, and related emails are all stored in one mailbox.

Shared mailboxes are also ideal for storing the mailbox contents ofterminated employees.

It is not necessary to assign licenses to shared mailboxes in Office 365, except when they are over their storage quotaof 50GB.

In the back end, shared mailboxes are identical to user mailboxes. Look atthe user list; there will be a user created forthe shared mailbox.

How do I export a user list from Zimbra into a CSV file?Answer:Step by step:

Open Zimbra Admin.

Select Account.

In the Search box, type the domain name to be exported.

On the Toolbar Zimbra Admin, select the Download button.

Save the CSV file generated.

How do I checkwhich version of .NET Framework I have installed?

Answer:

You can check the version of .NET Framework installed on a computer by opening a command prompt, navigating to %windir%\Microsoft.NET\FrameWork, and then navigating to thedirectory with the latest version number. Once in the directory with the latest version number, run the command .\MSBuild.exe -version.

The above command will output the latest version installed in the following format:

C:\Windows\Microsoft.NET\Framework\v4.0.30319> .\MSBuild.exe -version

When the command is entered, the following information will appear:

Microsoft (R) Build Engine version 4.6.1038.0

[Microsoft .NET Framework, version 4.0.30319.42000]

Copyright (C) Microsoft Corporation. All rights reserved.

The last line, after the copyright,will output the most recent verson of .NET Framework on your computer, for example, 4.6.1038.0.

How do I assign the elevated admin role 'Organization Management' to the administrative account that is performing a Public Folder migration?Answer:When setting certain fields in Exchange, the user performing a migration needs to be assigned the correct permissions through assigned admin roles. In most cases, the admin role for migration is relatively straightforward. For Public Folders, however, the role is not so obvious.In most cases, the assumption is that simply creating a new admin role and assigning the 'Public Folders' and 'Mail Enabled Public Folders' roles to the group would allow any users in that group to have full access to the Public Folders and be able to set all of the appropriate fields. However, this is not the case. In terms of read-only fields, such as the received date, simply having these two permissions is not enough. If these are the roles set, and if a read-only field such as the received date is set in the message being migrated, it is ignored and the current date and time are set instead of the value passed in.In order to allow read-only fields to be set, an elevated admin role has to be assigned to the user performing the migration. The role that is recommended is 'Organization Management', which provides all of the necessary permissions to set fields like the received date without any problems.Click here to learn more about the Organization Management role, and how to add it.This can be set via the Exchange Administration Center (EAC) or via PowerShell.Via Exchange Administration Center:

In the Exchange Administration Center (EAC), navigate to Permissions > Admin Roles.

Select the group: Organization Management and then click on Edit How to Add a User or Group to an Administrator Role.

In the Members section, click on Add.

Select the users, USGs, or other role groups you want to add to the role group, click on Add, and then click on OK.

Click on Save to save the changes to the role group.

Via PowerShell:The PowerShell command to add this is:Add-RoleGroupMember "Organization Management" -Member username

Notes:

To migrate from Exchange 2007, elevate the permissions of the admin to be part of the Exchange Organization Administrator role. To add the user to the role, follow the TechNet article .

If migrations are performed with an account that does not have this elevated admin role level assigned, then the received date will change to the current time, after the migration of Public Folder content.

How do I migrate from MDaemon?Answer:

At this time, we can only migrate from MDaemonusing IMAP.Review your MDaemonconfiguration to determine the appropriate server name and port to use with your migration.

What are some best practice guidelines for migrating from G Suite or Gmail?

Answer:

Here is what you need to know about migrating from G Suite orGmail:

IMAP access needs to be enabled for all users. Follow the steps in the Turn POP and IMAP on and off for users article from Google. Bandwidth limits for accounts

Contact and calendar services need to be turned on for all users. Follow the steps in the Control who can access Google services article from Google.

If migrating from free Gmail or non-paid G Suite accounts:

Unfortunately, migrating any Google free accounts is not supported due to recent changes in Google Security policies.

If migrating from G Suite for Business or Education, thenenable OAuth administrative credentials to avoid Google lockouts and having to provide each end user's credentials.Read the Enable access to G Suite using OAuth 2.0 article for more information.Note: When setting upthe migration project, and choosing G Suite as either the Source or Destination, it is necessary to addalldomains that will be migrating from, orto, G Suite. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, you mustensure that both of these are added under Your Domains when setting upthe project in MigrationWiz.

Review howitems are migrated to Exchange/Office 365:

Folders:

Read the Why was my Sent Items folder not migrated to the correct folder at the destination? article for more information about applying folder re-mappings.

Email:

Read the How are Google labels converted and migrated? article.

Calendars:

Read the What calendars are migrated with my account? article.

Contacts:

Read the How are Google contact groups migrated? article.

Read the What options are available for migrating G Suite/Gmail suggested contacts? article to learn how to migrate G Suite/Gmail suggested contacts.

Be aware of G Suite throttling when retrieving data. Google may lock your account for 24 hours if they consider that too much data has been retrieved from their servers in a given amount of time. MigrationWiz adjusts migration throughput accordingly but remains subject to those limits. Read the article from Google for more information.

MigrationWiz does not have a limit for the length of a label name. However, G Suite limits the length of label names to 225 characters.

G Suite calendar items can have multiple reminder notifications. For example, a calendar item can have three reminders: the first reminder at 30 minutes before the meeting, the second at 15 minutes before the meeting, and the third at 5 minutes before the meeting. In Office 365 and Outlook, calendar items have only one reminder; therefore, MigrationWiz will migrate only the first calendar reminder. In the example, then, the only calendar reminder that will be migrated is the one that appears 30 minutes before the meeting.

G Suite calendar item titles (subjects) that are over 255 characters will be truncated in Office 365. For example, a calendar item with a title that is 403 characters long will be cut down to 255 characters in Office 365.

Create a Windows Installer Package (MSI) to deploy the Device Management Agent

Answer:

You can create an MSI package for DMA by following the steps below. This can then be deployed via a Group Policy Object (GPO), or via a software deployment tool, such as SCCM.

Prerequisites

Download the DMA setup file from MSPComplete.

In MSPComplete, clickAll Customersfrom the navigation sidebar.

Click on the customer name for which you wish to deploy DMA.

On the horizontal menu bar, click Users.

Click Add Users, and then clickAdd Users via Device Management Agent.

On the Add Users via Device Management panel, clickDevice Management Agent setup fileto download the DMA setup file to your local drive.

Step 1: Download MSI Wrapper

Choose a tool that allows you to convert an executable setup program into an MSI package. In the example below, we guide you through the steps when using the freeware software from Exemsi.com.

Important: This is athird-party utility that is not owned or supported by BitTitan.

Download and install the free version of MSI Wrapper from http://www.exemsi.com/

Step 2: Run MSI Wrapper

the KB article here

Step 3: Select the BitTitanDMASetup_xxxxxxxxxxx_.exe installer file.

Step 4: Get a GUID for the MSI application.

Get a GUID from https://www.guidgenerator.com/online-guid-generator.aspx

Copy and pastethe GUID into the Application ID field (in MSI Wrapper application) and Click Create New'for Upgrade Code.

Step 5: Accept default information for the Properties and More Properties screens.

Step 6: Proxy Information (if needed).

If DMA needs to use a proxy, enter the command lineas described in to the Install Arguments field. Otherwise, leave the field blank.

Enter -uninstall for the Uninstall Arguments.

Step 7: Verify and Build.

Once you have builtthe MSI package, it can be deployed via a GPO, or via a software deployment tool, such as SCCM.

How does MigrationWiz prevent duplicates?

Answer:

MigrationWiz uses a system of watermarks to track items that have previously been migrated.There are a number of advantages to using watermarks instead of detecting items by their names, titles, or other properties.

How are watermarks created and stored for later use?

As items are migrated, a small watermark is embeddedin the header of eachitem, allowing us to track it once it resides inthe Destination.This watermark alsospecifies certain information, such as the endpoint type specified in MigrationWiz.

At the same time, we place a matching watermark in one of our databases.We do not store any content data from theitem,only the watermark data.Our databaseholds the items that have been migrated, andprevents items from being remigrated if they are deleted by users at the Destination.

Because we track watermarks in two different places, there is a double layer of protection against the creation of duplicates.

How does MigrationWizuse these watermarks during delta passes?

When a Delta Migration begins, we scan the Destination for watermarks so we will know what data has been migrated. We will also scanour watermark databaseto prevent remigration of items thatwere deleted or moved at the Destination, between passes. This scanning process occurs at the beginning of every Delta pass. The larger the quantity of data migrated,the longer this process will take. For example, a migrationthat previously transferred 20GB of data will generallytake longer to scan for watermarks than a migration with 20MB transferred.

We do not migrate watermarked items a second time. Only items found without a watermark will be migrated.

What happens to items at the Source?

We do not modify any data at the Source, includingwatermarks.

How do I delete thesewatermarks?

If a user manually deletes a migrated item from the Destination, we will not migrate this item because we still track it onthe backend.

To delete our end of the watermarks database, simply checkmark the box next to the migration you want to do this for, and click the circular Reset Items button on the toolbar at the top of the user list. This will only clear our end of the database.

If you would like to delete watermarks stored at the Destination, you will need to delete the items themselves, as the watermarksareembedded in theitem headers. This is typically only done when choosing to restart your migration from scratch. Deleting items at the Destination will only clear the Destination watermarks. Unless you reset watermarks on our end, items deleted from the Destination will not be remigrated.

To learn more about resetting items and item statistics, see resetting item statistics.

What else should Ibe aware of?

Because we use proprietary watermarks that are specific to our system, we will not be ableto detect items migrated by other means. For example, items forwarded from the Source to the Destination -- and items migrated by other solutions -- will not contain our watermarks. Therefore, we have no knowledge of them existingat the Destination. As a result, we will migrate these items even if they are already at the Destination.

Since we store the endpoint type in the watermark, changing the Source orDestination endpoint type in between passeswill effectively void the watermark, and all items will be migrated again. If this happens, we will generatea new watermark in each item, based on thenew Source or Destination endpoint type.

If an item at the Source is moved in between passes, we will not be able to match the Source item with its Destination counterpart, so the item will be migrated a second time. It will then exist in each location,in its original location andalso in its new location.

Important:Only Collaboration projects created after December 8, 2019 will be able to see the new action menu option to Select Teams. For projects created before December 8, 2019, the project can be cloned or recreated as a new project to make use of the new options.

After running an Assessment, it is possible to use a MigrationWiz-generated CSV to select which teams are included in the migration.

To use this functionality, follow the steps below.

Open the Collaboration project that needs specific teams selected.

If an Assessment has not already been completed, run an Assessment.

After the Assessment completes, click on the Actions button and click on Select Teams.

From the flyout menu, click on Assessment Summary CSV File.

When the file finishes downloading, open the file and edit only the first column, titled Selection (true/false).Notes:

All teams with TRUE in the Selection column will be included in the migration. To exclude a team from the migration, change TRUE to FALSE. A blank cell will be treated as a FALSE.

Do not change any other information in the CSV file. Changing other fields will cause the team selection to fail.

Save the modified CSV.Note: The file must remain in .csv format and must not exceed 5MB.

The new CSV is then uploaded to the project in the same flyout menu that it was downloaded from. The upload entry field is shown at the bottom of the flyout menu.

Click Select File.

Find the modified CSV on your computer and select it.

Click Import. The Assessment results for the project will be updated to reflect only the teams now selected for migration.

When ready, click Start Migration.

After the migration completes, verify on the Destination tenant that only the specified teams have been migrated.

Notes:

After uploading the CSV file, a new option will show under the Actions menu.

Clear All Selections This option will clear the updated CSV list, resetting the migration back to the default, which means all teams will be selected for migration.

Selecting Run Full Assessment after uploading a modified CSV will also clear the updated CSV list and reset the migration back to the default of all teams being selected for migration.

If any team names have special characters, such as emoji icons, Excel may not be able to open the generated CSV file. The steps below may allow the CSV file to be imported:

Open Excel.

Import the data using Data--> Import External Data --> Import Data.

Select the file type of "csv" and browse to your file.

In the import wizard change the File_Origin to "65001 UTF" (or choose correct language character identifier ).

Change the Delimiter to comma.

Select where to import to and Finish.Note: While these steps should work for most versions of Excel, some versions may still not be able to open the CSV.

Why am I getting Path Too Long errors when migrating to OneDrive?

Answer:

When migrating to OneDrive, the path length limitation is a common issue. OneDrive has several limitations:

A given element (file or folder) cannot be more than 128 characters.

A total file path including full path + file name cannot be more than 260 characters.

All of them have to be URL encoded, so many characters count as 3 characters, so the limit can be reached faster that we first expect.

It is, however, not always clear why the errors arise when the path actually seems small. So lets assume the following environment:

Domain: domain.com

User: [email protected]

Folder: /folder

File: this & that.docx

One would assume that the file is /folder/this & that.docx, 24 characters.

However, when using the API, we have to use the complete OneDrive path, which is this case would be:

/personal/test_user_domain_com/Documents/folder/this & that.docx

This is 64 characters.

We also have to URL encode this string:

%2Fpersonal%2Ftest_user_domain_com%2FDocuments%2Ffolder%2Fthis%20%26%20that.docx

We're already at 80 characters out of the 260-character limit.

When applying file permissions, we need to use the full file path to the file, which is even longer:

https://domain-my.sharepoint.com/personal/test_user_domain_com/Documents/folder/this & that.docx

Then we URL encode this, ending up with the following:

https://domain-my.sharepoint.com%2Fpersonal%2Ftest_user_domain_com%2FDocuments%2Ffolder%2Fthis%20%26%20that.docx

This is 112 characters, when the file appears to be only 24 characters.

Use the Advanced Option in MigrationWiz to enable the use of 400 characters for the file path name. For more information, see What would I use the Advanced Option IncreasePathLengthLimit-1-for?

How do I verifycredentials?Answer:

You may verify the credentials of items in MigrationWizwithout migrating data or consuming any licenses.

Sign in to your MigrationWiz account.

Open the Project containing itemsyou wish to validate.

Select the itemsyou wish to validate.

Click onthe Start button in your dashboard.

Select Verify Credentials from the drop-down list.

Once complete, the results of the verification will be shown in the Status section.

BitTitan DeploymentPro is a module of Device Management and the Device Management Agent (DMA) that remotely configures Outlook email profiles after you perform a mailbox migration to Microsoft Office 365.

DeploymentPro configures Outlook email profiles to the new Destination server and moves users AutoComplete, email signatures, and PST files to the reconfigured email profile. However, DeploymentPro does not set the users default email signatures for new messages, replies, and forwards.

Sections in this article:

Prerequisites

Confirm that the users computers are successfully running DMA

Configure the DeploymentPro project

Schedule the Users

Next steps

Prerequisites

Complete these prerequisites before you get started with DeploymentPro:

Create the customer in MSPComplete. Read the View, add, and edit your customers article for more information.

Create the Destination endpoint in MSPComplete. Read the View, add, and edit customer endpoints article for more information. The Destination endpoint requires admin credentials to be entered so that you can selectthe endpointfrom the endpoint drop-down menu.

Review the system requirements for DMA and for DeploymentPro. Read the What are the system requirements for DeploymentPro? article and the Introduction to Device Management article for more information.

Install DMA on the customers computers for the users who will need their Outlook email profiles reconfigured. For more information, read the DMA installation articles listed below:

Install DMA on computers using an email request to Users

Install DMA on computers using an Active Directory Group Policy Object

Install DMA on computers that use a proxy

Install DMA on terminal servers

Important: With respect to HTTP authentication, DeploymentPro supports only "Basic" authentication. For more information, see Understanding HTTP Authentication.

Confirm that the users computers are successfully running DMA

After DMA is installed on the user'scomputers, you must ensure that the users who will need their Outlook email profiles configured by DeploymentPro are listed in MSPComplete with a successful (Success or Timed Out) agent status.

Complete these steps to confirm the users running DMA:

Select the appropriate workgroup, and then click All Customers in the left navigation pane.

Click the name of the customer for which you want to view users.

Click the Users tab.

Scroll through the list of users to identify users who are listed with a successful, an unknown or failed agent status, or with a .local, .corp, .internal, or other private network address.

Success means that the user is logged in and the DMA is communicating with our servers.

Timed Out means that the user has been logged in and DMA was communicating with our servers, but the user has been logged off for more than 4 hours.

Failed means that the DMA was not able to be installed. Usually, there is a security program or policy blocking the agent installation.

Not Installed means the DMA installer has not been run or this is a duplicate user entry. Duplicates happen when the agent is installed but is not able to match the user profile with the email address in the Users List.

Users with a status of Failed or Not Installed will not have their Outlook email profiles reconfigured by DeploymentPro.

If these users need to have their Outlook email profiles reconfigured by DeploymentPro, then you need to install DMA to those users' computers. If you have already tried to install DMA to those users' computers, then try to reinstall it using an alternate method. For example, if you previously tried to install DMA using a Group Policy Object (GPO), you might try re-installing it with an email instead, in case those users are not using domain-joined computers. You might also want to try performing a few troubleshooting steps as outlined in the Troubleshoot connectivity between DMA and MSPComplete article.

Note: When you go to the DeploymentPro page you will only see the users that have DMA installed successfully (Success or Timed Out status). These are the only users that will have their profiles configured.

Configure the DeploymentPro project

After the users running DMA have been confirmed, its time to configure the DeploymentPro project under the Device Management section of MSPComplete.

Note: DeploymentPro is currently supported only for Office 365. If using DeploymentPro with Exchange (either On-Premises or Hosted) as a Destination, then a Proof of Concept should be run first. For more information, see What Destination systems are supported by DeploymentPro?

Complete these steps to configure the DeploymentPro project:

Select the appropriate workgroup, and then click the products icon ( End user experience when DeploymentPro reconfigures their Outlook profile ) in the top navigation bar.

Click DeploymentProin the list of products.

Click the name of the customer for which you want to configure a DeploymentPro project.

Click Save and Continue.

The DeploymentPro page is refreshed to list the email addresses for the customers users who are successfully running DMA and who are ready to run the DeploymentPro module. If the DeploymentPro module has not yet been set up, the set up screen will load for configuration of the module.

Configure the DeploymentPro Email

The DeploymentPro page is refreshed to list the email addresses for the customers users who are successfully running DMA and who are ready to run the DeploymentPro module. If the DeploymentPro module has not yet been set up, the setup screen will load for configuration of the module.

Destination Domain Name: Enter the customers email domain.

Select Destination Endpoint: Select the Office 365 Destination endpoint. This endpoint must have Admin credentials entered.

Autodiscover URL: The Autodiscover URL auto-populates for Office 365, but must be manually filled in for other destinations. For more information see How do I find the main AutoDiscover URL and Certificate Principal Name for my Hosted Exchange provider?

Certificate Principal Name: The Certificate Principal Name auto-populates for Office 365, but must be manually filled in for other destinations. For more information see How do I find the main AutoDiscover URL and Certificate Principal Name for my Hosted Exchange provider?

Expired or Temporary Password Settings: Choose the password setting that applies to your customers environment:

ChooseEnable users with temporary or expired passwords to set their own passwordsif your customer uses Office 365 to manage user accounts and password policies. With this setting selected, the DeploymentPro wizard that runs on the customers computers will prompt users to enter a new password when their password is expired or set to temporary. DeploymentPro automatically updates Office 365 with the password that users enter. Important:Users must know their current expired or temporary password.

ChooseDo not allow users to set their own passwordsif your customer manages their user accounts and password policies using ADFS. With this option selected, all user password resets are managed by the companys IT department. Enter the following information into the DeploymentPro Module Configuration form:

Upload Logo: ClickUpload Logoto upload your companys logo for use in the DeploymentPro wizard that runs on users computers. For more information see What are acceptable specifications for the logo used by DeploymentPro?

Message: Enter a message to display a customized note in the DeploymentPro wizard that runs on users computers.

Schedule the Users

After the DeploymentPro project is configured, we recommend that you schedule the users as soon as possible even if the email cutover (MX record cutover) won't happen for some time. Read the Troubleshoot DeploymentPro article for more information.

Complete these steps to schedule the DeploymentPro module:

Select the appropriate workgroup, and then click All Customers in the left navigation pane.

Click the name of the customer that you wish to schedule.

Click the Manage button in the top right corner of the page, and then select Device Management.

Click DeploymentPro in the left navigation pane.

Add a checkmark next to the email addresses for which you want to run the DeploymentPro module, and then click Schedule Cutover.Note: We recommend running a proof of concept on a few test accounts. Read the Test DeploymentPro with a couple of users article for more information.

In the Select a Date field, select a date and time for the DeploymentPro wizard to run on user computers. This date and time should happen soon after the email cutover (MX record cutover) date and time.Note: If you havent identified the email cutover date, then select a date far in the future (i.e., a few months later than the expected cutover date). When you do this, you should also set a reminder for yourself to return to the DeploymentPro page and reschedule the date and time for the DeploymentPro wizard once you've identified the exact date and time for the email cutover.

Click Schedule Cutover.Note:To run the DeploymentPro module, you must either have DeploymentPro licenses available on your account or have applied User Migration Bundle licenses to each user. Refer to the View, purchase, and edit subscriptions article and the Apply User Migration Bundle licenses to the Customer's Users article for more information. Standalone DeploymentPro licenses, if any are available on your account, are consumed automatically when an unlicensed user is scheduled.

After DeploymentPro is scheduled, and before the scheduled start date/time, the email addresses should be in the "Scheduled" phase in the DeploymentPro page. When the scheduled start date/time is reached, the email addresses will be in the "Running" phase. If some of the email addresses listed don't progress to the "Running" phase, then you may need to perform some troubleshooting actions to get them to the appropriate phase.Read the Troubleshoot DeploymentPro article for more information.Note: Scheduled time is based on the local time of the machine that is scheduling the request.

Next steps

Perform the mailbox migration. Follow the steps in the appropriate migration guide for your customers Source and Destination.

Soon after the email cutover date and time, the DeploymentPro wizard will guide the customers users through the configuration of their Outlook email profiles. As users complete the DeploymentPro wizard, their email addresses will progress to the Completed phase on the DeploymentPro page. Read the for more information.

BitTitan uses app-based authentication for SharePoint, OneDrive for Business, Office 365 Groups (Documents) migrations, and Teams migrations. This provides greater security and reduces the potential of Microsoft throttling. It replaces the previous Office 365 authentication, which has been subject to increased throttling by Microsoft. This app-based authentication method is specific for Office 365 tenants.

Important: This app must be added in both .microsoftonline.com tenants (Source and Destination) to reduce the throttling and failures due to Microsoft throttling policy changes.

If this app is not added on both tenants, MigrationWiz will attempt to create a temporary substitute app in the tenants to be used for authentication. We do not recommend relying on this substitute app creation, as this behavior will only be a temporary transitional behavior within MigrationWiz. To avoid potential interruptions or failures in migrations, it is strongly recommended to set the app up in the tenants.

The steps for creating and removing this app are below.

Add the App to the tenant

Post Migration Steps

Add the App to the tenant

Step 1:

Visit the following URL and sign in as the administrator user:

For Teams migrations: https://login.microsoftonline.com/common/adminconsent?client_id=e541adb0-93aa-4053-a1e3-04692035881d&state=12345

For SharePoint or OneDrive migrations: https://login.microsoftonline.com/common/adminconsent?client_id=e7c20566-14a7-4722-acd1-396f7268ea1a&state=12345

Do this for both Source and Destination tenants.

Step 2:

Authorize the App for both Source and Destination tenants.

Click on the Accept button.

Post Migration Steps

To remove the BitTitan Enterprise app, perform the following steps:

Launch PowerShell.

Connect PowerShell to Office 365.

Enter the command:

Connect-AzureAD

Enter the admin credential in the prompt.

Enter the command:

Get-AzureADServicePrincipal -SearchString Migration

Look for the ObjectId of the app you want to remove and enter the following command:

Remove-AzureADServicePrincipal -objectId <the object id>

The following steps are recommended before setting up or running a Collaboration project to help reduce the number of errors or delays that might be encountered.

Before a Migration

Ensure that the users are all set up and licensed on the Destination (MigrationWiz does not create or license the users). We recommend setting up the users several hours prior to the migration, as Microsoft can take up to 24 hours to complete user setup in a tenant.

The administrator account on the destination must be set up without a federated account.

ADFS and Multi-Factor Authentication turned off for the administrator accounts on both the Source and Destination before starting a Collaboration migration.

Add the Administrator account as an owner to the teams on the Source and the Destination. Do this at least 24 hours ahead of the migration testing, to avoid possible delays in permission setting.

Assessments are required for Collaboration migrations. They cannot be skipped. Assessment completion typically takes about thirty seconds per Team; however, speeds are affected by several external factors and the assessment may take longer to complete. These external factors include, but are not limited to, current server demand, the size of the Teams on the Source server, and available bandwidth. You can read more about potential factors in our article How long does a migration take?

To prevent users from updating or using specific Teams while the migration is ongoing, it is possible to archive the team on the Source for the duration of the migration. This will prevent changes to the Team and its channels.

By default, we match users from the Source to the Destination based on the email prefix in their SMTP address. For example, if the user email is [email protected], we match the name portion. If there are multiple people with the same email prefix at the Destination (e.g. [email protected] and [email protected], or the email prefix of a particular user is changed in the destination (e.g. [email protected] [email protected]), it will be necessary to use the advanced option UserMapping="[email protected]>[email protected]" to set the new or correct name for each user. For instructions on adding this option, see How do I add support options to a project or to a single item? Note:The Usermapping command goes in the Support Options section and will require one line per user that needs mapping. Click the + to add additional lines.Replace the email addresses in the example with the actual user email addresses.

During a Migration

MigrationWiz is not an updating tool. Once a Collaboration project has been started, we recommend that you do not rename any Channels at the Source. If Channels need to be renamed, they should be renamed before an initial Assessment is run, or after all teams have been successfully migrated to the Destination tenant. If a Channel is renamed between when the initial Assessment is run and the final migration has completed, some files may end up in incorrect Destination locations.

Conversations that are migrated, then updated on the Source, will not be updated on the Destination when the migration is run again. Because of this, it is best to plan to do this migration in a single migration pass, generally over a weekend or a planned down time.

If conversations are updated during the course of the migration, the migrated files will need to be deleted from the Destination tenant. The project will need to be reset from the Action menu, the assessment will be run again, and then you can migrate the files again.

Alternatively, it is possible to delete only the updated conversation from the Destination, adding a filter to the project to migrate only that specific conversation. After the project has been reset, run the migration again. To add a filter, use the instructions in the article How do I filter a Folder? The team name will be used for the filter. For example, if the specific team is called Team_Alpha and the specific channel is called Project_ChitChat, then the filter used to migrate only this channel would be ^(?!Team_Alpha/Project_ChitChat)

Note:To add filters or mapping to a project, clickEdit Project and selectAdvanced Options.

After a Migration

If a migration completes successfully, but not all members show on the Teams destination, the users may be taking extra time to sync. This can happen when a Team has a large number of users. It is possible to verify that all the users were migrated by logging into the Office 365 Admin portal, going to the migrated group (Team), and viewing the members list to verify that the expected number of members were migrated. This should be synced to the Teams interface within the next few hours.

After the migration is completed, remove the MigrationWiz App Authentication with the instructions here.

You can run the BitTitan DeploymentPro module for a few users at a time in MSPComplete. However, it is more efficient to use PowerShell to run the DeploymentPro module if you must do it for 100 or more users. This method is also recommended if the destination domain varies for different users, because you candefine various destination domains using a comma-separated value (CSV) file. This article guides you through the steps to use PowerShell to run the DeploymentPro module.

Sections in this article:

Prerequisites

Create a CSV file of users for DeploymentPro

Run the Start-DeploymentProUserBatch PowerShell script

Next steps

Prerequisites

Complete these prerequisites before you use PowerShell to run the DeploymentPro module:

Download and install the BitTitan SDK. For more information: Read the How do I install the BitTitan SDK?

Configure your DeploymentPro project in MSPComplete. For more information: Read the DeploymentPro Guide. The process outlined in this article replaces the steps to run the DeploymentPro module.

Download the Start-DeploymentProUserBatch.zip file, which contains a CSV file and the PowerShell script file (PS1).

Create a Scripts folder in the root of C:\ (example: C:\Scripts) and extract the contents of the Start-DeploymentProUserBatch.zip file to it.

Create a CSV file of users for DeploymentPro

Before you can use PowerShell to run the DeploymentPro module, you must create a CSV file that lists the users who will need their Outlook email profiles configured by DeploymentPro.

Complete these steps to create a CSV file of users for DeploymentPro:

Open the csv file that you extracted to the C:\Scripts\ directory.

Add this information under each column header for every user who will need their Outlook email profiles configured by DeploymentPro:

PrimaryEmailAddress: Enter the users primary email addresses that are displayed in the DeploymentPro page in MSPComplete, as shown in the screenshot below. End user experience when DeploymentPro reconfigures their Outlook profile

DestinationEmailAddress: Enter the users UserPrincipalName (UPN) for the destination mailbox. This is the email address users will enter when they sign in to their destination mailboxes.You can define different destination domains in the CSV file. A completed CSV file should look like the example below.

Save and close the CSV file.

Run the Start-DeploymentProUserBatch PowerShell script

We recommend that you run the Start-DeploymentProUserBatch PowerShell script to run the DeploymentPro module as soon as possible, even if the email cutover (MX record cutover) won't happen for some time. When you run the DeploymentPro module, you define the date and time in which the DeploymentPro wizard will run on user computers. DMA immediately downloads the DeploymentPro module to user computers, even if the wizardisn'tscheduled to run for some time. Run the DeploymentPro module right away to give yourself enough time to troubleshoot connectivity issues that could occur when DMA tries to download the DeploymentPro module to user computers. Read the Troubleshoot DeploymentPro article for more information.

Complete these steps to run the Start-DeploymentProUserBatch PowerShell script and run the DeploymentPro module:

Search for Windows PowerShell in the Windows Start menu.

Right-click Windows PowerShell in the search results, and select Run as administrator.

Click Yes at the prompt to confirm that you want to allow the app to make changes to your device.

To confirm that the PowerShell execution policy is set to Unrestricted or RemoteSigned, type this command and press Enter:Get-ExecutionPolicy

To set the execution policy to Unrestricted if it is currently not set to Unrestricted or RemoteSigned, type this command and press Enter:Set-ExecutionPolicy UnrestrictedNote: Do not change the execution policy to RemoteSigned if it is already set to Unrestricted.

To set the PowerShell location to the C:\Scripts directory where the required files are stored, type this command and press Enter:Set-Location C:\Scripts

To run the Start-DeploymentProUserBatch PowerShell script, type this command and press Enter:.\Start-DeploymentProUserBatch.PS1

Type R and press Enter to confirm that you want to run the PowerShell script.

The PowerShell script requests the sample.csv file that you configured earlier. Locate the CSV file (C:\Scripts) and double-click it.

Type Y and press Enter to specify a date and time to run the DeploymentPro module for users.

Type a date and time for the DeploymentPro wizard to run on user computers. This date and time should happen soon after the email cutover (MX record cutover) date and time. Use the format listed below:YYYY-MM-DD HH:MMExample: 2020-04-01 10:00Note: If you have not identified the email cutover date, then enter a date far in the future (i.e., a few months later than the expected cutover date). When you do this, you should also set a reminder for yourself to rerun the PowerShell script to reschedule the date and time for the DeploymentPro wizard once you have identified the exact date and time for the email cutover. Scheduling is done by the local computer time of the computer being scheduled.

Type Y to confirm the date and time.

Enter your BitTitan username and password and click OK.

Enter the customer ID from MSPComplete and press Enter. The customer ID can be found in the URL when viewing customer information in MSPComplete as highlighted below.

The script confirms the user email addresses that were successfully scheduled for DeploymentPro. DMA downloads the DeploymentPro module to user computers at the next heartbeat interval, which could take up to an hour.Note: You may get an error that users were not scheduled due to insufficient licenses. To run the DeploymentPro module, you must apply User Migration Bundle licenses to each user. Refer to the View, purchase, and edit subscriptions article and the Apply User Migration Bundle licenses to the Customer's Users article for more information.

Next steps

Perform the mailbox migration.For more information: Follow the steps in the migration guide for your customers source and destination.

On the email cutover date and time, the DeploymentPro wizard will guide the customers users through the configuration of their Outlook email profiles. As users complete the DeploymentPro wizard, their email addresses will progress to the Completed phase in the DeploymentPro page.For more information: Read the article for more information.

How do I deploy the Device Management Agent with a Group Policy Object (GPO)?

Answer:

To deploy the BitTitan Device Management Agent (DMA) using a Group Policy Object (GPO), complete each of thesteps detailed below, in order:

Download the DMA setup file from MSPComplete.

Create a network share that is accessible to all of your customers computers, and put the DMAsetup file in the share folder.

Create a Group Policy Object that forces the domain-joined computers in a security filter to execute the DMAsetup file through a scheduled task.

These three steps are explained in greater detail below.

Step 1: Download the DMA setup file from MSPComplete.

In MSPComplete, click on All Customers from the navigation sidebar.

Click on the customer name for which you wish to deploy DMA.

On the horizontal menu bar, click on Users.

Click on Add Users, and then click on Add Users via Device Management Agent.

On the Add Users via Device Management panel, click on Device Management Agent setup file to download the DMA setup file to your local drive.Note: The instructions here are more detailedthan those listed in the Add Users via Device Management Agent panel.

Step 2: Create a network share that is accessible to all of your customers computers, and put the DMAsetup file in the share folder.

Note: For more information about Windows Server file and storage services, read the File and Storage Services Overview TechNet article.

Log onto the file server as an administrator.

Click on Start and search for Server Manager.

Click on Server Manager from the search results.

Click on File and Storage Services.

Click on Shares.

Next to Shares, click on Tasks.

Click on New Share.

Continue through the New Share Wizard prompts until finished,then click on Create.

Right-click on the new share in Server Manager, and click on Open Share.

Put the DMA setup file in the share.

Write down the share's network path; this will beneeded when creating the scheduled task. How do I deploy the Device Management Agent on computers that use a proxy?

Step 3: Create a Group Policy Object that forces the domain joined computers in a security filter to execute the DMAsetup file through a scheduled task.

Log on to the Active Directory Domain Controller as an administrator.

Click on Start, and search for Group Policy Management.

Click on Group Policy Management.

Right-click on the desired Active Directory domain, and then click on Create a GPO in this domain, and Link it here.

Enter a name for the GPO, and then click on OK.Note: By default, the GPO will apply to all users and computers that successfully authenticate to the Active Directory domain.

To narrow the scope of computers that install DMA, select Authenticated Users, and click on Remove.

To confirm the removal, clickOK.

To add a new security filter, click Add.

Type the name of the security group that the target computers are a member of, and click on Check names.

Click OK.

Right-click on the new GPO, and then click on Edit.

In the console tree, under Computer Configuration, click on Preferences > Control Panel > Scheduled Tasks.

Right-click under Scheduled Tasks and click on New, and then click on Immediate Task (At least Windows 7).Note: For more information about Scheduled Task Items, read the Configure a Scheduled Task Item TechNet article.

Enter a name and a description for the Scheduled Task.

Click on Change User or Group.

Type "system" into the Object name text box.

ClickonCheck Names.Note: Make sure that the system object name resolves to NT Authority\System.

Under Security options, click on Run whether a user is logged on or not and add a checkmark next to Run with highest privileges.

In the Configure for drop-down menu, select Windows 7, Windows Server 2008 R2.

Click on the Actions tab

Click on New.

In the Action drop-down menu, select Start a program.

In the Programs/script text box, enter the network path for the DMA setup file.Note:If you use theBrowse button to find the location of the script, then it will add the path as c:\xxxx. This is incorrect since the script needs to include the UNC path and not the local path. Be sure to replace the c:\ format with the \\servername\sharename\ format.

If the customer's computers use a proxy,you must add a command lineparameterinto the Add argumentsfield to ensure that DMA is able to transmit data through the proxy. Read the article for more information.

Click OK.

Click on the Conditions tab.

Add a checkmark next to Start only if the following network connection is available, and then select Any connection.

Click OK.

Close Group Policy Management Editor, and then close Group Policy Management.

The DMA setup file will execute on user computers at the next Group Policy refresh, typically every 90 minutes, with a random offset of 0 to 30 minutes.

MigrationWiz uses IMAP to access the email contents from Google. IMAP is not enabled for the mailbox you are attempting to migrate.Resolution:

Sign in to your Google account .

Click onSettingsin the upper-right corner of your browser.

Click on theForwarding and POP/IMAPtab.

In the IMAP Access section, click onEnable IMAP.

Click onSave Changes.

Administrators can add subscriptions and licenses to their account by redeeming a coupon generated from a distributor, another workgroup, or an MSPComplete account. You can also shift subscriptions and licenses from one workgroup to another, or from one MSPComplete account to another, by generating a coupon and then redeeming it in the desired workgroup or account.

For MigrationWiz users who arenotusing MSPComplete, simply click on your name in the top right of your Active Migrations page and select "Redeem Coupon" to be directed to the appropriate flow.

Once you have been directed to the coupon page, enter your coupon code into the Coupon Code field, and then click Check. If you have multiple coupons, add a space between each code.

MSPComplete Steps

Follow these steps to redeem a subscription or license coupon:

Select the workgroup on the top of the left navigation pane.

Click Settings on the left navigation pane.

Click the Coupons

Click Redeem Coupon.

Enter your coupon code into the Coupon Code field, and then click Check. If you have multiple coupons, add a space between each code.

If the coupon code is valid, MSPComplete displays information about the purchased items. If the code is not valid, contact the person or distributor who generated the coupon.

Click Apply. Important: Subscriptions are validated and activated as soon as you redeem the coupon. The one-year subscription period begins at this point, not at the time subscriptions are consumed by agents.

Introduction

This is the complete onboarding task flow for migrating Microsoft Teams from one Office 365 tenant to another Office 365 tenant.

Important: MigrationWiz is not a sync tool. Once you have started the migration, items updated at the Source will not be updated at the Destination. There is no process by which the migrated items can be updated on the Destination after being migrated.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Important notes:

Unfortunately, due to limitations on connections allowed by GoDaddy, we do not support migrating to or from GoDaddy using this specific migration type.

Teams migrations to Destination tenants that use IP restrictions are unable to use Microsoft-provided Azure storage for migration. Custom Azure storage is required for this situation.

Teams Migration is currently not supported for migrations to or from Black Forest tenants using the MigrationWiz Germany DataCenter. While this may become a supported functionality in the future, we do not have any expected timeline on such functionality. German tenants with a .com Office 365 instance should migrate without issue.

For instructions on migrating to or from Government sources, see our new Government Tenants article.

Prerequisites

All migrating users must exist in the Destination environment. MigrationWiz will not create or license users.

This migration requires a Global Administrator account to be used on both the Source and the Destination endpoints.

The Global Administrator account must also have an Office 365 license applied that includes Teams.

MigrationWiz-Collaboration licenses are required for this migration type. User Migration Bundles will not work.

The Administrator user account must be set up without a federated account.

ADFS must be turned off for the Administrator account prior to migrating.

Multi-Factor Authentication (MFA) must be disabled for the Administrator user account for the duration of the migration.

Prepare the Source Environment

Create a Global Administrator account in Office 365 to be used for migration or use the Global Administrator account for the tenant. Read the How do I create an administrator account in Office 365? article for more information.

Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

Prepare the Destination Environment

Create a Global Administrator account in Office 365 to be used for migration or use the Global Administrator account for the tenant. Read the How do I create an administrator account in Office 365? article for more information.

Create user accounts and assign Office 365 licenses. The Office 365 licenses must include Teams access. For more information on which licenses can be used, refer to Office 365 Licensing for Teams.

Set up the app-based authentication in the Office 365 tenant. For specific instructions, see Sharepoint App-based Authentication.

MSPComplete Steps

Create the Customer. For more information, see View, Add, and Edit Your Customers.

Create the Source and Destination endpoints. For more information, read View, Add, and Edit Customer Endpoints.Notes:

If endpoints are set up in MigrationWiz, the endpoints will automatically default to the type Teams. This is normal and cannot be changed.

If the endpoints are set up in MSPComplete, you will need to select Teams (Source) or Teams (Destination), when settings up the Source and Destination endpoints.

The Destination endpoint will require Azure Storage access. You can either use Microsoft provided Azure storage or your own Azure Storage. If using your own, the Storage Account Name and Access Key will be required.

Purchase MigrationWiz-Collaboration licenses.

MigrationWiz Steps

Create a Collaboration migration project. See the How do I create a new migration project? article for step by step instructions.

Click Start Assessment to add items to the Collaboration project. Notes:

This step will connect to the endpoints and discover all teams, channels, users, conversations, and files in both tenants before the migration can proceed. When the Assessment completes, MigrationWiz will display information such as the number of teams, total file size, total number of users, the number and type of licenses needed, and the number of licenses currently available to be used.

Guest users will not be included as part of the assessed license requirement. Conversations that guest users participate in will be migrated as part of the migration process.

If additional licenses are needed, purchase additional Collaboration licenses to make up the difference.

Once the additional licenses have been purchased, click the Rerun Assessment.Note: If no additional licenses are needed, you can skip over this step.

Once the assessment shows the message You have sufficient licenses. You can start your migration., you will be able to click the Start Full Migration button.

Click the Start Full Migration button.

When the migration completes, verify that the users are now able to see their teams and channels in the Destination tenant.

Click the bar chart icon in the MigrationWiz dashboard to request an email containing the project migration statistics. Read How do I request statistics for my migration project? for more information.

Notes:

All Teams and Channels are added to the project by default. It is not possible to only add specific Teams or Channels to the project. It is possible to use a filter to select specific Teams or Channels in a project to be migrated or skipped. For more information, see Collaboration Migration: Adding a filter.

The teams and channels will show the Administrator account as having added the users and then leaving the group. This is normal behavior from Office 365.

All conversations will be migrated with a UTC timestamp.

Only the latest 3,000 messages in a channel will be displayed in the Destination channel. The entire conversation history for the channel be found in the Conversation History tab on the Destination team channel. The messages in the Conversation History tab are not able to be replied to.

This migration process syncs the permissions of users from the Source to the Destination. If permissions differ on the Destination, the Source will always be used as the reference.

I am missing items or the number of items do not match.

Resolution:

Thereare several reasons for items to be missing, or toappear to be missing.

Check to see if the migration completed successfully and without any errors. If there were errors, consider performing a repair migration pass to allow missing items to migrate.

Check to see if the missing items are special items that we do not migrate. The list of items we do not migrate can be found here.

Check to seeif the missing items are stored on the Source server (i.e., not in a local PST file). If possible, use a web client to verify the content of the Source mailbox.

Check to seeif the missing items are stored on the Destination server. Some clients may need to "subscribe" to folders for them to appear, or may take time to download items. If possible, use a web client to verify the content of theDestination mailbox.

Check to see if the missing items were not moved to a new location on the Destination server (i.e., Outlook automatically archived old content after the migration). If possible,do a search across all folders.

Check to see if your mailbox connector or mailbox has any advanced filtering option specified. For example, a date filter, a folder filter, or an object type filter may result in a partial migration.

Check to see if the Source items have any type of special permissions set on them. In some rare cases, the folder can be read but cannot migratesome items.

Check to see if any folder was renamed, or items moved between folders while the migration was in progress. This may, in some rare cases, cause items to be missing.

Check to see if the Destination system did not move migrated items to theJunk mail folder because of anti-spam processing. Some Destination email systems will apply anti-spam to migrated items.

Check to seeif missing items were received by the Source while the migration was in progress. We recommend performing a multi-pass migration to migrate residuals after the migration completes.

Check to see if missing items are readable at the Source. Some archive systems such as Symantec Enterprise Vault may cause only stub items to be returned by access APIs.

Note:MigrationWiz remembers which items have been migrated. If you deleted items at the Destination after migration, and then resubmit a migration, we will NOT remigrate the items you deleted at the Destination. You will need to reset the statistics of your migration first, then resubmit.

The BitTitan Audit Logging Service allows you to compare items between the Source and Destination to analyze the difference. However, verifying the above points will expedite our investigation. In most cases, we will require screen shots demonstrating that an item is missingto facilitate investigation.

How are categories migrated?Answer:

Categories and associated colors are a mailbox configuration setting, and therefore arenot migrated. However, if an item in the Source has a category assigned, it will show at the Destination as having that category assigned even though the category will not be listed under "All Categories" in Outlook.You must manually recreate the categories at the Destination. Once a category is recreated and a color is assigned, all Destination items with that category will update to show the new color. This can be done either before orafter the migration is performed.

How do I specify the data center to use for my migration?

Answer:

In order to reduce the latency between a Source system and our migration infrastructure, we provide our customers with several data centers in strategic locations around the world.

Choosing a data center closer to the Source servers can significantly increase the performance of migrations by decreasing latency.

Specify a data center:

Sign in to your MigrationWiz account.

Edit your Project and click on Advanced Options.

Under Performance, select a data center using the Preferred Data Center field.

Introduction

This is the complete onboarding task flow for migrating mailboxes from On-Premises Lotus Notes, or On-Premises Lotus Domino, to On-Premises Microsoft Exchange, versions 2007+.There are a few things you should know before beginning your migration.

Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

Important: MigrationWiz is not a sync tool. Items updated at the Source will not be updated at the Destination. There is no process by which the calendars, contacts, tasks, etc., can be updated after being migrated.

Lotus Notes requires local software installation to use MigrationWiz, as there are no remote APIs for the messaging system. The Lotus Extractor is a small console application (a standalone .exe file) responsible for extracting data from the Domino server and securely streaming this data to the MigrationWiz platform. The steps to install this extractor are included in the Prepare the Source Environment section of this guide. After installing the Lotus Notes Extractor, you can then manage the migration from the MigrationWiz web portal (e.g., to stop/start migrations, view statistics, etc.).

MigrationWiz 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 can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.

Prepare the Source Environment

Set up an administrator account for migration on the Domino server. For more information, see How do I set up an admin account on Lotus Notes or Lotus Domino server?

Test administrative access to the mailboxes. For more information, see How do I test administrative mailbox access for Lotus Notes?

Perform mailbox cleanup:

Mailboxes should be emptied of unneeded/unsupported data:

Old/unwanted email (this will reduce the time for migration)

Large attachments (any attachment larger than 150MB will not be migrated)

Unwanted mailboxes should be archived/deleted according to company compliance policies.

Synchronize users' personal address books on the Lotus Domino server. For more information, see How can I synchronize my Lotus Notes contacts on the Lotus Domino server? Notes:

Lotus Notes contacts are stored locally on the users hard drive, in a local .nsf file. In order to migrate them, each user must have synchronized their personal address book on the Lotus Domino server before the migration begins.

We recommend that you send an email to all users with instructions on how to synchronize their personal address books. Provide them the instructions that are in How can I synchronize my Lotus Notes contacts on the Lotus Domino server?.

Set up the Lotus Notes Extractor. For more information, see How do I set up the Lotus Notes Extractor? Notes:

The Lotus Extractor will require ports 80 and 443 to be open.

Running the Extractor now will result in a message that the Extractor is unable to find a mailbox connector. This is an expected message and is not a problem for this step.

Prepare the Destination Environment

Create an administrator account in Exchange that has full access to all user mailboxes. For more information, see How do I create an administrator account in Office 365, and then use this during migration?

Set up user accounts in Exchange.

Disable throttling against the administrator account. Refer to Option 1 in How do I disable the throttling policy on Exchange?

Verify mailbox accessibility, using EWS. For more information, see How can I verify mailbox accessibility using EWS?

If you want to be able to migrate messages with attachments larger than 10MB, the following limits need to be increased:

Message size limits. For more information, see How do I increase the Exchange message size limits?

Maximum accepted content length. For more information, see How do I increase the maximum accepted content length?

Maximum receive message size.For more information, see How do I increase the maximum received message size?

Maximum accepted request length. This is only valid if your destination server is running Exchange 2007.For more information, see How do I increase the maximum accepted request length?

MigrationWiz Steps

Create the Mailbox Migration project. For more information, see How do I create a new migration project? Note: You will create one project per Lotus Extractor.

During the project creation, it will be necessary to create the Source and Destination endpoints. For more information, see View, Add, and Edit Customer Endpoints.

For the Source endpoint:

Click New > Enter endpoint name > Endpoint type: Lotus Notes 6.5+.

In the Server Name field, enter the Lotus Extractor Identifier.Notes:

This was generated in Step 8 of How do I set up the Lotus Notes Extractor? when setting up the Source environment.

Create separate Source endpoints for each Extractor you have set up. These will be used when setting up your MigrationWiz projects. You will be setting up one MigrationWiz project per Extractor.

For the Destination endpoint:

Click New > For endpoint type, select Exchange Server 2003+.

Enter the OWA URL. For more information, see How do I verify if my OWA URL is correct?

Click the Provide Credentials radio button and enter the administrator account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.

Add the accounts (also referred to as "items") that will be migrated to the project. You will use the LotusExtractor.csv that was generated when setting up the Lotus Extractor. For more information, see How do I perform a bulk import of my Lotus Notes mailboxes?

4. Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow you to perform multiple migration types with a single license. Refer to these articles for more information:

How do I purchase licenses?

Apply User Migration Bundle licenses to the Customer's Users

Which migration license should I choose?

Set the Project Advanced Options. For more information, see What project Advanced Options are available? The following options are the most valuable for this migration scenario:

Set Maximum concurrent migrations. This should be set to15. Each Lotus Extractor can simultaneously migrate up to 15 mailboxes only.

Add the following in the Support Options: LotusDisableRetryOnGetMIMEFailure=1 Note: This is used if Lotus Notes is configured to use rich text formatting (RTF) by default. This ensures proper MIME conversion of the formatted text.

Run Verify Credentials. For more information, see How do I verify credentials?

Notify users that a migration is occurring. Send an email to all users telling them the time and date of the migration.

Pre-Stage pass: Select the users > Click the Start button from the top and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. For more information, see How do I start a migration?

MX Record Cutover. Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting. Note: If migrating in batches and coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must perform an extra step:

Set up mail forwarding for Lotus Notes. For more information, see How do I set up a forwarding address for Lotus Notes?

Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. For more information, see How do I start a migration?

Run Retry Errors. For more information, see How do I retry failed items?

Look through the user list and click any red "failed migration" errors. Review information and act accordingly.

If problems persist, contact Support. For options, see How do I get support for your products? Notes:

If contacting Support for a Lotus Notes migration issue, you should provide the log files with your support request. The required log files are LotusExtractor.log, Coordinator.log, andHeartbeat.log. These files are located at C:\Users\UserName\AppData\Local\BitTitan\logs, as detailed in What log files do I need to send in case of a problem with my Lotus Notes migration?

If error messages state that email addresses cannot be resolved at the source, refer to Why are some email addresses unresolved?

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. For more information, see How do I request statistics for my migration project?

How long does a migration take? What is the speed that we can expect?

Answer:

It can be difficult to accurately predict how long a migration will take. Several factors that will have an impact on timing are system load, bandwidth, average item size, and source or destination bottlenecks.

MigrationWiz is unlikely be the bottleneck,as we are connected to the largest migration farms and we do not throttledata. However, this is a variable process with many moving parts.

Here is a very rough breakdown of whatcan be expected. Note: This is not an SLA; it is an example based on a very large sample ofmigration speeds experienced by our Partners.

Low end: 250mb per hr/per user

Mid end: 750mb per hr/per user

High end: 1.25gb per hr/per user

Here are some factors that will affectmigration speeds:

Network Speed:

How fast are the Source and Destination servers connected to the internet? The entire process is only as fast asthe slowest link. We've connected to networks that range from a T1 to networks that host multiple gigabit connections, but depending on the data center that the migration server is located in, we will most likely be connected with a gigabit or 10-gigabit connection.

Server Load:

What type of equipment is the Source and Destination mailbox deployed on? Our migration process is not usually noticeable ifthe server is sized appropriately for your organization.

Throttling:

Does the Source or Destination system throttle the amount of data that can be read or written? Several systems implement throttling policies that prevent full utilization of available network bandwidth.

Number of Folders:

Depending on the number of folders and the Source system, enumeration of the folders might slow down the migration process. Read more on this topic in How does folder size impact migration speeds?

Network Latency:

The network latency is dependent on the quality of the connection between our data center and the Source and Destination. We utilize the fastest internet backbones available globally. Because of our global migration farm, our connections are made from networks with low latencies.

Mailbox Migrations

Simultaneous Mailbox Migrations:

MigrationWiz is able to migrate hundreds of thousands of mailboxes simultaneously. Migrating more mailboxes at the same time allows parallel processing,reducing the duration of your migration. If all of your mailboxes are migrated at thesame time, the migration duration is the time it takes to migrate the largest mailbox.

Number of Mailbox Items & Mailbox Size:

There is a per-item transaction overhead and time cost. For example, given two mailboxes of the same size but with a different number of items, the one with fewer items will migrate faster than the one with more items.

The more data there is, the longer the migration. When migrating between two hosted providers, the size of the mailbox is unlikely to overload our bandwidth, but some Destinations might have capacity issues. When mailboxes exceed a certain size, speed reduction may occur because of those scalabilityissues.

Mailbox Errors:

Errors can occur for a number of reasons: corrupt items, network outages, etc. MigrationWiz contains automated, self-corrective technology that deals with errors automatically in most cases. For those it does not automatically handle, our Help Center offers resources and guidance.