Why English? | Writing a Data Migration Plan Through Scope, Source Mapping, Data Quality, Transformation, Validation, Cutover, Rollback and Ownership

ORIENTATION

What this guide covers

Current fact check

Checked on 8 November 2026, GOV.UK Gate 4 readiness guidance called for a clear data or information migration plan, migration scripts, appropriate archiving and retention, attention to data quality and duplication, and consideration of dependencies. The current Government Digital Functional Standard required secure migration or removal processes and user engagement, while legacy-technology guidance recommended phased planning, risk evaluation, user testing, training and communication.

What this guide does not cover

This article owns a practical data migration plan for a defined system change. It does not own a research data management plan, cloud infrastructure migration, database schema design, backup policy, privacy impact assessment, disaster recovery plan, retention schedule or final go-live approval.

Worked example

Every chapter returns to a fictional school co-curricular activity membership register moving from several spreadsheets into a new authorised portal, with synthetic records used for practice. It is fictional, low-stakes and educational; it does not report a real school, clinical decision or guaranteed outcome.

Warm up with eduKate’s guides to explaining scientific evidence and asking better questions in class.

CHAPTER 1 OF 16

1. Define the Business Purpose and Success Condition

Back to contents

Why this move matters

Explain why the move is needed, which service depends on it and what usable success looks like.

Describe the data movement as a controlled claim

Explain why the move is needed, which service depends on it and what usable success looks like. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, The club portal must show one accurate active membership per student and preserve approved historical participation. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Technology replacement is not itself a user outcome. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Define the Business Purpose and Success Condition”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 2 OF 16

2. Fix Scope, Boundaries and Authority

Back to contents

Why this move matters

List included systems, datasets, dates, populations and environments, plus who authorises each class of movement.

Describe the data movement as a controlled claim

List included systems, datasets, dates, populations and environments, plus who authorises each class of movement. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Active memberships and two years of approved history are in scope; private notes and abandoned draft sheets are not. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Possession of a file does not prove authority to migrate it. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Fix Scope, Boundaries and Authority”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 3 OF 16

3. Inventory Source Records and Owners

Back to contents

Why this move matters

Record each source, format, volume, update pattern, owner, sensitivity and known quality issue.

Describe the data movement as a controlled claim

Record each source, format, volume, update pattern, owner, sensitivity and known quality issue. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Three spreadsheets use different club names and one has no reliable update date. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

An inventory can become stale during a long project. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Inventory Source Records and Owners”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 4 OF 16

4. Describe the Target Model and Constraints

Back to contents

Why this move matters

Define target entities, required fields, code lists, relationships, permissions and limits.

Describe the data movement as a controlled claim

Define target entities, required fields, code lists, relationships, permissions and limits. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, The portal requires student key, club code, membership state, start date and approved role. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

A target field may be technically optional but operationally essential. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Describe the Target Model and Constraints”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 5 OF 16

5. Profile Data Quality Before Designing Rules

Back to contents

Why this move matters

Measure completeness, validity, uniqueness, consistency, timeliness and plausible ranges.

Describe the data movement as a controlled claim

Measure completeness, validity, uniqueness, consistency, timeliness and plausible ranges. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, The team finds duplicate students, missing start dates and free-text club names before writing conversion code. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Profiling identifies symptoms; business owners decide which meaning is correct. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Profile Data Quality Before Designing Rules”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 6 OF 16

6. Write a Field-Level Source-to-Target Map

Back to contents

Why this move matters

For every target field, name source, rule, format, default, exception and owner.

Describe the data movement as a controlled claim

For every target field, name source, rule, format, default, exception and owner. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Legacy “Robotics Club” and “Robotics CCA” map to the approved club code only after owner confirmation. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

A default can create false data if it hides absence. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Write a Field-Level Source-to-Target Map”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 7 OF 16

7. Define Transformation and Cleansing Rules

Back to contents

Why this move matters

Write deterministic rules for formats, codes, dates, duplicates, derived values and rejected records.

Describe the data movement as a controlled claim

Write deterministic rules for formats, codes, dates, duplicates, derived values and rejected records. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Dates convert to one standard, while conflicting membership states enter an exception queue. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Cleansing should not invent facts that the source cannot support. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Define Transformation and Cleansing Rules”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 8 OF 16

8. Protect Access, Transfer and Working Copies

Back to contents

Why this move matters

Specify least privilege, approved environments, encryption, logging, temporary-file handling and incident routes.

Describe the data movement as a controlled claim

Specify least privilege, approved environments, encryption, logging, temporary-file handling and incident routes. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Only authorised migration roles can access the synthetic rehearsal set and production transfer area. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Security controls depend on classification, contracts and current policy. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Protect Access, Transfer and Working Copies”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 9 OF 16

9. Design Validation and Reconciliation Rules

Back to contents

Why this move matters

Define record counts, control totals, field checks, relationship checks, samples, thresholds and sign-off.

Describe the data movement as a controlled claim

Define record counts, control totals, field checks, relationship checks, samples, thresholds and sign-off. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Counts match by club, every student key resolves and sampled memberships agree with approved source evidence. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Equal totals can still contain different records. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Design Validation and Reconciliation Rules”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 10 OF 16

10. Rehearse With Representative Safe Data

Back to contents

Why this move matters

Run extraction, transformation, loading, validation and exception handling before production cutover.

Describe the data movement as a controlled claim

Run extraction, transformation, loading, validation and exception handling before production cutover. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, A synthetic rehearsal reveals that special characters break one club name and that rollback takes longer than expected. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Test data must represent difficult patterns without exposing real people unnecessarily. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Rehearse With Representative Safe Data”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 11 OF 16

11. Manage Exceptions and Data-Quality Decisions

