The best cloud migration guide for a business under 20 employees is Microsoft 365 Business Standard at $12.50 per user per month, combining SharePoint for files, Exchange for email, and Teams for communication. A 20-person team in Daytona Beach or DeLand can run a complete cloud infrastructure for $250 to $450 per month — replacing on-premise servers, local file shares, and most IT complexity with a single subscription that Microsoft manages.

The ideal cloud setup for a small business under 20 employees is Microsoft 365 Business Standard ($12.50 per user per month) combined with SharePoint for files, Exchange for email, Teams for communication, and basic Azure services for anything that does not fit neatly into the Microsoft 365 box. This combination costs between $250 and $450 per month for a 20-person team and replaces on-premise servers, local file shares, and most of the IT headaches that keep small business owners up at night in DeLand, Daytona Beach, and across Volusia County.

I want to have an honest conversation about cloud setups for small businesses, because the industry has a tendency to overcomplicate this. Talk to three different IT consultants and you will get three different architectures, each more elaborate than the last. Kubernetes clusters. Multi-region failover. Microservices. Zero-trust networks with hardware security keys. All of it technically excellent, and all of it wildly inappropriate for a 12-person accounting firm or a 15-person real estate agency.

Here is the thing nobody in IT consulting wants to admit: for most businesses under 20 employees, the “good enough” cloud setup is not just acceptable, it is optimal. The fancier architectures introduce complexity that requires expertise to maintain, and that expertise either costs money (hiring an IT person or paying for managed services) or costs time (you learning it yourself instead of running your business). Neither of those trade-offs makes sense when Microsoft has already built everything you need into a single subscription.

I have helped businesses in DeLand, Port Orange, and throughout the Daytona Beach metro area migrate to the cloud. The ones that end up happiest are not the ones with the most sophisticated architecture. They are the ones with the simplest setup that actually meets their needs. That is what we are building today.

What “Good Enough” Actually Means

Let me define what I mean by “good enough” because it is not a compromise. It is a philosophy.

A good enough cloud setup meets these criteria:

It works reliably. 99.9% uptime or better, which Microsoft 365 guarantees in its SLA.
It is secure enough. Multi-factor authentication, encrypted data at rest and in transit, compliance with major frameworks.
It is maintainable. You or a non-specialist IT person can manage it without calling in experts every week.
It is affordable. The total cost is predictable and scales linearly with your team size.
It is recoverable. If something goes wrong, you can restore service within hours, not days.

What “good enough” is not:

It is not a multi-cloud strategy spanning Azure, AWS, and Google Cloud.
It is not a custom-built application platform with CI/CD pipelines.
It is not an architecture designed to handle 10x your current load “just in case.”

If your business has fewer than 20 employees, a single vendor cloud strategy built on Microsoft 365 will handle 95% of your needs. For the other 5%, we will add targeted solutions as needed. That is the approach, and it works.

The Core Stack: Microsoft 365 Business Standard

The foundation of your cloud setup is a Microsoft 365 Business Standard subscription. At $12.50 per user per month (rising to $14 in July 2026), it includes everything most small businesses need:

Email and Calendar through Exchange Online. Custom domain email ([email protected]), 50GB mailbox per user, shared mailboxes for departments (info@, support@, sales@), and calendar sharing across the team. This replaces your on-premise Exchange server or that aging POP3 email setup you have been running since 2015.

File Storage and Sharing through SharePoint Online and OneDrive. Each user gets 1TB of personal storage via OneDrive, and the organization gets 1TB plus 10GB per licensed user for shared SharePoint sites. For a 20-person team, that is 1.2TB of shared storage plus 20TB of personal storage. That is almost certainly more than you are using on your current file server.

Communication through Microsoft Teams. Chat, video conferencing, screen sharing, and phone system integration. Teams replaces Slack, Zoom, and whatever internal chat tool your team cobbled together during the pandemic. For businesses in Ormond Beach and New Smyrna Beach with remote or hybrid workers, Teams becomes the virtual office.

