Office 365 is the older name for what Microsoft now calls Microsoft 365: the same email, files and apps, under the current name. A Microsoft 365 (or Office 365) migration moves your email, calendars, contacts and files from your current system into Microsoft 365, then points your company’s email address at the new service. The safe order is to plan and clean up first, copy your data while the old system keeps running, switch your email on a date you pick, and turn on two-step sign-in right away.
Microsoft’s overview is plain about the rename: “Office 365 is now Microsoft 365”, and “Microsoft 365 includes everything you know in Office 365.” This guide uses both names because that is how people still search, and because older invoices and hosts often still say Office 365.
This guide is for small offices in Hackensack, Paramus, Ridgewood, Teaneck, Fort Lee and the rest of Bergen County. If you’d rather have someone run the move, our Microsoft 365 support and migration page explains how that works.
What actually moves in a Microsoft 365 migration?
Think of it as moving offices: the boxes, the mail forwarding and the keys all change on purpose.
- Email, calendars and contacts move from an old Exchange server, Gmail or another host into Exchange Online mailboxes. Shared mailboxes like info@ or billing@ move too.
- Office files move from a file server, a NAS box or another cloud drive into SharePoint and OneDrive.
- Team chat moves into Teams if you use another chat tool. Past chat history may not come along, so ask.
- Your email address changes where it points, through your domain’s DNS records.
- Devices get reconnected: Outlook, phones, and the quiet items like the scanner that emails PDFs or the website contact form.
Moving from Gmail, GoDaddy or an old server?
The same planning applies whether your email is at Gmail, a host such as GoDaddy, another IMAP service, or an old on-site server. The method changes with the source.
Microsoft’s mailbox migration overview and migrate email to Microsoft 365 pages describe the main paths. From Gmail or another IMAP service, the messages in each mailbox move, but contacts, calendar items and tasks don’t, and the mailboxes have to exist in Microsoft 365 first. From an Exchange Server, a cutover migration moves all mailboxes at once, a staged migration moves them in batches, and a hybrid setup lets old and new run side by side. Microsoft says cutover works for fewer than 2,000 mailboxes, but is more reasonable for 150 or fewer.
There isn’t one schedule that fits every office. Ask for a written plan and a cutover date before any work starts.
How do I plan a Microsoft 365 migration?
Spend most of your effort here. A good plan fits on one page:
- List every mailbox, including shared ones and former employees whose email you must keep.
- List where your files live: the server, laptops, a cloud drive, a USB drive in a drawer.
- Find out who controls your domain. Your registrar, or whoever runs your website, holds the DNS settings you’ll need for the switch.
- Clean up first. Remove old accounts, delete duplicates and decide what to archive instead of move.
- Pick a quiet cutover date, like an evening or weekend, and tell staff in advance.
How do I check my Microsoft 365 licensing before I move?
The plan you pick decides which security tools you get, so check before you buy. Count how many people need a mailbox, and who needs the full Office apps versus email only. Make sure former staff aren’t still licensed. Then check the security features: Microsoft says Conditional Access needs Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium. Check Microsoft’s current business plan comparison the day you decide, since features and pricing can change.
How does the mailbox migration work?
The pattern is the same each time, whatever the source. Your team keeps using the old system while the email is copied in the background. After the switch, a final sync catches whatever arrived in between, and you check a few mailboxes from each department. For large collections of PST files, Microsoft offers an import service.
The source-specific options are in the Gmail, GoDaddy or an old server section above.
How do I move my files and set up Teams?
Files take more thought than email, because a file server can hold years of folders nobody has opened. Sort before you copy: decide what to move, archive or delete. Then match the structure to how people work, with a shared company library, department libraries and private OneDrive space. Rebuild permissions on purpose, so payroll and HR folders stay limited to the people who need them. Start Teams with a few teams that match real work, like Front Office or Billing.
What is the DNS and MX cutover, in plain English?
An MX record is your domain’s mail-forwarding instruction. It tells the internet which service receives email sent to your company address, so changing it is the moment your email moves. Microsoft’s guide to connecting your domain with DNS records covers the details. The basics:
- Create users and mailboxes first. Microsoft says to do this before updating the MX record so email keeps working.
- After the change, new mail goes to Microsoft 365. Existing email stays at the old host unless you migrate it.
- Handle the old MX record. Remove it or give it a lower priority than the Microsoft 365 one.
- Keep one SPF record. If your domain already has one, add Microsoft’s value to it instead of making a second.
- Add the helpers. Autodiscover helps Outlook set itself up, and DKIM and DMARC help protect your name from fake emails.
Write down the old settings and have your registrar login ready first.
What security should I set up right after the move?
A new account with only a password is a tempting target, so finish these on day one:
- Turn on multifactor authentication for everyone. Microsoft’s MFA setup guide says security defaults are available in all Microsoft 365 organizations and are on by default for tenants created after October 2019. Check that yours are on.
- Use Conditional Access if your plan includes it. Microsoft’s templates cover requiring MFA for all users and administrators, and blocking legacy sign-in.
- Create two emergency admin accounts that aren’t tied to a person. Microsoft recommends this so you can’t get locked out.
- Limit admin rights and review outside sharing.
- Ask how your Microsoft 365 data is backed up. Our backup and recovery page explains the options. For what Microsoft keeps on its own, and where a separate backup still matters, see Microsoft 365 backup for small businesses.
For the bigger picture, see our cybersecurity checklist for Bergen County small businesses and our cybersecurity services.
What will staff notice on day one?
Most people will sign in, open Outlook or the web mailbox, and keep working. A few things often need a second look: a phone that still points at the old host, a scanner that emails PDFs, a website contact form, and shared mailboxes such as info@ or billing@. Tell staff the cutover date, how to sign in, and who to call if something looks off. Don’t cancel the old service until those checks are done.
What mistakes should I avoid?
- Switching the MX record before mailboxes exist. Mail then has nowhere to land.
- Leaving the old MX record in place, or creating a second SPF record. Both can send mail to the wrong place or get it flagged as spam.
- Forgetting the scanner, website form and phones.
- Moving every file as-is. You bring the old clutter and old permissions with you.
- Putting off MFA. The first weeks are when it matters most.
- Canceling the old service too soon. Keep it until you’ve checked mailboxes and files.
- Not telling staff. Send a short note with the date and who to call.
What does a Microsoft 365 migration checklist look like?
Before
- List all mailboxes and where files live
- Confirm who controls your domain and DNS
- Choose a plan and count licenses
- Clean up old accounts and files
- Set a cutover date and tell staff
During
- Create users and mailboxes
- Copy email and files in the background
- Update the MX and related DNS records
- Run a final sync
After
- Reconnect Outlook, phones, scanners and apps
- Turn on MFA and check admin accounts
- Check mailboxes, files and permissions
- Retire the old system once everything checks out
How do I find Microsoft 365 migration services near me in Bergen County?
Ask who handles the DNS switch, how permissions get rebuilt, what happens to your phones and scanners, and who answers questions afterward. Our guide to choosing an IT company in Bergen County has more questions to ask.
BizTechPro has been based in Pearl River, NY since 2008 and supports offices across Bergen County, plus Rockland and Westchester in New York and Passaic, Morris and Essex in New Jersey. We have local Microsoft 365 migration pages for Hackensack, Paramus, Ridgewood, Teaneck and Fort Lee. Most work is handled remotely, with site visits, when needed. After the move, our help desk is staffed Monday to Friday, 8am to 6pm. Law offices and medical practices in the county seat can see what else we cover on our Hackensack IT support page.
Frequently asked questions
Is Office 365 the same as Microsoft 365?
For most small offices, yes: Office 365 is the older name for what Microsoft now calls Microsoft 365. Microsoft’s own overview says Office 365 is now Microsoft 365, and that Microsoft 365 includes everything that was in Office 365. A few enterprise plans still use the Office 365 name, which is why you may see both on older invoices or in a search.
Which Microsoft 365 plan does a small business need?
It depends on how many people need a mailbox, whether they need the full desktop apps, and which security tools you want. Microsoft’s current business plan comparison is the place to check features the day you decide, because plans can change. We can help you match a plan to your office; we don’t set Microsoft’s prices.
Can you move us over to Microsoft 365 and help with setup?
Yes. BizTechPro can plan the move, copy email and files, handle the DNS switch, turn on two-step sign-in and help staff get connected on day one. We’re based in Pearl River, NY since 2008 and support offices across Bergen County, plus Rockland and Westchester in NY and Passaic, Morris and Essex in NJ. Most work is handled remotely, with site visits, when needed.
Will we lose email during the move?
A planned move is built so you don’t. Mailboxes are created first, old email is copied while your current system keeps working, and then the MX record is switched on a date you choose. Microsoft notes that existing mail stays at the old host unless you migrate it.
What should we clean up first, and what will staff notice on day one?
Before you copy anything, remove old accounts, delete obvious duplicates and decide what to archive instead of move. On day one, staff will sign in to Microsoft 365, reopen Outlook or the web mailbox, and may need to reconnect a phone, a scanner that emails PDFs, or a website form. A short note ahead of the cutover date, with who to call, prevents most of the confusion.
Ready to plan your Office 365 / Microsoft 365 move?
Call our sales line at (845) 747-5803 and we’ll talk through where you are today and what the move would involve.