Microsoft 365 Migration for New Jersey Businesses: What Actually Happens, Step by Step

Most New Jersey businesses that call about Microsoft 365 are not asking "should we move?" They have already decided. The questions are practical: how long will it take, what breaks, who is going to be on the phone when email stops at 8 a.m., and what does it cost to have someone else handle it.

This guide answers those questions in order. It is written for owners and office managers, not IT people, and it covers the migration path we see most often in South Jersey: a 10–150 person organization moving from an on-premises Exchange server, a hosted email provider, or Google Workspace to Microsoft 365.

What a migration actually moves

"Migrating to Microsoft 365" is really four separate moves, and each has its own risk:

  1. Email, calendars and contacts. Every mailbox, including shared mailboxes (info@, billing@) and old employees' archives you still need for legal or customer-history reasons.
  2. Files. Whatever lives on your file server or in Google Drive moves to SharePoint and OneDrive. This is where most of the planning time goes, because folder structures and permissions have usually grown for a decade without anyone designing them.
  3. Identity. Who can log in, with what password, and with what second factor. Microsoft 365 becomes the place your staff sign in to everything, so this has to be right before anything else moves.
  4. The desktop apps. Word, Excel, Outlook and Teams installed and signed in on every computer, with old versions removed.

A migration that only moves email is a weekend job. One that moves all four properly is a project with a plan, and it should be treated like one.

A realistic timeline for a New Jersey small business

For a typical 25–75 person organization with one office, expect three to six weeks from kickoff to the last computer being signed in. That sounds long for something that "just moves email." It is long because the parts that protect you — the inventory, the permission cleanup, the test migration — are the parts you cannot see.

Week 1 — Discovery. An inventory of every mailbox, shared mailbox, distribution list, file share and application that sends email (your scanner, your line-of-business software, your website contact form all send mail and all break if forgotten). Licensing is decided here too: most small organizations end up on Business Standard or Business Premium, and the Premium tier matters if you need the built-in security controls your cyber-insurance application asks about.

Week 2 — Identity and security first. The Microsoft 365 tenant is set up, your domain is verified, users are created, and multi-factor authentication is turned on before a single email is moved. Doing security last is how migrations create new problems.

Weeks 2–3 — Pilot. A handful of users — ideally including one skeptic — are moved first. Their mail flows both ways, their files are checked, their phones are set up. Whatever goes wrong here goes wrong for five people, not fifty.

Weeks 3–4 — The main move. Mailboxes are migrated in batches, usually overnight or over a weekend. The DNS "switch" that routes new mail to Microsoft 365 is flipped once everything is staged. Files move in parallel, with permissions mapped rather than copied blindly.

Weeks 4–6 — Cleanup. Old servers decommissioned, licenses right-sized, staff trained on the things that changed (Teams, OneDrive sync, the new sign-in). This phase gets skipped by anyone in a hurry, and it is where the long-term cost savings actually show up.

Larger organizations, multiple offices, or an older on-premises Exchange server stretch this. A school district or a municipality with departmental email domains and records-retention rules can reasonably take two to three months.

Where migrations go wrong

Having done this many times across South Jersey, the failures are rarely technical. They cluster around a few predictable things:

  • The forgotten senders. The copier, the alarm panel, the accounting software, the website form — anything that emails on your behalf needs to be re-pointed. Discovery that misses these produces a quiet week of "we didn't get your invoice."
  • Permissions copied instead of designed. Moving a file server to SharePoint one-for-one usually recreates every bad decision from the last ten years. A short permission-design session before the move pays for itself.
  • Mail flow switched too early. If DNS is changed before every mailbox is staged, mail arrives in a mailbox nobody is watching. Experienced teams stage everything, verify, then switch.
  • Phones. Half your staff read email on their phones. Each one needs the Outlook app set up and the old account removed, or you will field "I'm not getting email" calls for a week.
  • Nobody owns the old system's shutdown. The on-prem server keeps running, keeps costing, and keeps a stale copy of your data for a year because nobody was assigned to turn it off.

What it costs, in general terms

Costs fall into three buckets:

  1. Licensing. Microsoft publishes per-user monthly pricing; it is the same whoever you buy it through. The real decision is which tier, and whether you need add-ons for archiving, backup or advanced security.
  2. The migration project itself. For a small organization this is typically priced as a fixed project. Market pricing varies with mailbox count, file volume and how messy the starting point is. Rivell's managed IT pricing guide explains how we structure project and ongoing pricing.
  3. Ongoing administration. Someone has to add and remove users, manage licenses, apply security settings and answer "how do I share this folder." That is either an internal person's time or part of a managed IT services agreement.

One thing worth saying plainly: Microsoft 365 is not automatically backed up in the way most people assume. Microsoft keeps the service running; retrieving a file an employee deleted eight months ago is your responsibility. Budget for a third-party backup, and ask any provider you talk to how they handle it.

Do you need a provider, or can you do it yourself?

If you have under ten users, one domain, no shared mailboxes and no file server, Microsoft's own tools can get you through a self-service move. Above that, the honest answer is that the hourly cost of your own staff fumbling through it — plus the week of disruption — usually exceeds what a provider charges to do it in a controlled way.

Choose a provider who will show you the inventory before the move, insists on multi-factor authentication from day one, has a written rollback plan, and will be reachable the first Monday morning after the switch. If they cannot answer "what happens if a mailbox fails to migrate," keep looking. Our guide to comparing New Jersey managed IT providers has a longer list of questions.

After the move: the part most businesses skip

A migration is a one-time project; Microsoft 365 is an ongoing responsibility. Three things to put on the calendar:

  • Quarterly license review. Departed employees' licenses are the most common wasted spend.
  • Security baseline check. Microsoft changes defaults regularly. Conditional access, MFA coverage and external-sharing settings should be reviewed, not assumed.
  • Training. Teams and OneDrive change how people work. A 45-minute session a month after go-live resolves more support tickets than any amount of documentation.

Frequently asked questions

How long will email be down during the migration?
With a staged migration, it should not be down at all. Mail keeps flowing to the old system until the moment DNS is switched, at which point it starts flowing to Microsoft 365. Users may need to re-enter a password. If a provider tells you to expect a day of downtime, ask why.

Can we keep our old emails?
Yes. Historic mail is migrated with the mailbox. Very large archives, or mail from employees who left years ago, are usually moved to archive mailboxes or shared mailboxes so you keep the record without paying for a full license.

We are on Google Workspace. Is it harder?
Different, not harder. Mail and calendars move cleanly. Google Drive to SharePoint needs more planning because Google's sharing model is looser than Microsoft's. Expect the file portion to take longer than the email portion.

Does Microsoft 365 meet HIPAA or other compliance requirements?
Microsoft offers the agreements and controls needed for regulated industries, but compliance depends on how the tenant is configured and used. A medical practice or law firm should treat the migration as the moment to set those controls up correctly. Our healthcare IT and law firm IT pages cover what that looks like.

What if we already have an IT person?
Many migrations we run are co-managed: your internal person keeps the day-to-day, and we handle the project and the parts they have not done before. See co-managed IT services.

Next step

If you are planning a move, the most useful first step is an inventory of what you have now. Rivell offers a no-cost IT assessment for New Jersey organizations that covers exactly that: mailboxes, file shares, the applications that send mail, and the security settings you will need in place before anything moves. You will leave with a written plan whether or not you work with us. More on our Microsoft 365 consulting services.

Facebook
Twitter
LinkedIn