Microsoft 365 Migration Checklist for NJ Businesses
Every botched email migration we've ever been called in to rescue failed in the planning phase, not the cutover. This is the checklist that prevents the rescue call.
Email migrations have a strange reputation: the actual data transfer is the easy part. Modern migration tooling moves mailboxes reliably while everyone sleeps. What goes wrong is everything around it, the domain registrar login nobody can find, the 70GB mailbox that won't finish syncing, the scan-to-email copier nobody remembered, and the brand-new tenant left wide open with no MFA. We've run this project for offices from Clifton to Midtown, and this is the phased checklist we work from every time.
Phase 1: Inventory (two weeks out)
This phase is pure information-gathering, and it's where the surprises live:
- Find your DNS and domain access. Who registered your domain, GoDaddy, Network Solutions, a web designer from 2014? You will need working logins for the registrar and wherever DNS is hosted. In roughly a third of our migrations, recovering this access is the single longest task, so start here. If the domain is registered to a former employee's or old vendor's email, fix that now.
- Measure every mailbox. Export a list of mailboxes with sizes. A 4GB mailbox syncs in minutes; a 60GB mailbox can take a day or more. The sizes determine your timeline and whether anyone needs pre-migration cleanup.
- Hunt down PST archives. Years of "archived" email lives in PST files on individual C: drives, invisible to any server-side migration. Ask every user, then verify with a scan. Importing them during the project costs little; recovering one from a dead laptop two years later costs plenty.
- List everything that sends email that isn't a person. Copiers that scan-to-email, the accounting system that emails invoices, website contact forms, door alarm notifications. Each needs reconfiguring at cutover, and they're the things nobody notices until Monday.
- Document shared mailboxes, aliases, and distribution lists. info@, billing@, the list that goes to "everyone", map them all to their M365 equivalents on paper before touching anything.
Phase 2: Decisions (one week out)
- Pick licensing deliberately. For most NJ small businesses the real choice is Business Standard ($12.50/user/month) versus Business Premium ($22), and we push Premium hard for any business with compliance or insurance requirements, because it includes Intune, conditional access, and Defender for Office 365. The $9.50 difference is cheaper than buying those controls separately, and your cyber insurance questionnaire will ask about exactly these features. Mix licenses freely: the warehouse PC that only prints labels doesn't need Premium.
- Choose cutover vs. staged. Under ~50 mailboxes, a cutover migration (everyone moves the same weekend) is almost always right: one weekend of disruption, no co-existence complexity. Staged/hybrid migrations exist for bigger orgs and have their place, but for a 20-person office they add weeks of complexity to avoid one weekend of inconvenience. Take the weekend.
- Schedule around your business. Not month-end if you're an accounting firm, not closing week if you're a law office. Friday 5 p.m. to Monday 7 a.m. is the standard window.
- Tell your people what to expect. A two-paragraph email beats a town hall: what's changing, what Monday morning looks like, and that someone will be onsite to help. Surprised users generate tickets; informed users generate patience.
Phase 3: The weekend itself
A good cutover is boring by design. Mail flow is redirected by lowering the DNS TTL in advance (Friday afternoon's quiet hero move), final mailbox sync runs overnight Friday, MX records switch Saturday, and the weekend's remaining hours go to reconfiguring the copiers, invoice systems, and phones from the Phase 1 inventory, plus spot-checking that mail flows in and out. Sunday is for Outlook profiles and mobile devices on a sample of machines, so Monday's onsite support is mop-up rather than triage. If your office still runs an on-premises Exchange or aging file server, the migration weekend is also the natural moment to revisit the bigger architecture question, we laid out that framework in server vs. cloud for North Jersey offices.
Phase 4: The security configuration most migrations skip
Here's our strongest opinion in this guide: a migration isn't finished when the mail flows, it's finished when the tenant is hardened. A fresh M365 tenant with default settings is a soft target, and attackers specifically hunt newly migrated companies because they know the security pass often never happens. Week one after cutover:
- Enforce MFA for every account via conditional access or security defaults, no exceptions, including (especially) the owner.
- Publish SPF, update DKIM, and add a DMARC record. You're already in DNS that week; there is no better moment. These three records stop criminals from spoofing your domain and are now table stakes for deliverability, Google and Microsoft both throttle unauthenticated senders.
- Disable legacy authentication protocols (POP/IMAP/SMTP basic auth), which bypass MFA entirely.
- Set up mailbox auditing and alerting for suspicious sign-ins and inbox forwarding rules, the calling card of business email compromise.
- Start backing up the tenant. Microsoft's retention is not a backup; deleted means gone after the retention window. Third-party Microsoft 365 backup runs a few dollars per user and closes the gap.
This phase is the difference between a migration and a liability transfer, and it's standard in every migration we run through our Microsoft 365 support practice and for managed IT clients.
What it costs and when to get help
A properly run cutover for a 15-25 person NJ office typically lands between $3,000 and $8,000 depending on mailbox sizes, PST volume, and how many non-human senders are hiding in the building. A motivated office manager can DIY a tiny migration, but the failure modes (mail loops, lost archives, a wide-open tenant) cost far more than the project fee, which is why even security-conscious do-it-yourselfers usually hand off Phase 4 at minimum. We run migrations across North Jersey and the New York City metro most months of the year.
More practical guides on the Setnom blog, and if a migration is on your horizon, book a free assessment and we'll size yours with real numbers.
A boring cutover is a successful cutover
This is the actual rhythm of a well-planned migration weekend. If any step feels dramatic, Phase 1 was skipped.
- Friday 3 p.m. Lower DNS TTL, confirm final user list, freeze mailbox changes.
- Friday night Final mailbox sync runs while everyone goes home on time.
- Saturday Switch MX records, verify inbound/outbound mail, reconfigure copiers and apps that send email.
- Sunday Rebuild Outlook profiles on sample machines, test mobile devices, import flagged PSTs.
- Monday 7 a.m. Support onsite before the first employee logs in, mop-up, not triage.
Migrate to Microsoft 365 without losing a single email, or a weekend of sleep.
Book a free assessment. We'll inventory your mailboxes, DNS, and the copier nobody remembered, then hand you a fixed-price migration plan with the security hardening included, not skipped.
- (646) 719-0490
- info@setnomconsulting.com
- Response within one business day