This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Office 365 tenant to tenant migration
#1
Before commencing with the migration process, one has to go through a multi-step preparatory process. It will get one ready for the migration process and complete it smoothly. The following steps are involved.

Step 1 – Domain Preparation
There should be sufficient space or room in the target tenant’s Office 365 to ensure the successful migration of all data from the source tenant. It could entail obtaining additional licenses, as well.
Secondly, both the source tenant and the target tenant will require the opening of administrator accounts. Also, specific migration tools might need the creation of additional admin accounts.
It is also necessary to create user mailboxes, resource mailboxes, and distribution groups in the target tenant.
At times, performing Active Directory Domain Services (AD DS) consolidation using AD DS tools might be necessary. The synchronization of the source and the target domain is the next step to follow.
The final step of the domain preparation stage is to train the end-users on how to use Office 365 post-migration.
Step 2 – Verification of the Domain
Commence the process of verifying the target tenant domain in Office 365.
The addition of a source domain in the admin center of the target Office 365 and the creation of TXT records in DNS have to be performed.
However, one should ensure that the domain is in use for only one target tenant lest the verification process should fail. It will now take around 72 hours for the change to take effect.

Step 3 – Scheduling the Migration
The first step involves generating a list of user mailboxes for migration and creating a CSV file for mapping.
Note down the lowest value of Time To Live (TTL) on the Mail Exchanger (MX) record of the primary email domain.
The next step is to disable the directory sync for the source tenant.
Step 4 – Facilitating the Migration
Change the primary MX record to an unreachable value to stop the flow of inbound mail to the source tenant. It becomes easy because of the noting down of the lowest value of TTL on the MX record.
Ensure erasure of all objects from the primary mail domain in the source tenant before the transfer of Office 365 mailbox to another account.
The final step is preparing the target domain by verifying the source tenant in the target domain. One should ensure to initiate this step one hour after performing the previous actions.
If one uses Active Directory Federation Services (AD FS), one has to configure a new domain in the target tenant for AD FS.
One should also activate new users in the target domain as well as assign new licenses.
The primary email address for the new users must be the source domain. Communicating the passwords to the new users is also necessary.

I hope this helps you in O365 tenant to tenant migration. To know more about Hybrid migration office 365 or IMAP migration to office 365 visit O365CloudExperts.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)