Data migration plan

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

• Migration name

  For example: Customer records move to the new CRM

• Migration owner

  For example: Hamza Idrissi

• Source system

  For example: Old CRM (on-premise database)

• Target system

  For example: New cloud CRM

• Planned cutover date

  For example: 18 October 2030

• What moves and what does not

  For example: Moves: 48,000 customers, 120,000 orders from the last 7 years, notes and files. Does not move: closed accounts older than 7 years, test records.

• Field mapping

  One row for each field.

  For example: cust_name | Account name | Join first and last name cust_tel | Phone | Convert to international format status | Stage | Active to Customer, Lead to Prospect

• Cleaning and duplicates

  For example: Merge records with the same email. Remove records with no name and no order. Fix phone numbers. The business owner approves the list of merged records.

• Approach and tools

  For example: Export to files, transform with a script, load with the target's import tool. Two full trial runs, then the final run.

• Trial runs

  For example: Trial 1 on 22 September: find mapping errors. Trial 2 on 6 October: time the run and check counts.

• Cutover steps

  For example: 1. Friday 18:00 freeze the old system 2. Final export and load 3. Run checks 4. Switch users and integrations 5. Open on Monday 08:00

• Checks after the load

  For example: Record counts match the source Totals of order value match to the cent 50 random records compared by hand Key users confirm their own accounts

• Rollback plan

  For example: If checks fail by Sunday 20:00, reopen the old system, which stays untouched for 30 days.

• Security and privacy (optional)optional

  For example: Export files are encrypted and kept on one approved server, deleted 7 days after sign-off.

• Who signs off

  For example: Maria Costa, business owner of the customer data

1. 11. Scope
2. 22. Field mapping
3. 33. Cleaning
4. 44. Approach
5. 55. Trial runs
6. 66. Cutover
7. 77. Checks after the load
8. 88. Rollback
9. 99. Security and privacy
10. 1010. Sign-off

1. 01

   Fill in

   Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

2. 02

   Check

   Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

3. 03

   Download

   Save it as a Word document to edit further, or as a PDF to send or print.

What details does this template ask for?

The form asks for 15 details, starting with Migration name, Migration owner, Source system, Target system, Planned cutover date. 1 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

What should I check before I use this template?

If the data holds personal information, rules on where it may be stored and moved can apply. Check them for the countries involved before you copy it anywhere.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

• API integration specificationSpecify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it.IT and projects
• Architecture decision recordRecord a technical decision with its context, options, reasons and consequences, for the team to find later.IT and projects
• Bring your own device policySet the rules for using personal phones and laptops for work: security, privacy, support and leaving.IT and projects
• Bug reportReport a software problem so a developer can repeat it, judge its impact and fix it.IT and projects
• Change management planPlan how people will be told, trained and supported through a big change, and how you will know it worked.IT and projects
• Change requestAsk for a change to a project or system, show its impact and record whether it is approved.IT and projects

See all IT and projects templates