Productivity Apps including Word, Excel, PowerPoint, and Outlook desktop apps. Business Standard includes full desktop installations, not just web versions. This matters if your team works offline or needs the advanced features that only exist in the desktop apps.

Collaboration Tools including Microsoft Lists, Forms, Planner, and Bookings. Most businesses do not realize these are included, and they replace standalone tools like Trello (Planner), SurveyMonkey (Forms), and Calendly (Bookings).

Here is what a 20-person team costs:

Plan	Per User/Month	20 Users/Month	20 Users/Year
Business Basic (web apps only)	$6.00	$120	$1,440
Business Standard (desktop apps)	$12.50	$250	$3,000
Business Premium (+ security)	$22.00	$440	$5,280

For most businesses, Business Standard is the sweet spot. Business Basic lacks desktop Office apps, which frustrates employees who are used to the full Excel and Word experience. Business Premium adds advanced security features like Microsoft Defender for Business and Intune device management, which are nice but not essential for a business with fewer than 20 people and a cooperative team.

One important note: Microsoft is raising prices in July 2026. Business Basic goes from $6 to $7 per user per month, and Business Standard goes from $12.50 to $14. If you are reading this before July, lock in annual billing at the current rates.

Setting Up Your M365 Tenant (The Right Way)

Here is the step-by-step setup process. I am going to walk through this in the order you should do things, because the order matters. Skip ahead and you will end up reconfiguring things twice.

Step 1: Buy the Subscription and Add Your Domain

Go to microsoft365.com/business, pick your plan, and sign up. Use your personal email for the initial account since you do not have business email yet. Microsoft will create a temporary [yourname].onmicrosoft.com domain.

Then immediately add your custom domain. In the Microsoft 365 Admin Center, go to Settings > Domains > Add Domain. You will need to verify ownership by adding a TXT record at your domain registrar (GoDaddy, Namecheap, Cloudflare, wherever your domain lives). Microsoft walks you through this, and it takes about 15 minutes. If this resonates, our post on Azure Key Vault and Certificate Automation: A Production Guide goes deeper into the specifics.

Do this first because every user you create after this point will automatically get a @yourbusiness.com email address instead of an @yourname.onmicrosoft.com address. If you create users first, you will have to go back and change their primary email, which creates confusion.

Step 2: Enable Security Defaults (MFA for Everyone)

Before you add a single user, turn on Security Defaults in Azure Entra ID. This is the single most impactful security measure you can take, and it is free.

In the Microsoft 365 Admin Center, go to Azure Active Directory (it is still labeled that way in some places even though it is now called Entra ID) > Properties > Manage Security Defaults > Enable Security Defaults.

This forces every user to register for multi-factor authentication. When they log in from a new device, they will need to approve the login on their phone through the Microsoft Authenticator app. Yes, some of your employees will grumble about this. Tell them that 99.9% of account compromise attacks are prevented by MFA. That is not a marketing number; that is from Microsoft’s own security research.

For a business in DeLand or anywhere in Volusia County, this alone puts you ahead of 80% of small businesses in terms of security posture. No firewall appliance, no expensive security subscription. Just MFA.

Step 3: Create User Accounts

Now create accounts for your team. In the Admin Center, go to Users > Active Users > Add a User. For each person, set:

Display name and username ([email protected])
A temporary password (they will change it on first login)
Assign the Microsoft 365 Business Standard license
Set their department and job title (this helps with SharePoint permissions later)

Pro tip for DeLand businesses with seasonal staff: Do not create accounts for temporary employees on the same plan as your full-time team. Microsoft 365 Business Basic at $6 per user per month gives them email and web apps without the desktop app cost. When they leave, disable their account (do not delete it immediately since you may need access to their mailbox for 30 days).

Step 4: Structure Your SharePoint Sites

This is where most small businesses go wrong. They create one giant document library and dump everything in it. Three months later, nobody can find anything and people are emailing files to each other again.

Instead, create SharePoint sites that map to your business structure:

