A Practical Cloud Migration Checklist for Long Island Small Businesses

What "cloud migration" actually means

For most Long Island SMBs, cloud migration means three projects, often run in sequence:

1. Email to Microsoft 365 or Google Workspace (4–8 weeks)
2. File server to SharePoint, OneDrive, or Google Drive (8–16 weeks)
3. Line-of-business apps to SaaS or Azure/AWS (varies wildly)

Email migration

Cleanest of the three. Most under-50-user shops can cut over a weekend. Allow 4 weeks of prep: assess current Exchange or POP/IMAP setup, set up Microsoft 365, configure DNS, run pilot for IT and select power users, train, then cut over.

Common gotcha: shared mailboxes. They don't migrate the way personal mailboxes do, and the new permissions model surprises people.

File server migration

Hardest of the three. SharePoint and OneDrive don't behave like a shared drive. The folder structure that worked for 12 years on a Windows server probably doesn't fit SharePoint's permission model. Plan a permissions cleanup as part of the migration; resist the urge to lift-and-shift the existing structure.

Timeline: 8–16 weeks for a shop with under 5 TB of data and standard departmental sharing.

Line-of-business migration

This depends entirely on the application. QuickBooks Desktop to QuickBooks Online is a few hours. A custom Access database used by accounting since 2001 might be a 6-month rebuild. Scope this as a separate engagement, never as a casual addition to email and file migrations.

Real costs

For a 25-person Long Island business:

• Email + Microsoft 365 setup: a one-time project, scoped on mailbox count
• File server to SharePoint: a one-time project, scoped on data volume
• Recurring Microsoft 365 licenses: billed per user per month for Business Premium

Things to fight for during the migration

• Schedule cutovers outside business hours, always
• Keep the old system in read-only mode for 30 days post-cutover
• Document the decisions, not just the configuration — "why did we do it this way" matters in two years
• Train end users before the cutover, not the day of

When cloud is the wrong answer

Some workloads still belong on-prem: legacy industrial control systems, line-of-business apps with hardware dongles, and anything where bandwidth costs would explode. We've helped clients un-migrate from cloud back to on-prem when the math didn't work. The cloud is a tool, not a religion.

Before you migrate: inventory checklist

Most migration problems come from something nobody wrote down. Before any move, list all of this.

• Every mailbox, including shared mailboxes and distribution lists
• Every shared folder, who uses it and who should have access
• Software that runs on the old server, and whether a cloud version exists
• Scanners and copiers that send to email or folders
• Devices with saved passwords, like phones, tablets and front-desk computers
• Domain registrar and DNS logins
• Current licenses and when they renew

Cutover weekend checklist

The first 30 days after

Keep the old system read-only for at least 30 days. Somebody will always find a folder they forgot about.

Use those weeks to clean up. Turn on multi-factor sign-in for every account, remove licenses nobody uses, and check sharing settings so files are not open to the whole company or the public. A migration is the best chance you will get to fix years of messy permissions.

When to bring in help

A small office can move email on its own if it is careful. File servers, shared mailboxes and anything tied to line-of-business software are where most do-it-yourself moves go wrong. Our cloud services page covers how we handle migrations, and the longer guide to cloud migration services on Long Island explains timelines and what affects cost. If the cloud move is part of a bigger plan, IT consulting can help you decide what moves and what stays.