Start with a defined next step
Request a data migration assessment
Profile sources and define mapping, quality, rehearsal, reconciliation, cutover and recovery controls.
Page purpose
Know what you provide and what you receive when you request a data migration assessment.
Choose a data migration assessment when a defined source-to-target move needs decisions about meaning, ownership, quality, history, volume, controls, validation, and authority transfer. It is narrower than an enterprise systems assessment and different from cloud readiness: its unit of analysis is the migration and its data domains, not the estate portfolio or workload placement.
Initial inputs: source and target names, data domains, approximate volumes, known quality issues, history expectations, timing, and accountable owners. Immediate output: fit, clarifying questions, a proposed migration boundary, and a safe evidence plan. If commissioned, outputs can include source-target findings, a migration risk view, mapping and validation strategy, rehearsal sequence, reconciliation and recovery conditions, and decision gates. Detailed schemas, samples, records, profiling outputs, credentials, keys, and database dumps require an approved environment with proportionate minimization or masking where suitable.
When to use this step
When is this the appropriate next step?
- Migration is estimated before source condition, semantics, and ownership are known.
- Source-to-target counts are used without validating relationships, meaning, and business totals.
- Cutover planning omits exception treatment, rollback, retention, and transfer of authority.
What you receive
What you receive after fit is reviewed.
- Initial output: fit response, proposed assessment boundary, and safe input checklist.
- Commissioned output: source-target inventory, ownership, dependencies, and risk findings.
- Mapping, transformation, quality, exception, and reconciliation strategy.
- Rehearsal, cutover, rollback, retention, and authority-transfer plan.
- Known exclusions, unresolved semantics, and evidence confidence.
What happens next
What happens after the request is submitted.
- Define source, target, domains, history, authority, and acceptance owners.
- Profile structure, content, quality, volume, relationships, and operational change.
- Agree mapping, transformation, cleansing, and exception rules.
- Rehearse repeatedly and reconcile technical and business measures.
- Gate cutover on accepted evidence, recovery readiness, and ownership.
What to prepare
Information that makes the conversation useful.
- Which sources, domains, history, attachments, and audit records are included.
- Who owns mapping semantics, cleansing decisions, exceptions, and acceptance.
- What reconciliation tolerances and recovery conditions permit authority transfer.
Information safety
Information that should not be sent through a public form.
- Transmitting production, personal, financial, health, or otherwise restricted records through an unapproved route.
- Changing data meaning during transformation without accountable approval.
- Declaring success from row counts while business balances or relationships are incorrect.
Decision questions
Know the boundaries of the next step.
What is sufficient to scope the data migration assessment?
Source and target technologies, domains, approximate volumes, known issues, timing, and accountable owners are sufficient to begin. If profiling requires records, an approved controlled environment and proportionate masking or minimization should be agreed first.
What must not be sent through this request page?
Do not send database dumps, spreadsheets containing real records, personal or restricted data, credentials, connection strings, encryption keys, production schemas with secrets, or confidential mapping documents.