SharePoint Site	Purpose	Access
Company-Wide	Policies, handbooks, templates	All employees
Finance	Invoices, budgets, tax documents	Finance team + owners
Sales	Proposals, contracts, client info	Sales team + owners
Operations	SOPs, vendor agreements, schedules	Operations team + owners
HR	Employee records, benefits info	HR + owners only

Each site gets its own document library, its own permissions, and its own Teams channel (SharePoint and Teams are connected behind the scenes). An accountant in Port Orange can access Finance files but cannot browse HR documents. A salesperson in Daytona Beach sees Sales materials but not financial records.

This structure takes 30 minutes to set up and saves hundreds of hours of confusion over the following year.

Step 5: Set Up Teams Channels

Create a Microsoft Teams organization with channels that mirror your SharePoint sites. When you create a Teams channel, it automatically creates a corresponding SharePoint folder, so files shared in Teams are stored in SharePoint. This means your team can work in Teams (which they will use daily) without worrying about where files end up (they are all in SharePoint, properly organized).

Recommended channel structure for a 20-person business:

General – Company announcements, all-hands updates
Sales – Deal discussions, pipeline updates, client questions
Operations – Day-to-day coordination, scheduling, vendor issues
Finance – Invoice questions, expense approvals, budget discussions
IT Help – Internal tech support requests, password resets
Water Cooler – Non-work chat, birthdays, social stuff (this matters more than you think for team cohesion, especially if you have remote workers in New Smyrna Beach or Deltona)

Step 6: Configure Email Basics

Exchange Online handles most email configuration automatically, but there are a few things you should set up manually:

Shared mailboxes for common addresses: info@, support@, sales@, billing@. These do not require additional licenses. Multiple people can send and receive from these addresses, and responses are threaded so the whole team sees the conversation.

Email signatures are best managed through a transport rule in Exchange. Go to Admin Center > Exchange > Mail Flow > Rules, and create a rule that appends a standardized signature to outbound email. This ensures every employee uses the same format, which matters for professional appearance.

Anti-spam filtering is enabled by default, but review the settings in the Security & Compliance Center. Microsoft’s built-in spam filtering catches about 99% of junk mail. If you are getting false positives (legitimate email going to spam), add the sender’s domain to your safe sender list.

What Else You Might Need (And What You Definitely Do Not)

The M365 stack covers email, files, communication, and productivity. But some businesses have needs that go beyond that. Here is an honest assessment of what is worth adding and what is not.

Worth Adding: A Cloud Backup Service

Microsoft 365 retains deleted files for 93 days and deleted email for 14 days (or 30 with a retention policy). That is enough for “oops, I deleted that file” recovery. But it is not a real backup strategy. If a ransomware attack encrypts your SharePoint files, or if a disgruntled employee bulk-deletes everything before leaving, you need a proper backup.

Services like Veeam Backup for Microsoft 365, Acronis, or Backupify cost $2-5 per user per month and create independent backups of your M365 data. For a 20-person team, that is $40-100 per month. Worth it.

Worth Adding: A Line-of-Business App Host (If Needed)

Some businesses run software that cannot move to the cloud natively. A custom inventory management system. An old accounting package that only runs on Windows Server. Industry-specific software that the vendor has not cloud-enabled yet.

For these situations, an Azure Virtual Machine running Windows Server works. An Azure B2s VM ($30 per month) handles most light line-of-business applications. Your employees connect to it via Remote Desktop, and the application runs in the cloud even though it was never designed for it. This is not elegant, but it works, and it eliminates the physical server sitting in your closet. We cover this in more detail in How to Build a Self-Healing Server with PowerShell and Scheduled Tasks.

Probably Not Worth It: Azure Virtual Desktop

Azure Virtual Desktop (AVD) gives every employee a full Windows desktop in the cloud. It sounds appealing, but for businesses under 20 employees, it is overkill. The licensing is complex (you need Windows E3 or E5 licenses on top of M365), the management overhead is significant, and the per-user cost can easily exceed $50 per month. Unless you have a specific compliance reason to use virtual desktops (like a healthcare practice in Daytona Beach that needs HIPAA workstations), skip this.

