This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
I am studying to do a migration using the cutover method.
Because?
They are only 200 mailboxes (total of 300GB) and we need to take it to Office 365.
But some things are not yet clear to me.
Thank you.
A comprehensive suite of productivity tools and cloud services that enhance collaboration, communication, and efficiency. Combining classic Office apps with advanced Microsoft 365 features, it supports both personal and business needs
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Hi Sandro,
If you have AAD connector or Dirsync enabled, the source of authority of the objects is defined as on-premises. In this situation, most of the attribute of the cloud users can only be managed from the on-premises. An on-premises Exchange server is needed to extend Active Directory schema and also provide the supported tools including Exchange Management Console or Exchange Management Shell to manage the mail related attributes. SSO relies on Dirsync or AAD connector, so it is suggested you keep at least one Exchange server.
If you don't need SSO and Dirsync, you can remove Dirsync and on-premises Exchange server, and manage all your users from the cloud side. Here is another official blog that may be helpful for your understanding: Decommissioning your Exchange 2010 servers in a Hybrid Deployment.
Thanks,
Alex
Hi Alex,
A2. If I have 200 users, I have to create a single bat to migrate all at once and expect to finish? I can make separate bat's migrating to go slowly? This to avoid competition access.
If the recommendation is to create a single bat and if I can not migrate all in two days total, starting the activity on Saturday and ending on Sunday night.
I can leave the bat to run until complete (during the week) and next Friday run an incremental?
A3. I can not later add another discovery, if I already have an existing one. I thought I could manually enter when creating the profile of the Office 365 address to advance the creation of profiles.
A6. 300GB is the total amount of mailbox users. But individual mailbox, having from 2G 10G. I believe that due to the size of the mailbox of the users and not cause impacts to users working 24x7, the best option is the hybrid.
Thanks.
Hi Sandro Alves Helps,
A2. As is suggested in the official article, only one single batch is created and used in Cutover migration. Please let me know if there is any misunderstanding and what you mean by creating separate bats. If the migration batch has not been completed yet and you pause it, the initial synchronization and incremental synchronization will be paused. If you resume the batch, the initial synchronization and incremental synchronization will continue. The incremental synchronization occurs automatically every 24 hours if the batch is running.
A3. If you add an Autodiscover record for Office 365, you will be able to use Exchange Autodiscover to set up your cloud mailbox in Outlook.
A4. Yes.
A5. No, Staged migration is only officially supported in on-premises Exchange 2003 and Exchange 2007.
A6. You can use the import PST service in Office 365 portal and PST capture as well. Considering you have 300GB mailbox contents, Cutover migration is a simpler solution to migrate all the mailboxes to Office 365.
Thanks,
Alex
Hi,
I will keep the questions that still have questions:
Q2. In the videos I studied, I'll create separate bat's to avoid competition (20) to access and ensure the migration of bat's.
After completed synchronization, I can run the bat again so that it synchronizes the difference of the changes made.
This to say that I can get on Saturday and Sunday is not finished, I can continue execution of new bat's until all are migrated? I mean, the bat's already run, I could run them to copy the difference after finished all bat's?
When you say that the bat will run 24 hours later, this is done automatically?
Q3. If I set the FQDN of the office 365 autodiscovey in during the new profile configuration will work? Using POP3 or IMAP is not interesting.
My goal is to anticipate the download of emails to prevent users are waiting, after the country's first login.
Q4. Users will have to use different password until AD Connect is implemented.
Q5. Staged migration applies to Exchange 2010?
Q6. Importing PST was unavailable last some time. Now I can do this import using the Office 365 portal or have to use PST Capture?
I am in a difficult situation.
I need to migrate accounts with 200 sizes (2G, 3G and 4G) on average and I need password synchronization and SSO.
They can not have an impact to the users.
I can not keep Exchange 2010 Onpremises.
The hybrido method is the best, but I need to keep the local exchange and the Cutover, and take a long time due to volumetric data (300GB), cause impacts to users in the reconfiguration.
What is the best way?
Thank you.
Hi Sandro Alves Helps,
I will try to answer your questions. Please find my response below.
Q1. During the process of copying the mailbox to Office 365, users suffer some impact? It is completely transparent?
There is no end user impact during the Cutover migration. They are able to access their on-premises Exchange mailboxes in Outlook and OWA. After the migration is completed and you point the Autodiscover record to Office 365, they need to create new Outlook profile to connect their Office 365 Online mailboxes.
Q2. After the start of the first bat process users, after finished, we can run the same bat users to copy the difference (changes during the bat)?
No. Once the new migration batch is started, the mailbox content are copied in the initial synchronization. The new coming emails are copied every 24 hours during the incremental synchronization. After you stop the batch, the synchronization is dropped. Restart the batch cannot restart the synchronization.
Q3.It is advisable to set up profiles of users, so the bat are being finalized. However, if the autodisovery is still pointing to the Exchange On-premisses as we can set up new profiles?
You can create new profiles and connect the online mailboxes with POP3 or IMAP, but Exchange Autodiscover is not available.
Q4.After migrating all users for Office 365 and removed the Exchange On-premisses, I can enable AD Connect to sync password?
Yes. You can set up AAD connector and match the on-premises users with cloud users and mailboxes.
Q5.If for any reason we can not move all accounts to Office 365. You can enable routing (using company.onmicrosoft.com) of emails already migrated to Office 365, until we can complete the migration?
No, cutover migration will move all your mailboxes in a single batch. If you want to migrate the user mailboxes to Office 365 with multiple batches over time, please consider IMAP migration, Staged migration or Hybrid migration.
Q6. If for any reason we can not move one of the bat accounts. We can finish this bat and create a unique mailbox for that we can not?
Yes. You can create a mailbox in Office 365 directly and import emails by PST.
Q7.The public certificate using cutover, needs all FQDNs of published services or just the FQDN used for Outlook Anyware?
FQDN of Outlook Anywhere.
If anything is unclear, please let us know.
Thanks,
Alex