Cloud Migration for Small Business: Plan and Checklist

A small business cloud migration moves email, shared files, and sometimes applications from equipment in your office to hosted services such as Microsoft 365. Done well, it runs in five phases: inventory, design, a pilot, the cutover, and cleanup. Staff keep working throughout, and the only moment everyone notices is the day mail starts arriving in the new system. For a typical small office, expect a few weeks from kickoff to cleanup, most of it preparation and background copying.

This guide assumes you have already decided to move. If you are still weighing it, start with server vs cloud for small business, which goes through the decision workload by workload.

What Gets Migrated?

Most small business projects are some combination of three moves:

• Email, calendars, and contacts, from an on-site Exchange server, a web host’s mailboxes, or a mix of personal accounts, into Microsoft 365 or Google Workspace.
• Shared files, from a server or network storage device into SharePoint and OneDrive, or Google Drive.
• Applications, from a local server to the vendor’s cloud version or a hosted Windows machine. This one is driven by each software vendor, so get their supported options in writing first.

The examples below use Microsoft 365. The phases apply to any platform.

A Phased Cloud Migration Plan

Phase 1: Inventory

Write down what exists before changing anything.

1. Every mailbox, shared mailbox, alias, distribution list, and forwarding rule, with sizes.
2. Every shared folder: size, who uses it, who should have access, and what is dead weight.
3. Everything that sends email as your domain: copier scan-to-email, the website contact form, accounting and CRM software.
4. Every program or shortcut that points at a server path such as \\server\share or a mapped drive letter.
5. Where your domain’s DNS is managed, and who has the login. A lost registrar password can stall the whole project, so confirm it early.
6. Your internet upload speed, since it limits how fast data can be copied out of the office.

Phase 2: Design

1. Choose licenses. As of September 2026, Microsoft lists Business Basic at $7, Business Standard at $14, and Business Premium at $22 per user per month. Basic has web and mobile apps only, Standard adds the desktop Office apps, and Premium adds device management and advanced email protection. Our Business Premium vs Standard comparison covers the differences.
2. Choose the email migration method. Microsoft’s migration path guide lists the options. From an Exchange server with fewer than 150 mailboxes, a cutover or express migration moves everything over a weekend or a few days. From other systems, IMAP migration copies email only, not calendars or contacts, which then need to be exported and imported separately. Microsoft also provides a dedicated Google Workspace migration path.
3. Design the file structure. Do not copy the old S: drive as one giant library. Plan a small number of SharePoint sites by department or function, with OneDrive for each person’s own working files. Our SharePoint guide explains how the two divide the work.
4. Plan security from day one. Decide how multi-factor authentication will be enforced, who the administrators are, and how shared mailboxes are accessed. Microsoft’s security defaults are the baseline for new accounts, and Business Premium allows finer control through Conditional Access.
5. Plan the backup. Microsoft 365 recycle bins have time limits, so arrange a separate Microsoft 365 backup to start the day data arrives.

Phase 3: Build and Pilot