Definitely Not Worth It: A Custom Azure Infrastructure

If someone suggests you need an Azure App Service, Azure SQL Database, Azure Functions, API Management, and a virtual network with site-to-site VPN, politely ask if they are building infrastructure for your 15-person company or for Netflix. These services are powerful and appropriate for software companies and enterprises. They are not appropriate for a dental practice in DeLand that just wants email and shared files.

The Security Checklist (The Stuff That Actually Matters)

I could write a 50-page security policy, but for a business under 20 employees, these six items cover 95% of your risk surface:

MFA on every account. We already did this in Step 2. Non-negotiable.
Conditional Access policies (Business Premium only). If you upgrade to Premium, set policies that block sign-ins from countries where you do not do business, require MFA from unmanaged devices, and block legacy authentication protocols (IMAP, POP3, SMTP Basic Auth). These three policies close the most common attack vectors.
Admin accounts separated. Your daily account should not be a global administrator. Create a separate admin account ([email protected]) that you only use for admin tasks. If your daily account gets compromised, the attacker does not get admin access.
Self-service password reset enabled. In Entra ID, enable SSPR so employees can reset their own passwords without calling you. This reduces help desk tickets by 20-40% and eliminates the security risk of IT people resetting passwords over the phone without proper identity verification.
External sharing restricted. In SharePoint admin settings, set external sharing to “Existing guests only” or “Only people in your organization.” This prevents employees from accidentally sharing sensitive files with external email addresses. When you need to share with a client or vendor, you can create a guest account with specific access.
Device compliance (Business Premium only). If your team uses personal devices, Intune can enforce basic policies: require a PIN, require encryption, block jailbroken devices, remotely wipe company data if the device is lost. This does not control the employee’s personal device; it only manages the M365 apps and data on it.

Verifying Your Setup

After you have completed the setup, run this PowerShell script to verify the key configuration items:

# verify-m365-setup.ps1 - Quick M365 configuration health check
# Requires: Microsoft.Graph PowerShell module
# Install: Install-Module Microsoft.Graph -Scope CurrentUser

Connect-MgGraph -Scopes "User.Read.All","Organization.Read.All","Policy.Read.All"

Write-Host "=== M365 Setup Verification ===" -ForegroundColor Cyan

# Check 1: Custom domain
$domains = Get-MgDomain
$customDomains = $domains | Where-Object { -not $_.IsInitial }
if ($customDomains) {
    Write-Host "[PASS] Custom domain configured: $($customDomains.Id -join ', ')" -ForegroundColor Green
} else {
    Write-Host "[FAIL] No custom domain - using .onmicrosoft.com only" -ForegroundColor Red
}

# Check 2: MFA status
$policies = Get-MgIdentityConditionalAccessPolicy
$mfaPolicy = $policies | Where-Object { $_.DisplayName -like "*MFA*" -or $_.GrantControls.BuiltInControls -contains "mfa" }
if ($mfaPolicy) {
    Write-Host "[PASS] MFA policy found" -ForegroundColor Green
} else {
    Write-Host "[WARN] No explicit MFA policy - check Security Defaults" -ForegroundColor Yellow
}

# Check 3: Licensed users
$users = Get-MgUser -All -Property DisplayName,AssignedLicenses
$licensed = $users | Where-Object { $_.AssignedLicenses.Count -gt 0 }
Write-Host "[INFO] Licensed users: $($licensed.Count)" -ForegroundColor Cyan

# Check 4: SharePoint sites
$sites = Get-MgSite -Search "*"
Write-Host "[INFO] SharePoint sites: $($sites.Count)" -ForegroundColor Cyan

Write-Host ""
Write-Host "=== Verification Complete ===" -ForegroundColor Cyan
Disconnect-MgGraph

