Above / migration dispatch

A cloud migration and DevOps proposal for a software company leaving a rented server rack for AWS. It covers the hours spent on releases and fixes, the three workloads that move, what gets set up, a twelve-week timeline, the team, a similar client’s results and three one-time options.

Cloud Migration and DevOps Proposal

<h1 style="font-family:Lora;font-weight:500;line-height:1;text-align:left;color:#202E3B"><span style="font-size:clamp(42px,9cqw,82px)">Cloud migration<br>& DevOps</span></h1>
<p style="font-family:Inter;color:#202E3B;text-align:left;font-size:18px;line-height:1.5">Proposal for {{CLIENT_COMPANY}}<br>by {{SELLER_COMPANY}}</p>

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Thank you for the server tour</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">You want to leave the rack before the contract ends in June, and release during the day without a late night.</p>

<p>Hello {{CLIENT_NAME}},</p>
<p>Your customer portal, public API and reporting database run on three servers in a rented rack, and the rack contract ends in June. Releases happen once a month, at night, and take about two hours by hand. Backups run every night, but nobody has tried a full restore.</p>
<p>We recommend moving all three to AWS by April, with automated releases, monitoring and a tested restore. Your developers will be able to release in the middle of the day, in minutes.</p>
<p><strong>{{SELLER_NAME}}</strong><br>Cloud lead, {{SELLER_COMPANY}}</p>

Hours your team spent on releases and server fixes each month

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Three workloads move to AWS</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">From your rack to managed services, one at a time.</p>

<p>A Node.js app with about 2,300 customer logins a week. Moves to containers, with two copies always running.</p>

Customer portal

<p>Used by 40 partner systems. Moves behind a load balancer, so releases no longer cause downtime.</p>

Public API

<p>PostgreSQL, 380 GB. Moves to a managed database you can restore to any minute in the last week.</p>

Reporting database

What moves

<h2 style="font-family:var(--proposal-font-accent);font-weight:500;line-height:1.14"><span style="font-size:clamp(30px,4.2cqw,52px)">We recommend moving one workload at a time, starting with the database, and rehearsing every cutover.</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Each move has a rollback plan, and you choose the cutover window.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">What we set up</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Five parts, all written as code so they can be rebuilt.</p>

<p>Separate AWS accounts for production and testing, sign-in through your Google Workspace, and the network and servers defined in Terraform.</p>

Foundations

<p>A GitHub Actions pipeline for each app.</p><ul><li>Every merge is tested automatically</li><li>Releases take minutes, with no downtime</li><li>Production needs an approval from your lead developer</li></ul>

Releases

<p>Dashboards and alerts for errors, slow pages and spend, sent to your on-call channel.</p>

Monitoring

<p>Automatic backups, and a full restore rehearsed before each cutover and again at handover.</p>

Backups and restore

<p>About $3,900 a month at today’s usage, against $5,200 for the rack, with budget alerts so nothing surprises you.</p>

Costs

Our recommendation

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Twelve weeks from kickoff</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Work starts on {{START_DATE}}. Each cutover happens in a window you choose.</p>

<p>Dependency map, AWS accounts, network and the release pipeline.</p>

Plan and foundations

<p>Copy, test and cut over, with a rehearsed restore.</p>

<p>Containers, load balancer and two rehearsals before each cutover.</p>

API and portal

<p>Training, runbooks and a second restore test. The rack servers are switched off.</p>

Handover

<p><strong>Not included:</strong> rewriting application code beyond the small changes needed to run in containers, AWS charges, and on-call cover after handover unless you choose the third option.</p>

Timeline

<p><strong style="font-size:1.15em">{{SELLER_NAME}}</strong><br>Cloud lead, {{SELLER_COMPANY}}</p>
<p>AWS certified, with 25 moves from data centres and racks since 2019, mostly for software companies with fewer than 100 staff. You will work with:</p>
<ul><li>A platform engineer for AWS and Terraform</li><li>A DevOps engineer for the release pipelines</li><li>{{SELLER_NAME}} for the plan, the cutovers and handover</li></ul>

Who you will work with

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Results for a similar client</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A healthcare software company, three months after cutover.</p>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Options and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Three options. We recommend Full migration.</p>

A plan your team can follow, and AWS ready to use.

Full migration

Plus three months of on-call cover while your team settles in.

Migration and operations

<p>Fees are in USD and exclude tax. AWS charges are billed to you directly. This proposal is valid until {{VALID_UNTIL}}.</p>

Options and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Common questions</span></h2>

<p>Each cutover takes under an hour in a window you choose, with a notice to customers. Partners using the API keep the same addresses.</p>

Will customers notice the move?

<p>About $3,900 a month at today’s usage, against $5,200 for the rack. Budget alerts warn you before any surprise.</p>

What will AWS cost us?

<p>Not much. They release through the same GitHub flow. Two training sessions cover logs, alerts and the pipeline.</p>

Do our developers need to learn AWS?

<p>Every cutover has a rehearsed rollback. The old servers stay on until each workload has run on AWS for two weeks.</p>

What if a cutover goes wrong?

<p>Yes, at the same price. We suggest AWS because your team already uses it for file storage.</p>

Can we use Azure or Google Cloud instead?

<p>Access to the servers and code, a developer to answer questions, and someone who can agree cutover dates.</p>

What do you need from us?

Questions

<p style="font-size:18px;letter-spacing:.08em;text-transform:uppercase">{{SELLER_COMPANY}}</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.2cqw,44px)">Next steps</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">How we start.</p>

Cloud Migration and DevOps Proposal - Preview