Cloud Migration Service
The shortcut: Most consultants quote a fixed-price "lift to AWS" before they've seen the server inventory and end up eating the surprise. Sell a paid 2-week discovery first, then quote the migration. The discovery itself is your first $4K-$8K invoice and the only way you stop losing money on under-scoped projects.
Industry: Software & Tech | Investment level: Medium — $5,000-$25,000 | Time to launch: 8-12 weeks (one cloud certification + a paid discovery template + first signed pilot gate the launch)
Best for: A sysadmin, devops engineer, or solutions architect who has actually moved production workloads — not just read about it. You can read a network diagram, talk to a CFO about TCO, and tell a client "no, we are not refactoring that PHP monolith this year." What you'll likely make: $4,000-$8,000 month 3, $10,000-$18,000 month 6, $18,000-$30,000 month 12. Math is in Section 4.
Market Opportunity
Your client has servers in a colo and a $14K/month bill. They have a half-finished AWS account someone's intern set up two years ago. They have a CFO who read an article about cloud savings. What they don't have is a written plan that says which workloads move, which stay, and what it costs in year one versus year three.
That gap is the entire business. The 10-100 person company is too small for Accenture and too complex for a generalist MSP. They want one technical person who will own the answer.
Most cloud migrations don't fail on the technical lift. They fail because nobody mapped which apps needed to move — and the client ends up paying for cloud AND keeping the old servers running for 18 months. You sell the map first.
Why this is a good time to start: Two-year cloud contracts signed in 2022-2023 by SMBs are coming up for renewal in 2026, and the bills are bigger than anyone budgeted. The companies hiring you now are the ones whose CFO finally asked "why is AWS our third-largest line item?"
Launch With AI
Pro section. AI doesn't replace the migration — it cuts the parts that drained you (writing the discovery deliverables, drafting MSAs with attorney review, generating the TCO model + 6R decision matrix, building monthly FinOps reports). Spend the saved time on what AI can't do: standing up the AWS Organizations structure properly, validating the database cutover with the client at midnight, and walking the CFO through the year-1 vs year-3 TCO line by line.
The trap most first-year cloud migration consultants fall into: they think AI will research patches, CVE IDs, or AWS service limits for them. It will hallucinate KB numbers and AWS quota values that don't exist. AI for the writing tail (discovery deliverables, vCIO reports, FinOps memos, sales follow-ups) is where it pays you back — every technical claim gets your eyes on it AND verification against AWS docs before it goes to a client.
Important up-front: AI cannot run the cutover, refuse the fixed-price-without-discovery client, or restore from a Datto BCDR snapshot at 2am. It will also confidently generate "zero downtime" promises you can't deliver solo. You own every commitment, every architecture decision, every breach response; AI scales the writing around them.
AI Tools You'll Use
| Tool |
Price |
What it does |
| ChatGPT Plus |
$20/mo |
Discovery deliverables, migration plan templates, sales follow-ups, FinOps reports |
| Claude Pro |
$20/mo |
Long-context server inventory analysis, dependency mapping, multi-cloud doc review |
| Cursor |
$20/mo |
Terraform/IaC, PowerShell, AWS CDK, scoped automation, runbook code |
| AWS Migration Hub built-in tools |
free |
Discovery scans, MGN agent rollout, dependency mapping, status dashboard |
| Loom AI |
free |
Discovery walkthroughs, monthly retainer reports, audit deliverables |
The Workflow
Discovery deliverable + 6R decision matrix (Claude long-context, ~3 hours/prospect). New client discovery is where most migration consultants spend a week. Paste the asset inventory + AWS Migration Hub scan + dependency map into Claude:
"Below is a discovery for [client, N servers, vertical]. Includes: server inventory CSV, AWS Migration Hub dependency map export, current monthly hosting cost ($X), key apps + their data residency requirements (US-only / EU-included). Generate: (a) the 6R decision per workload (Rehost / Replatform / Refactor / Repurchase / Retire / Retain) with the 1-line rationale each, (b) the TCO model — year 1 / year 2 / year 3 cost breakdown comparing current colo vs AWS rehost vs AWS replatform with managed services, (c) the migration risk-ranked plan (week-by-week 12-week plan with cutover order — easiest workloads first, the database/legacy-app cluster last), (d) the 1-paragraph CFO summary with the headline number ($X savings year 1, $Y year 3). NEVER hallucinate AWS service limits or quota values — flag any number for my verification against AWS docs. Tone: senior migration advisor."
Verify every quota and KB cite against AWS docs. Claude long-context turns a 6-hour discovery into a 90-min discovery — that's billable hours back to the technical work.
Reusable Terraform/IaC starter (Cursor + Claude, ~6 hours one-time). Standardized AWS Organizations setup is the asset you reuse across every client. Open Cursor with Claude 3.5 Sonnet:
"I'm building a reusable AWS Organizations Terraform starter for SMB migrations. Generate: (a) the AWS Organizations module (master account + Security/Logging/Production/Sandbox sub-accounts + SCPs preventing region-deviation outside US-east-1 + EU regions for GDPR clients), (b) the baseline VPC + Transit Gateway module (10.0.0.0/16 with /20 subnets per AZ × 3 AZs, NAT gateway, IPv6 dual-stack), (c) the IAM Identity Center setup (SSO with Okta/Google Workspace SAML), (d) CloudTrail + AWS Config + GuardDuty turned on org-wide, (e) the S3 bucket policy template that enforces encryption + blocks public ACLs by default. Output as Terraform modules with var files for client-specific overrides. Code only."
Build once. Client 2 onward, deploying the baseline takes 4 hours instead of 30. That's the unit-economics math for the $35K migration price.
Migration plan + cutover runbook (ChatGPT + Loom AI, ~4 hours/migration). Paste the discovery into ChatGPT:
"Below is the discovery for [client]. Build the migration plan + cutover runbook: (a) the 12-week timeline (week 1-2: AWS Organizations + baseline; week 3-4: rehost wave 1 of 5 servers via MGN; week 5-6: rehost wave 2; week 7-8: replatform RDS + S3; week 9-10: cutover prep + DR test; week 11: production cutover; week 12: optimization), (b) the cutover-day runbook (T-7 days through T+24 hours — every step named, the rollback trigger at each step, the named owner per step), (c) the client-facing weekly status email template (5 sentences max — what shipped, what's next, any risks, this week's billable hours, FinOps savings tracker). Output as Notion-ready cohort guide."
Walk the client through the runbook in a Loom recording — Loom AI auto-titles + transcribes. Recorded runbooks drop client anxiety AND give you legal cover — the timeline is documented before cutover starts.
FinOps + monthly retainer report (ChatGPT + RMM data, ~30 min/client/month). The FinOps retainer ($1,500-$2,500/month) is what stacks this into a real income. Paste each month's AWS Cost Explorer + Trusted Advisor + CloudWatch data into ChatGPT:
"I run the FinOps retainer for [client]. Below is this month's AWS Cost Explorer + Trusted Advisor + CloudWatch data. Generate the 1-page monthly retainer report: (a) headline number ($X spent vs $Y projected — are we hitting the 30% savings target from the original TCO model?), (b) idle resource cleanup (the 5 EC2 instances at <5% CPU for 30 days, the 12 unattached EBS volumes, the 8 unused NAT gateways — total $X/month savings if we kill them), (c) reserved-instance + Savings Plans recommendations (the 3 workload patterns where committing 1-year reserved would save $Y/month), (d) the cyber insurance attestation status (MFA %, GuardDuty findings, IAM rotation), (e) one strategic recommendation for next month. Tone: senior FinOps advisor. NEVER auto-implement deletions — flag every cleanup for client approval. Output as Notion-ready 1-pager."
Send first business day of every month. The FinOps retainer renews itself — clients who get a real strategic memo don't shop their consultant.
Sales follow-up + LinkedIn outreach (ChatGPT, ~30 min/week). Cold LinkedIn to IT directors at 10-100 person companies converts at 0.5-1.5% to paid discovery. Paste:
"I'm a cloud migration consultant. Build the LinkedIn cold-DM template I'll send to 5 IT directors/day at 11-100 employee companies in [my metro]: (a) 2-sentence body — name 1 specific pain (cloud bill renewal coming up, Windows Server 2008 EOL, audit-driven cyber insurance posture), offer the 1-page TCO calculator as a free download (NEVER 'I'd love to discuss your IT strategy'), (b) the post-download autoresponder — 'here's the calculator + a 15-min audit-call link if useful, no obligation,' (c) the 7-day follow-up to non-replies — 1 line, NEVER pushy. Tone: senior consultant, NEVER eager. Output as paste-ready LinkedIn DM."
Send 5/day for 4 weeks = 100 messages. 2 paid discoveries × $5K = $10K from one month of disciplined outreach.
Time Saved Per Week
Roughly 8-12 hours/week once your discovery template, IaC starter, and FinOps report are built:
- Discovery deliverables: 8 hours/prospect → 3 hours (Claude long-context)
- Reusable IaC: 30 hours/client → 4 hours (Terraform starter + Cursor)
- Migration plan + runbook: 8 hours/migration → 4 hours (ChatGPT)
- FinOps retainer report: 90 min/client → 30 min (ChatGPT + AWS data)
- LinkedIn outreach: 4 hours/week → 30 min (template)
Trade that time for: the AWS re:Invent talk you should attend, the cyber insurance broker coffee meeting, and the third FinOps retainer client.
Total AI Stack Cost
- Budget tier ($20/mo): ChatGPT Plus only. AWS Migration Hub is free; Cursor free tier handles small Terraform; Loom AI is free. Right for first 60 days while you build the IaC starter.
- Full tier ($60/mo): ChatGPT Plus + Claude Pro + Cursor. Worth it once you sign anchor client 2 — Claude long-context on dependency analysis alone saves 4+ hours per discovery.
- Compare: A junior cloud engineer doing IaC + discovery + retainer reports runs $7,000-$12,000/mo. The full AI stack is one-hundredth that cost — and you keep eyes on every PowerShell and Terraform script before it runs in production.
Cancel anything you don't open in a 7-day window. NEVER use AI for compliance research without verification against the actual AWS docs — hallucinated quota values are the kind of mistake that ends an engagement.
Your First Win
30 minutes from now your TCO calculator is built. Open ChatGPT (free tier works). Paste:
"I'm a cloud migration consultant. Build me a 1-page TCO calculator I'll use as a lead magnet on LinkedIn outreach. Inputs: (a) current monthly hosting cost ($X), (b) server count (N), (c) approximate RAM/storage per server, (d) any compliance requirement (HIPAA / GDPR / SOC2). Outputs: (a) AWS rehost estimated monthly cost (using on-demand pricing for the closest EC2 instance + RDS + EBS + S3), (b) AWS replatform with reserved instances + Savings Plans estimated monthly (showing 30% savings target from Flexera benchmark), (c) the year-1 / year-3 cost comparison vs current colo, (d) the 6R framework summary explaining the difference. Tone: senior consultant, defensible numbers ONLY (link to AWS pricing source for every number). Output as a Google Sheets-ready calculator with formula structure I can rebuild."
Drop into Google Sheets. Gate behind email — converts at 10-15% of downloads to a discovery call. That single calculator is worth your first 5 paid discoveries.
Product / Service Offering
You sell three things in this order. Each one is a separate signed agreement so a stalled project doesn't kill the engagement.
- Paid discovery + assessment — 2-3 weeks. Server inventory, dependency mapping, Gartner 6R framework decision per workload (Rehost / Replatform / Refactor / Repurchase / Retire / Retain), a TCO model the CFO can read, written migration plan. $4,000-$8,000.
- Migration execution — 6-16 weeks. Lift-and-shift rehost workloads using AWS MGN, Azure Migrate, or Google Migrate to Virtual Machines. Replatform the few that need it (managed RDS, managed Kubernetes). Cut over with a documented rollback. $15,000-$60,000 depending on server count.
- FinOps + optimization retainer — month 4 onward. Monthly bill review, rightsizing, reserved-instance and savings-plan recommendations, idle-resource cleanup. $1,500-$4,000/month.
Push lift-and-shift first and refactor later. Clients who try to refactor during the migration miss every deadline. Get them to cloud parity in 90 days, prove the bill matches what you projected, then sell the refactor as a separate engagement. Pick a primary cloud and stick with it — AWS is the deepest SMB market, but if your background is Microsoft-shop, Azure pays the same and your competition is thinner.
Revenue Model
Solo consultant, one engagement at a time, billing through Stripe with 50% deposits.
| Service |
Price |
Variable cost (tools + Stripe) |
Engagement length |
Take-home |
| Paid discovery + assessment |
$6,000 |
$40 (Cloudamize trial / sheet templates) + $174.30 (Stripe 2.9% + $0.30) |
2-3 weeks |
~$5,785 |
| Migration execution (15-server SMB) |
$35,000 |
$400 (MGN beyond 90 days, test infra) + $1,015.30 |
8-12 weeks |
~$33,585 |
| FinOps + optimization retainer |
$2,500/mo |
$50 (monitoring tools share) + $72.80 |
4-8 hrs/mo |
~$2,375/mo |
| Replatform add-on (managed DB, Kubernetes) |
$12,000 |
$150 + $348.30 |
3-5 weeks |
~$11,500 |
Your first $1K month = signed paid discovery at $6,000 with 50% deposit upfront = $3,000 in the door. Two weeks of focused work to deliver.
Your first $3K month = one discovery wrapping ($3,000 final invoice) plus a signed FinOps retainer at $2,500/month = $5,500 in. Two months from a cold start, three if your first discovery slips.
The retainer math is what makes this a real business. Three FinOps retainers at $2,500/month is $7,500/month base before any new migration lands — and FinOps clients turn into repeat migration buyers when they acquire the next subsidiary.
Startup Costs
- AWS Solutions Architect Associate exam: $150 (AWS certification). Add the Professional at $300 by month six if you're going upmarket.
- Azure Solutions Architect Expert: two exams at ~$165 each (Microsoft Learn). Skip if AWS-focused.
- GCP Professional Cloud Architect: $200 (Google Cloud certification). Skip unless you have a specific GCP-shop client lined up.
- Lab + cert prep: $300-$800 for AWS/Azure free-tier overage plus A Cloud Guru or Tutorials Dojo practice exams.
- Hardware: A laptop that can run Terraform, Docker, and three CloudWatch tabs without crying. $1,500-$3,000 if you don't already own one.
- LLC + EIN: $35-$500 LLC filing — LLC University 50-state table. EIN is free at IRS EIN Online — never pay a third party.
- E&O insurance: $1,200-$2,500/year (Hiscox or Insureon). Slightly higher than a frontend dev because client losses on a botched cutover are bigger.
- MSA + SOW attorney review: $400-$800 for a real review of templates from Bonsai — the data-handling and indemnification clauses are non-trivial in this work.
- Bookkeeping + accounting: QuickBooks Self-Employed at ~$20/month or Bench at $249-$499/month if you'd rather hand it off.
Realistic all-in: $5,000 if you own a dev laptop and skip Bench; $25,000 if you stack two cert tracks, bind insurance year one, sit a full attorney review, and book in-person AWS re:Invent training.
Legal & Formation
Business entity. Single-member LLC the moment you sign the first paid discovery. A botched cutover that loses three days of database transactions is the kind of claim where you want the lawsuit naming your LLC, not your house. Filing fee runs $35-$500 — see the LLC University 50-state table. EIN is free at IRS EIN Online — never pay a third party. Once net profit clears $80K-$100K/year (plausible by month 12), run the math on an S-corp election via IRS Form 2553.
Licenses & sales tax. No professional license is required for cloud migration consulting. Custom professional services are generally not taxable in most states — but the moment you resell cloud capacity (reselling AWS as part of a managed-services bundle) you can trip into taxable territory. Cross $100K in sales or 200 transactions in any state and you have economic nexus there. Check current rules via the Avalara state-by-state SaaS taxability tracker.
Industry-specific risk. Three traps and they trip people up in this exact order. First, the fixed-price-without-discovery trap. Never quote a fixed migration price before a paid discovery. Client server inventories are wrong about 80% of the time — the forgotten finance app, the 11-year-old Windows 2008 box no one wants to touch, the database that "doesn't talk to anything" but actually feeds three reports. Quote the discovery first. Quote the migration only after you've seen the inventory yourself. Second, the zero-downtime promise. Do not promise zero downtime as a default. It is achievable for some workloads with read replicas and DNS cutover, but it requires architecture decisions that get scoped and priced as a separate line item. Promising it casually ends with you working three weekends for free. Third, GDPR data residency. If any client workload touches EU resident personal data, GDPR Article 44 restricts where that data can live. AWS eu-west-1, Azure North Europe, and GCP europe-west1 are compliant regions. Scope this before the migration plan locks — discovering at cutover that you migrated EU data to us-east-1 is a five-figure remediation problem. Cap your total liability at fees paid in the trailing 12 months in your MSA, and never accept uncapped liability.
Marketing & First Customers
Your first three clients come from people who already know you can run production infrastructure — old colleagues, the ex-CTO of your last job, the friend-of-a-friend whose colo lease is up. Send those eight emails before you build a website.
The channels that work after that:
- Direct LinkedIn outreach to 20-30 IT directors / VP Engineering at 10-100 person companies in your geography. Filter by "company size 11-100" and "industry: software / financial services / healthcare." Two-sentence message: "I help SMBs migrate to AWS without the surprise bill — happy to send you the 1-page TCO template I use, no call required." Send 5/day for 4 weeks. Reply rate 8-12%, scoping-call rate 3-5%, paid discovery rate 0.5-1.5%. Two paid discoveries from 100 messages is realistic.
- AWS Partner Network registration. Register as an AWS Partner Network member (free). Even at the lowest tier you show up in partner directory searches for migration. Once you've shipped 2-3 migrations, apply for AWS Migration Competency — it filters inbound leads to ones who already know they need help. About 20-30% of mid-tier partner inbound converts.
- One-page free TCO calculator as a lead magnet. Spreadsheet that takes server count, current monthly hosting cost, and rough memory/storage and outputs an estimated AWS reserved-instance price. Gate behind email. Converts at 10-15% of downloads to a discovery call. Promote on LinkedIn and on r/devops when topical.
- Local user groups and one talk per quarter. AWS user group, Azure user group, the local devops meetup. Talk title: "How a 40-server SMB cuts their cloud bill 30% in 60 days." 1-2 inbound clients per talk if you don't pitch from stage.
Disclose your AI tool stack upfront in every sales call. Regulated-industry clients (finance, healthcare) will ask whether you ran their network diagrams or config files through Copilot or Claude. Saying it first builds trust. GitHub Copilot for Business includes commercial IP indemnification and is the safer default.
First 90 Days
- Week 1. File LLC. Get free EIN. Register for the AWS Solutions Architect Associate exam ($150) with a date 5 weeks out — the deadline forces the studying.
- Week 1-2. Bind E&O insurance. Buy Bonsai MSA + SOW templates, send to an attorney for a $400-$800 review. Set up Stripe.
- Week 2-4. Build your reusable discovery deliverables: a server-inventory intake spreadsheet, a 6R decision matrix, a TCO template, and a 1-page migration-plan template. These are the artifacts you'll sell on every discovery — build them once.
- Week 5. Pass the AWS Solutions Architect Associate exam.
- Week 5-8. Send 8 personal emails to old colleagues describing what you're now doing. Send 100 cold LinkedIn messages to IT directors at 10-100 person companies in your area. Target: 1 paid discovery signed at $4,000-$6,000.
- Week 8-10. Run the discovery. Deliver a 15-page migration plan, a TCO model spreadsheet, and a 6R-coded server inventory. Use AWS Migration Hub as the live status dashboard the client can log into.
- Week 10-12. Quote the migration off the discovery. Aim for $20,000-$40,000 at this stage (your first execution). Convert the discovery client to a $1,500-$2,500/month FinOps retainer post-cutover.
- Week 12. Target metric: 1 paid discovery delivered, 1 migration signed, 1 FinOps retainer in place. Total 90-day revenue $8,000-$15,000 in the door, with $20,000-$40,000 of contracted backlog.
Common Pitfalls
- Quoting a fixed migration price before discovery. This is the career-killer for SMB migration consultants. Without a paid discovery you're guessing at server count, dependencies, and the one app that's actually a Lambda-incompatible mainframe emulator. Eat one bad project (lose $15,000 on a $25,000 quote, work weekends, lose the referral) and you're done. Fix: every quote starts with a paid discovery — minimum $4,000. No exceptions, even for warm referrals.
- Promising "zero downtime" casually on a sales call. Engineers say it because it sounds professional. Then you spend three weekends doing read-replica cutovers for free because the client heard "zero" and budgeted accordingly. Real zero-downtime architecture costs an extra $5,000-$15,000 in setup. Fix: in the SOW, write the maintenance window in hours ("4-8 hours of weekend downtime"), and price zero-downtime as a named line item the client can say yes or no to.
- Building everything in the client's existing AWS account. Their account has the intern's old IAM policies, an unpatched VPC, and three S3 buckets that are publicly readable. You inherit all of it. Fix: stand up a fresh AWS Organizations account structure with proper SCPs from day one. The 4-6 hours it takes saves a 40-hour security cleanup you can't bill for and a breach you'd never sleep through.
- Skipping the FinOps retainer pitch. Every cloud bill creeps. Idle EC2s, oversized RDS, forgotten dev environments. The Flexera report's 30% wasted spend is real, and on a $14K/month bill that's $4,200/month you can save the client. Quote the retainer in the same proposal as the migration, not three months later. Fix: in your migration SOW, the last page is a $1,500-$2,500/month FinOps retainer that auto-starts 30 days post-cutover unless the client opts out. Half will keep it. That's $9,000-$15,000/year in recurring revenue per client you would otherwise leave on the table.
Get your full launch plan — take the free 60-second quiz.