The script connects to your M365 tenant using the Microsoft Graph API, checks for a custom domain, verifies that MFA policies exist, counts your licensed users, and lists your SharePoint sites. It is read-only and makes no changes to your configuration. If any check shows [FAIL], go back to the corresponding setup step and fix it.

The Total Cost Picture

Let me put together the complete cost picture for a “good enough” cloud setup for a 20-person business in DeLand or anywhere in Central Florida:

Component	Monthly Cost	Annual Cost
M365 Business Standard (20 users)	$250	$3,000
Cloud backup (Veeam/Acronis)	$60	$720
Azure B2s VM (LOB app, if needed)	$30	$360
Domain name renewal	~$1	$12
Total (without VM)	$311	$3,732
Total (with VM)	$341	$4,092

Now compare that to what you are probably spending on on-premise infrastructure:

On-Premise Component	Cost
Server hardware (amortized over 5 years)	$100-250/month
Windows Server licenses	$30-80/month
Backup solution (hardware + software)	$50-100/month
Electricity for server room	$40-125/month
IT support for server maintenance	$200-500/month
Total On-Premise	$420-1,055/month

The cloud setup is cheaper in almost every scenario, and that is before you factor in the cost of a server failure, a hurricane damaging your server room (this is Florida, after all), or the productivity loss from running 5-year-old hardware.

What Migration Looks Like

Moving from on-premise to this cloud stack typically takes one to two weeks for a 20-person business. Here is the realistic timeline:

Week 1:

Day 1-2: Set up M365 tenant, add domain, create user accounts
Day 3: Configure SharePoint sites and Teams channels
Day 4-5: Migrate email (Microsoft’s migration tool handles this, or your IT provider can run it over a weekend)

Week 2:

Day 1-2: Upload files from file server to SharePoint (BitTitan, ShareGate, or manual upload for smaller file sets)
Day 3: Train employees on SharePoint and Teams (2 hours is usually enough)
Day 4-5: Parallel running period where both old and new systems are available
End of Week 2: Decommission the old server (or keep it as a local backup for 30 days)

The biggest challenge is not the technology. It is change management. Your employees have been using the file server and Outlook (or worse, Gmail) for years. Switching to SharePoint and Teams requires them to change habits, and that takes patience and training. Schedule two hours for a hands-on training session, create a one-page cheat sheet with the top 10 things they need to know, and designate a “Teams champion” on your staff who can answer questions during the first few weeks.

Common Objections (And Honest Answers)

“What if the internet goes down?” This is the number one objection I hear from businesses in Deltona and DeLand. And it is valid. If your internet connection fails, you lose access to your cloud services. But here is the counterargument: how often does your internet actually go down for more than a few minutes? For most businesses, the answer is rarely. And when it does, Office desktop apps still work offline. OneDrive syncs files locally so you can keep working. When the connection comes back, everything syncs automatically. Your on-premise server, by the way, is also useless if a power outage hits your office, unless you have a UPS and generator.

“I do not trust Microsoft with my data.” Microsoft spends over $1 billion per year on security. They employ more than 3,500 security professionals. Their data centers are SOC 2, ISO 27001, and HIPAA certified. Unless you are spending that kind of money on your server closet (spoiler: you are not), your data is safer with Microsoft than on your own hardware.

“It is too expensive.” We just did the math. It is cheaper than on-premise in almost every scenario, especially when you factor in hardware replacement cycles, IT support costs, and the implicit cost of running aging infrastructure.

“What about compliance?” Microsoft 365 Business Standard meets the compliance requirements for most small business regulations, including HIPAA (with a BAA), PCI DSS (with proper configuration), and Florida’s Information Protection Act. If you are in healthcare or financial services and need more stringent controls, Business Premium adds Microsoft Purview compliance tools and Defender for Business.

“Can we keep our existing phone system?” Yes. Microsoft Teams can integrate with your existing phone system through Direct Routing, or you can add Teams Phone licenses ($8 per user per month) and port your existing phone numbers. For a small business, Teams Phone often replaces a $200-400 per month phone system with a $160 per month Teams add-on.

