How to Bound Engineering Hours for a Healthcare Migration

Bound healthcare migration hours by slicing the work into compute, data, identity, regional controls, queues, recovery, and proof. A provider deployment may be quick while replacing a broad database model takes much longer. Estimate each slice, assign dependencies, and reserve time for reconciliation and failed tests.

The result is a planning envelope, not a contractor quote. Track actual hours after the first vertical slice and revise the remaining estimate. Do not present a cloud price as evidence that the migration is small.

Cost surface and assumptions

Inventory current application calls, data stores, scheduled jobs, queues, integrations, roles, exports, reports, backups, logs, regions, and support tools. A migration that changes only compute has a different scope from a migration that changes the database and tenancy model.

The Cloud Run Pricing page informs runtime cost assumptions. The AWS Lambda Pricing page informs a serverless alternative. Neither page estimates code conversion, data reconciliation, or authorization testing.

The Cloud SQL Pricing page informs the always-on database floor for a relational alternative. Use it to model production resources, not to claim that a relational migration is a fixed monthly price.

For cost buckets, read migration versus recurring operations. For tenant proof, read tenant isolation negative tests.

One-time work versus recurring work

Break the estimate into work blocks.

Block	Deliverable	Dependency
Compute	Runtime, domains, deploy, jobs	Target region and secrets
Data	Schema, indexes, migration, reconciliation	Query inventory
Identity	Membership, MFA, service roles	Tenant and support matrix
Regional	Resource policy, keys, logs, backups	Home-region decision
Queues	Retries, idempotency, dead letters	Event contract
Proof	Negative, restore, rollback, evidence	Working vertical slice

Recurring work starts after cutover. Include deployment maintenance, provider changes, access reviews, support, backup tests, audit review, incident exercises, and future schema work. Keep legal review and training outside engineering hours unless an owner explicitly combines them.

Scenario table and hour envelope

Use ranges that identify what drives the spread.

Route	Planning envelope	Why the range moves
Runtime lift	40 to 80 hours	Jobs, domains, secrets, networking, and smoke tests
Document database rewrite	180 to 320 hours	Queries, transactions, reports, backfill, and access controls
Relational database rewrite	220 to 400 hours	Schema, constraints, row policies, conversion, and cutover
Regional proof	Add measured hours	Region count, logs, backups, keys, and support geography

These are internal planning estimates from the architecture baseline, not provider or contractor quotes. Replace them with measured hours after the vertical slice. Record what is excluded: counsel, training, customer migration support, downtime, tax, and vendor approval.

Vertical slice and evidence

Choose a slice containing tenant membership, one intake path, one booking state, one outbox event, one report, one export, and one restore. Prove authorized and denied access. Reconcile counts and statuses. Test retry, idempotency, rollback, logging, and cleanup.

Do not start a broad migration before this slice passes. A successful build proves compilation and deployment. It does not prove that the target preserves query semantics, tenant scope, or recovery behavior.

Use regional backup restore testing and immutable home-region controls as separate acceptance gates. Include their results in the estimate if they fail and need remediation.

Commercial approval gate

1. Freeze the source and target boundary.
2. Measure a vertical slice before committing to full migration.
3. Assign hours to compute, data, identity, regional, queue, and proof blocks.
4. Show low, expected, and high cases.
5. Price support, legal, training, and recurring maintenance separately.
6. Approve only with rollback and old-store cleanup plans.

Stop when query coverage is unknown, a target service cannot enforce the required boundary, or the migration estimate contains no reconciliation and restore work.

Keep one named owner for reconciling counts, failed jobs, rollback evidence, and cleanup before declaring cutover complete.

Frequently asked questions

Which block is usually underestimated?

Data and proof work are common sources of underestimation. Query inventory, report behavior, authorization failures, backups, restore validation, and cutover reconciliation take time beyond runtime deployment.

Can provider free tiers reduce migration hours?

No. Free tiers may reduce provider charges in a test or low-volume scenario. They do not reduce schema conversion, identity design, testing, or evidence work.

When should hours be re-estimated?

Re-estimate after the first vertical slice, any failed authorization or restore test, a changed database choice, a new region, a new vendor, or a new contract requirement.

References

• Google Cloud, Cloud Run Pricing, retrieved 2026-08-15: https://cloud.google.com/run/pricing
• Amazon Web Services, AWS Lambda Pricing, retrieved 2026-08-15: https://aws.amazon.com/lambda/pricing/
• Google Cloud, Cloud SQL Pricing, retrieved 2026-08-15: https://cloud.google.com/sql/pricing