Back to contents

Why this move matters

Create a queue with issue type, affected records, evidence, owner, disposition and deadline.

Describe the data movement as a controlled claim

Create a queue with issue type, affected records, evidence, owner, disposition and deadline. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Ambiguous membership states wait for the CCA owner instead of being converted to active automatically. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Unresolved exceptions may require deferral rather than forced completion. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Manage Exceptions and Data-Quality Decisions”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 12 OF 16

12. Plan the Cutover Window and Communications

Back to contents

Why this move matters

Set freeze time, final extraction, sequence, verification, business checks, service messages and decision points.

Describe the data movement as a controlled claim

Set freeze time, final extraction, sequence, verification, business checks, service messages and decision points. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Updates stop Friday evening, the final load runs in order and club coordinators verify priority records before reopening. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

A cutover window does not guarantee every user sees the notice. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Plan the Cutover Window and Communications”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 13 OF 16

13. Define Rollback Conditions and Recovery Steps

Back to contents

Why this move matters

State measurable triggers, backups, restoration sequence, authority and communication if cutover fails.

Describe the data movement as a controlled claim

State measurable triggers, backups, restoration sequence, authority and communication if cutover fails. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Rollback begins if key resolution errors exceed the approved threshold or validation cannot finish before reopening. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Rollback may restore service while leaving later reconciliation work. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Define Rollback Conditions and Recovery Steps”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 14 OF 16

14. Confirm Business Acceptance and Service Readiness

Back to contents

Why this move matters

Require named owners to verify usability, permissions, reports, integrations, support and outstanding risks.

Describe the data movement as a controlled claim

Require named owners to verify usability, permissions, reports, integrations, support and outstanding risks. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Club coordinators confirm rosters, access levels and support routes; technical success alone is insufficient. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Acceptance does not erase defects documented for later repair. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Confirm Business Acceptance and Service Readiness”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 15 OF 16

15. Govern the Legacy System, Retention and Disposal

Back to contents

Why this move matters

Decide whether the old source is retained, archived, made read-only or securely destroyed under current authority.

Describe the data movement as a controlled claim

Decide whether the old source is retained, archived, made read-only or securely destroyed under current authority. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, Approved history is archived, temporary exports are deleted and the old spreadsheet route becomes read-only. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

Retention and disposal must follow applicable law, policy and contracts. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Govern the Legacy System, Retention and Disposal”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

CHAPTER 16 OF 16

16. Assign Post-Migration Ownership and Review

Back to contents

Why this move matters

Name owners for monitoring, corrections, access, metadata, incidents and lessons, with review dates.

Describe the data movement as a controlled claim

Name owners for monitoring, corrections, access, metadata, incidents and lessons, with review dates. State the source, target, fields, transformation and acceptance rule. “Move the records” is an intention; a migration plan needs an auditable mapping and a decision about what must not move.

Follow one record through the plan

In the worked migration, The portal owner tracks exceptions for one month and the records owner reviews the archive decision. Trace a single learner record from source extraction through transformation, loading, validation, reconciliation and authorised disposal or retention.

Design validation before cutover

Define totals, field checks, referential checks, duplicate rules, exception thresholds and business-owner sign-off before the first production move. A copied row is not necessarily a correct record.

Protect continuity and recovery

New quality problems can appear after ordinary users begin work. Name the freeze window, backups, rollback conditions, service communications, access controls and ownership after cutover. Migration is incomplete until users can work safely and the old system has a governed future.

Student, parent and career transfer

Make one evidence card for “Assign Post-Migration Ownership and Review”: source location, plain-language meaning, limit and next question. A parent or teacher can ask for one everyday explanation and one specialist explanation; both must preserve the same conditions. This habit supports data operations, information systems, administration, software projects, records work, business analysis, quality assurance, school technology and service transition without promising a grade, admission, funding decision or job.

PRACTICE LAB

Build a data migration plan decision trail

Student route

1. Choose one original report inside this guide’s scope.
2. Copy its objective and underline actor, action, context, evidence and intended decision.
3. Draw the specific reasoning chain used in this article.
4. Mark each step reported, inferred, contested or unknown.
5. Rewrite the conclusion so it preserves the narrowest important limitation.

Parent or teacher route

Ask the learner to explain move data between systems without losing the meaning, controls or evidence that make each record usable twice: once to a classmate and once to a method specialist. Praise a precise correction and a well-stated unknown; both show disciplined attention to evidence.

Early-career route

Create a one-page data migration plan audit with source link, date checked, scope, method logic, decisive wording, contrary evidence, limit and next action. A colleague should be able to continue without guessing.

Continue with eduKate’s guides to reading course and career information and giving useful feedback in group projects.

USEFUL NEXT READING

Connect this narrow owner to its neighbour

Read the operations-runbook guide for a related but different reader job. Return here when the question is specifically how to move data between systems without losing the meaning, controls or evidence that make each record usable. Use each guide for the reader task named in its heading.

For English practice across research, school and career communication, visit the Singapore English Tuition Centre learning site.

FREQUENTLY ASKED QUESTIONS

Questions students and parents often ask

Is data migration just copying files?

No. It includes mapping meaning, transformation, validation, security, service transition and governed handling of the old data.

What is a source-to-target mapping?

A field-level record of where target data comes from, how it changes, what exceptions apply and who owns the rule.

Why reconcile if record counts match?

Matching totals can hide missing, duplicated, misclassified or incorrectly linked records.

Must every old field be migrated?

No. Scope, necessity, authority, retention and target usefulness should determine the decision.

What is rollback?

A controlled route to restore an agreed safe state when cutover criteria are not met.

Who signs off a migration?

Use the named technical, business, data, security and other authorities required by the organisation and risk.