Our experience migrating from Exchange Server to Microsoft 365
We recently performed a migration from an on-premises Exchange Server to Microsoft 365. Our goal was to transfer mailbox data while minimizing disruption to users. Before starting, we reviewed the source mailboxes, Microsoft 365 accounts, permissions, network availability and mailbox mapping. We then migrated a few test mailboxes to confirm the connection and verify emails, calendars, contacts and folder structures. For this migration, we used EdbMails Exchange Migration to connect the source and destination environments, map mailboxes and perform the migration in stages. Most historical data was transferred during the initial migration while users continued working. Before the final cutover, we ran an incremental migration to transfer newly received and modified items. After migration, we checked: Emails, folders, calendars and contacts Recent and sent messages Archive and shared mailboxes Item counts and migration logs Mail flow after the DNS changes Overall, the staged approach made the migration easier to manage and reduced the amount of work required during the final cutover. Our main lessons were: Always begin with a pilot migration. Verify permissions and mailbox mapping early. Run an incremental migration before cutover. Validate the migrated data before retiring the source server. The migration was completed successfully, and the structured approach helped us maintain data integrity while keeping disruption to users to a minimum.Planning a Google Workspace to Microsoft 365 Migration? What Should You Consider?
Hi everyone, Has anyone recently migrated from Google Workspace to Microsoft 365? I’m interested in knowing what challenges you faced during the migration, especially around mailbox data, calendars, contacts, user mapping, or the final cutover process. For those planning the migration, what are the key things you recommend preparing before getting started? Would like to hear your experiences and suggestions.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?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.
Publish an Excel Add-in by just submitting the add-in manifest to Microsoft Marketplace
I am working on Excel Add-in built using the react template. We are planning to host the add-in code on our domain and update the manifest to point to the URL for our domain. Can I just submit the add-in manifest to Microsoft to publish it in Microsoft Marketplace?
I haven't seen anyone talking about this online store
There is this office and windows key store called esd codes and they sell office keys. They seem legit since they're affiliated with Microsoft and they have mostly positive reviews but I the description of every office key and I mean every has a note stating "if office (literally every single one) version is not available, you will receive the Professional Plus version at the same price" which they are trying to make it look like an upgrade but from what I searched the professional plus versions are bought in bulk by big companies and organizations and after they stop being updated they are being sold for cheap probably by employees. I have found multiple for less than 2 or even 1 buck and I feel they are scamming people.
How to extract data from Word tables into Excel
Thx！And I was dealing with a bunch of old Word forms filled out over the past decade – inconsistent fields, messy tables. I need to extract the data for each field into Excel for analysis and processing. Is there a good way to do this? I heard about this tool from a friend. Has anyone here used it? Is it good? https://chestnuttable.vercel.app/
