Moving Office 365 Mailboxes to IMAP Servers - What’s the Best Approach
I’ve recently been looking into scenarios where organizations need to move mailboxes from Microsoft 365 to IMAP based email servers, and I noticed this is still a common requirement in many migrations. In most cases, the challenge is not just moving emails, but making sure everything like folder structure, old emails, and user data stays intact without creating too much disruption for users. From what I’ve seen, doing this manually can get very complex, especially when there are multiple mailboxes or large data volumes involved. That’s where migration tools usually come into the picture. Most tools simplify things by handling: 1. Secure connection to Microsoft 365 accounts 2. Bulk mailbox migration 3. Preserving folder hierarchy 4. Reducing downtime during the move 5. Avoiding duplicate data issues One thing I’ve noticed is that running a small pilot migration first always helps. It gives a clear idea of how the actual migration will behave before moving all users. Has anyone here worked on Office 365 to IMAP migration at scale? Would be good to know what approaches or tools worked best in your case and what challenges you faced during the process.Need to Restore PST Files to Office 365 Mailboxes - What's the Best Approach
Hey everyone, I have a task coming up where I need to restore several PST files back into Office 365 mailboxes. Haven't done this before at this scale and honestly not sure where to begin. I've looked at Microsoft's native import service through Purview but I have a few concerns: Some of the PST files are quite large — not sure how well it handles that I need to restore only specific folders for some users, not the entire PST I'm worried about data consistency after the restore Would prefer something that doesn't require too many admin roles or complex setup For those who have done PST to Office 365 restores — what approach worked best for you? Any tools, tips, or things to watch out for that you wish you knew before starting?Office 365 Mailbox Export to PST - Third Party Tools: What’s Your Experience?
Exporting Office 365 mailboxes to PST is still a common requirement in many Microsoft 365 environments, especially for backup, compliance, and migration scenarios. While Microsoft offers native options like Purview eDiscovery and Outlook export, many administrators also consider third-party tools when dealing with large mailboxes or bulk export requirements. In real-world scenarios, factors like speed, ease of use, permission handling, and consistency of exported data often influence the choice of tool. Some teams prefer native methods for compliance control, while others explore third-party solutions to simplify large-scale or repeated export tasks. For those working with Microsoft 365, what has your experience been with third-party PST export tools? Have they helped in your environment, or do you still rely mainly on Microsoft’s native options?
Migration from Hosted Exchange (Hybrid) to M365 Classic Outlook Client Problems and Solutions
Hello Everyone, I'm a tech who started on a 8088 processor in the 80's. Not mentioning the Vic20 and C64 since that hardly seem relevant! I'm posting here to hopefully help the next person with the issues I've had over the last few weeks. My client had to port his email from a provider with an on-perm Exchange server in a Hybrid setup with M365 to his own M365 environment. I expected this was to be about 3 hours of work for me - setup M365 environment, plan the cut-over window, update the Outlook clients on each PC. It ended up being roughly 20 hours of my time and at least 10 hours of dedicated time for my client. For those wanting to jump directly to what mostly fixed it use this link, it should get you past the dreaded "an encrypted connection to your mail server is not available" when trying to add the mail account into a clean profile. Use https://support.microsoft.com/en-us/windows/classic-outlook-troubleshooters-086e3d66-5404-4034-9cc5-545909dcc166 and pick "Classic Outlook Profile Setup Troubleshooter" Most hits are going to tell you its an autodiscovery issue, but if you're reading this I'm going to assume you've already confirmed that. Our issue was some ghost configuration, only on the PCs previously setup for mail on the old server. A new PC could add the same account without issue. Some of the research suggested this would not happen if the proper Microsoft migration process is followed to move the account - but in our case the previous provider was unable to perform the migration. I'll skip over the research we tried along the way, such as New Outlook Profiles, Registry entry changes, MS Personal users with the same email as MS Business Users, Autodiscover problems (including concerns that the base website for the client was offering invalid data), and so on. After each hit where we applied a fix we again had to try adding the mail to the profile, and each time we sat watching the little circle for up to 5 minutes only to get the same error. Now, once we found the link above - which did not come up in most searches - things got better, but not 100%. We added the profile ok but then Outlook gave a permission error while starting. To fix that, the user signed in must have administrative access and you use File Explorer to navigate to the folder identified in the error. In our case it was in folders kept under \Windows\System32\. When prompted that we need to grant permanent access we said yes. In our case this is where Outlook was storing the ost files. That worked for most of the clients, but we had one additional issue where the error was pointing to a folder that didn't exist. Just creating the folder was not enough, the final fix was to hold CTRL-SHIFT down while opening Outlook to start in administrative mode to allow it to create the ost file in the newly created folder. Finally 3 weeks after our cut over window, while the client had to use OWA, we were able to get outlook running. This was critical for my client because they did not have access to the mail history since the migration didn't happen - they had to open a copy of their PST in Outlook and use mail in OWA and constantly bounce back and forth. I hope this helps someone avoid the pain we went though!Migrating G suite to Office 365
Dears, Good day, I working on a company which hosted their email on G suite, and I want to migrate all mailboxes, calendar, tasks, files, all things to Office 365. kindly let me know the steps for Migration, we have 69 users needed to be completely migrated. Kindly advise
Cross tenant migration tools : New MS solution compared to Migration Wiz?
Hi, I'm looking for informations about advantages and limitations between new Microsoft Cross Tenant migration solution (Preview) and "Migration Wiz". Microsoft solution look more limited and doesn't seem to have Free/busy sync. What are the returns for those who did use MS cross tenant solution ? Thanks,
365 Tenant To Tenant Migration
I have a tenant who is not set up to be GCC compliant. We have created another tenant that is now GCC compliant and need to move the tenants from the original tenant to the newly created GCC compliant tenancy. I am not sure how we can go about doing this with the destination and origination having the same domain name. I have created the users with the onmicrosoft accounts, instead of the .org users, but we still have the issue of migration. How do we move these users? What is the expected down time for their domain if we use a dummy domain? I am very concerned this is going to result in a massive loss of data.
Google workspace migration - Automatic doesn't download the JSON while creating the migration endpoi
I recently came across an issue where the google workspace migration wasn't downloading the Json file. After a lot of struggle, I figured out that google by default blocks service account key creation. To resolve this, follow the below mentioned steps 1) login to https://console.cloud.google.com/iam-admin and select the root org 2) Add Organisation Policy Administrator role 3) Click on Organization policies and then search for "Disable service account key creation" and set the enforcement to OFF. 4) Now you should be able to download the JSON.
Migrating from Google Workspace with Multiple Domains
I am interested in switching from Google Workspace to Microsoft 365 for Business. For context, I just use this personally, but enjoy the custom email and control over my account. I want to switch over because the only product that I use is Gmail, and pay for an additional Microsoft 365 subscription. While I won't be saving any money, or the savings will be negligible, it would be nice to have everything in one ecosystem. I've looked over how to migrate just one domain, and that seems fairly straight forward. However, I am wondering how feasible it would be to transfer multiple domains, and to switch my primary domain. Below is the structure of my current Google Workspace domains: - domain1.com | This is used as my primary domain that I log into. Also serves as my primary email. - domain2.com | Used as an additional email alias for different purposes. Not used for logging in. - domain3.com | Used as an additional email alias for different purposes. Not used for logging in. If I wanted to keep domain1.com as my primary domain, I assume that I would do the standard migration and then add domain2.com and domain3.com as additional email aliases. However, I want to switch my primary domain in Microsoft 365 to domain2.com. Is there any way to migrate emails from Google Workspace that's on domain1.com --> domain2.com via Microsoft 365 and make domain2.com the primary domain? I know that this is a lot, so please ask for clarification if needed. Thanks!
