
API Documentation
Docs + Word14 pages
Free
Data migrations go wrong when scope is vague, cleansing is left until after the load, and nobody has agreed in advance what a good result looks like. This template puts scope, mapping, cleansing, trial loads, reconciliation and cutover on eight pages, so the sponsor, data owners and engineers sign the same plan.
The sample moves 24 million records across 38 tables from a legacy ERP to a cloud platform for Greystone Digital, with trial loads at 10%, 50% and full volume, a 10-hour cutover window and a rollback decision at hour 8. Replace the systems, volumes, thresholds and dates with yours.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace the source and target systems with yours, and list the objects and record volumes in scope.
Fill in the mapping and trial load commands with your real fields, then set the reconciliation thresholds your data owners will sign.
Rewrite the cutover timeline with your freeze and cutover hours, and name the person who runs each task and makes the go or no-go call.
Delete the Make it yours page, then share the plan with your sponsor and data owners or present it at your readiness review.
Yes. Make a copy in Google Docs and edit it in your own Drive. You do not need to install anything or create an account beyond your Google account.
No. Greystone Digital, the people named and every figure, volume and date are fictional sample data, written to show what a controlled migration plan looks like.
The sample accepts a gap of 0.01% in row counts and requires balances to agree to the penny. Agree your own thresholds with data owners before the first trial load.
More Google Docs templatesMore developer workflows templates

Docs + Word14 pages
Free
Slides + PowerPoint12 slides
Free
Docs + Word7 pages
Free
Docs + Word8 pages
Free
Slides + PowerPoint12 slides
Free