Cookies on this site

We would like to use cookies to understand how the site is used and to measure our campaigns. Nothing is set until you choose, and you can change your mind at any time from “Cookie settings” at the foot of every page. Privacy policy

Contact UsContact Us

Move your email to Microsoft 365, planned so mail keeps flowing.

We move mailboxes, calendars, contacts and archives to Microsoft 365 from Google Workspace, from Exchange servers you run yourself, or from another Microsoft 365 tenant. Each move is planned around how mail reaches you, so messages keep arriving while mailboxes copy, and your people open the new system with their history already in it.

Book a strategy call

What we cover

What we move from

Google Workspace, Exchange or another tenant

The source decides the method. Google Workspace mail, calendars and contacts move with migration tools built for that route. Exchange servers you run yourself can move in stages or all at once, depending on their size and how long the two systems need to run side by side. A move between two Microsoft 365 tenants, after a merger or a split, takes identities, files and Teams as well, and has its own page.

Our engineers confirm the method for your source in the plan. Moves the other way, from Microsoft 365 to Google Workspace, and from other mail systems are planned case by case.

What we do

  • Google Workspace to Microsoft 365
  • Exchange servers to Exchange Online
  • Microsoft 365 tenant to tenant
  • Shared mailboxes, groups and distribution lists

What moves

Mail, calendars, contacts and archives

A mailbox is more than its inbox. We inventory folders, calendars and meeting rooms, contacts, shared and resource mailboxes, distribution lists, aliases, delegate access and the archives people keep, including old PST files on laptops and file shares. Then we agree with you what moves, what is kept as an archive and what is left behind.

Large mailboxes and archives are copied well ahead of the cut-over, so the last step only has to catch up on recent mail.

Approach

Plan, pilot, copy, cut over

The plan comes first: the inventory, the order of the move, the licences the target needs and the message your people will receive. A pilot group of willing users moves next and tells us what the instructions missed. The remaining mailboxes are then copied in batches while everyone keeps using the old system. At cut-over the mail records (MX) change so new mail goes to Microsoft 365, a final pass copies what arrived in between, and people sign in to a mailbox that already holds their history.

What we do

  • Inventory and migration plan
  • Pilot group and user instructions
  • Batch copying ahead of the cut-over
  • Mail record change and a final catch-up pass

Coexistence and downtime

Both systems working while the move runs

A move that runs over days or weeks needs the old and new systems to work side by side. We set up mail routing so a message reaches the right mailbox whichever system it is in, and calendar sharing between the two where the platforms allow it, so people can still see each other's availability. Lowering the DNS time-to-live before the cut-over keeps the switch of mail records short, and the final catch-up pass copies across any mail that arrived during it.

Risks

Risks, and how each is handled

Mail lost in the switch: records change in a planned window with a short time-to-live, and a catch-up pass follows. Archives nobody knew about: the inventory looks for PST files and old archives before the plan is fixed. Broken delegate access and shared calendars: permissions are listed and re-created in the target. Phones and Outlook that stop syncing: people get step-by-step instructions and help on the first day. Phishing: a move is when people expect unusual emails, so the plan tells them in advance which messages to expect and where to report anything else.

What you get

Everyone on Microsoft 365, with their history

Once mail runs in Microsoft 365, our Microsoft Consulting team can secure it with Purview sensitivity labels, data loss prevention and Entra ID conditional access, the same controls that keep Copilot from seeing more than it should.

What we do

  • A migration plan with the inventory and the order of the move
  • Mailboxes, calendars, contacts and agreed archives in Microsoft 365
  • Mail routing and records switched, with a catch-up pass
  • User instructions and first-day help

Questions

Common questions

Which email systems can you move to Microsoft 365?

Google Workspace, Exchange servers you run yourself and other Microsoft 365 tenants. For any other system, our engineers confirm the method in the plan before the move is scheduled.

Will people lose email during the move?

The plan is built so they do not. Mailboxes are copied while the old system stays in use, the mail records change in a planned window, and a final pass copies what arrived during the switch.

Do calendars and contacts move too?

Yes, with the mailbox. Meeting rooms, shared mailboxes and delegate access are listed in the inventory and set up again in Microsoft 365.

What about old PST files and archives?

We look for them during the inventory and agree with you which ones move, which are kept as archives and which can go.

What do our people have to do?

Very little: sign in to the new mailbox and, on phones, add the account again. They get instructions before the day and help on the first morning.

From the blog

Writing on Email migration

All Cloud & apps articles

Related services

On-site IT support across New Jersey, New York City and Philadelphia. Remote services wherever you are. Areas we serve →

Moving your email to Microsoft 365?

Tell us what you run today and how many mailboxes. We will plan the order of the move and how mail keeps flowing during it.

Book a strategy call

Tell us what you are working on

A few lines is enough. The engineers who do this work will reply within one business day.

Or email it.services@princetonits.com or call +1 (212) 507-9350.