1. Set up the Microsoft 365 account, add and verify your domain, create users and groups, and assign licenses. Verifying the domain does not affect mail flow.
2. Configure security settings and the backup before any data arrives.
3. Clean up file and folder names. SharePoint and OneDrive do not allow certain characters (" * : < > ? / \ |), and the full path, including the file name, is limited to 400 characters.
4. Pilot with two or three people. Migrate their mailboxes and one shared folder, have them work normally for a few days, and fix what they find.

Phase 4: Migrate and Cut Over

1. Start the bulk copy of mailboxes in the background while the old system stays live. For files, Microsoft offers two free tools: the SharePoint Migration Tool, which runs on a computer in your office, and Migration Manager in the SharePoint admin center.
2. A few days before cutover, lower the time to live (TTL) on your mail-related DNS records so the change spreads quickly.
3. Choose a quiet time, such as a Friday evening, and work through the cutover checklist below.
4. Run a final sync to catch mail and files that changed since the first copy.

Phase 5: Clean Up

1. Keep the old system in a read-only or powered-but-unused state for an agreed period, commonly two to four weeks, so anything missed can be retrieved.
2. Remove old drive mappings and shortcuts, and redirect scanners and applications.
3. Take a final backup of the old server, then retire it and wipe its drives.
4. Raise DNS TTL values back to normal.
5. Update your documentation: administrator accounts, license counts, DNS records, backup details, and your disaster recovery plan.

Cutover Day Checklist

Before

• All users exist, are licensed, and have signed in once with multi-factor authentication set up
• Mailbox pre-copy finished with no unresolved errors
• Verified backup of the old system completed today
• DNS login tested, TTL already lowered
• Staff told what will change, when, and how to get help on Monday

During

• Change the MX record to point to Microsoft 365
• Update the SPF record to v=spf1 include:spf.protection.outlook.com -all, plus any other legitimate senders
• Publish the two DKIM CNAME records and enable DKIM signing for your domain
• Confirm the Autodiscover record so Outlook finds the new mailboxes
• Run the final mailbox and file sync
• Set old file shares to read-only

After

• Send test messages both ways with Gmail and Outlook.com accounts, and confirm SPF, DKIM, and DMARC pass
• Test shared mailboxes, shared calendars, and distribution lists
• Test scan-to-email, the website contact form, and any software that sends email
• Set up Outlook and phone mail on each device
• Confirm the new backup ran and restore one test item
• Be available to staff on the first working morning

Do not skip the email authentication steps. Without them, outbound mail can land in spam. Our guide to SPF, DKIM, and DMARC has the record formats and the tag-by-tag explanation.

How Long Does a Cloud Migration Take?

Microsoft notes that migration performance varies with your network, mailbox sizes, and the method used, so nobody can quote a fixed number. The factors that set your timeline:

• Data volume and upload speed. This is simple arithmetic. At a sustained 20 Mbps upload, 100 GB takes roughly 11 hours to transfer and 1 TB takes about four and a half days. Real throughput is lower because of overhead and service throttling, and copies are usually limited to evenings so daytime work is not slowed.
• Cleanup effort. Sorting permissions and years of clutter in a file share can take longer than the copy itself.
• Number of people and devices. Each computer and phone needs its mail profile set up after cutover.
• Third parties. Waiting on a registrar login, a software vendor, or a copier technician adds days.

As an illustration, a ten person office with modest mailboxes and a couple hundred gigabytes of files might spend a week on inventory and design, a week on setup and pilot, a week or two of background copying, one evening for cutover, and two to four weeks of cleanup in the background. Large file collections, line-of-business applications, or a compliance review stretch that.

Common Pitfalls

• Outbound mail goes to spam after cutover because SPF, DKIM, and DMARC were not updated along with the MX record.
• Folders get missed because nobody listed every share, or a department kept files on a local computer.
• Permissions are copied blindly. Old access lists move with the files, including access for people who left long ago.
• The wrong license is bought. Business Basic has no desktop Office apps, which surprises offices that expected Word and Excel installed on each computer.
• Calendars and contacts are left behind on an IMAP migration, which copies email only.
• Long paths and illegal characters cause files to fail to copy, and nobody reads the error report.
• No backup of the new environment, on the assumption that cloud data cannot be lost.
• Multi-factor authentication is postponed until later, leaving brand-new accounts protected by passwords alone.
• The old server is switched off too soon, before anyone confirms that nothing still depends on it.
• Cutover lands during a busy period. Avoid month end, tax deadlines, and the week before a holiday.

When Should You Wait, or Not Migrate Everything?

Migration is not always the right next step. Hold off, or migrate only part of your systems, when:

• A critical application has no supported cloud or hosted option. Email and files can still move while that application stays local.
• Your internet connection is slow or unreliable and cannot be improved yet.
• You are in your busiest season. A rushed cutover costs more than a delayed one.
• Your daily work involves very large files, such as CAD or video, that perform poorly over your connection. A hybrid setup usually suits that better.

Common Questions

Will email stop working during the migration?

It should not. Mailboxes are copied in the background while the old system keeps running. At cutover the MX record changes, and mail is delivered to either the old or the new system while the change spreads, then a final sync picks up stragglers. The main change staff notice is that Outlook needs to be set up again.

Can we migrate ourselves?

A very small office moving a handful of mailboxes from a web host can, using Microsoft’s setup wizard and IMAP migration. The risk grows with an Exchange server, shared mailboxes, large file shares, or several services that send email as your domain. Mistakes in DNS and email authentication are the ones to worry about, because they affect every message you send.

Do we keep the old server after the move?

Keep it powered and read-only for an agreed period, commonly two to four weeks, so that anything missed can be retrieved. Then take a final backup, keep that backup according to your retention rules, wipe the drives, and recycle the hardware. If one application still needs a local machine, the old server may be replaced by something much smaller.

Is our data automatically backed up once it is in Microsoft 365?

Microsoft keeps the service available and provides recycle bins and version history, but those have time limits and are not an independent copy. A separate backup of mailboxes, OneDrive, and SharePoint protects against deletions noticed late, ransomware that syncs, and account compromise. Set it up before the migration, not after.

How Coastal Growth Co. Can Help

We plan and carry out cloud migrations for small businesses: the inventory, license and structure design, security and backup setup, a pilot, the cutover, and cleanup, with expected interruptions agreed ahead of time. The work is part of our cloud and email services, and you can read more about how we handle Microsoft 365 in South Orange County. Get in touch to describe what you have today, and we will agree on scope and price before any paid work begins.