The One-Page Setup Checklist

Print this out. Check off each item as you complete it:

[ ] Purchase M365 Business Standard subscription
[ ] Add and verify custom domain
[ ] Enable Security Defaults (MFA for all)
[ ] Create user accounts with proper licenses
[ ] Create separate admin account
[ ] Set up SharePoint sites by department
[ ] Create Teams channels mirroring SharePoint structure
[ ] Configure shared mailboxes (info@, support@, sales@)
[ ] Set up standardized email signature via transport rule
[ ] Restrict external SharePoint sharing
[ ] Enable self-service password reset
[ ] Set up cloud backup (Veeam, Acronis, or equivalent)
[ ] Migrate email from old system
[ ] Upload files from file server to SharePoint
[ ] Train employees (2-hour hands-on session)
[ ] Run verification script
[ ] Decommission old server (after 30-day parallel period)

That is it. Seventeen items. You can complete most of them in a single day, with migration and training taking the remainder of the week.

Frequently Asked Questions

What Microsoft 365 plan should a business with 10-15 employees choose?

For most businesses with 10-15 employees, Microsoft 365 Business Standard at $12.50 per user per month is the best value. It includes desktop Office apps, email, file storage, and Teams. Business Basic saves $6.50 per user per month but lacks desktop apps, which frustrates employees who need full Excel or Word functionality. Business Premium adds advanced security features that become important as you grow past 20 employees or enter regulated industries like healthcare.

Can I migrate from Google Workspace to Microsoft 365?

Yes, and Microsoft provides a free migration tool built into the Admin Center that handles email, contacts, and calendar migration from Google Workspace. File migration from Google Drive to SharePoint can be done through the SharePoint Migration Tool (free from Microsoft) or third-party tools like BitTitan MigrationWiz. Plan for a one-week migration window for a 20-person team.

What happens to our data if we stop paying for Microsoft 365?

Microsoft retains your data for 90 days after subscription expiration. During the first 30 days, you can reactivate your subscription and everything comes back. From days 31-90, only admins can access the data (users are locked out). After 90 days, Microsoft permanently deletes everything. This is why cloud backup (separate from M365) is important, even for cloud-first businesses.

Is Microsoft 365 HIPAA compliant for healthcare practices?

Microsoft 365 can be HIPAA compliant, but you need to sign a Business Associate Agreement (BAA) with Microsoft, which is available at no additional cost. You also need to configure the environment properly: enable encryption, restrict external sharing, set up audit logging, and ensure MFA is active. Business Premium adds Defender for Business and Intune, which strengthen compliance posture. Many medical practices in Daytona Beach and Port Orange use M365 with a BAA successfully.

Should I hire someone to set this up or do it myself?

If you are comfortable following step-by-step instructions and have 4-8 hours available, you can set up the basic M365 environment yourself. The migration phase (moving email and files) is where most businesses benefit from professional help. An IT consultant in the DeLand or Volusia County area typically charges $1,000-3,000 for a complete migration, which includes setup, migration, training, and 30 days of post-migration support. For a setup that your business will use for years, that is a reasonable investment.

The Bottom Line

You do not need the fanciest cloud architecture to run a successful small business. You need email that works, files that are shared and backed up, a way for your team to communicate, and enough security to keep the bad actors out. Microsoft 365 Business Standard delivers all of that for $12.50 per user per month.

Stop overthinking it. Stop waiting for the “perfect” setup. The good enough setup, the one you actually implement and use, beats the perfect setup that lives forever on your to-do list. Every day you run on that aging file server in the back closet is a day you are carrying unnecessary risk, unnecessary cost, and unnecessary complexity.

If you need help getting started with cloud setup for your business in DeLand, Ormond Beach, Daytona Beach, or anywhere in Volusia County, we can help with the migration. And if you want to understand the differences between Azure and AWS before committing, read our honest comparison of the two platforms.

The ‘Good Enough’ Cloud Setup for Businesses Under 20 Employees