Database migration should preserve the meaning and relationships of business records, not merely copy files. Zoha can scope mapping, trial migration, reconciliation and cutover around the source and destination systems. Agree who approves transformed records, how changes during the move are handled and what recovery is possible before replacing a working data source.
Updated
On this page
Clarify what is moving and why
A business may be replacing an application, changing hosting or consolidating information from several systems. Each situation creates different mapping and validation work. Identify the source, destination, record types and business owner who can decide whether the result is correct.
A database engine name and a total file size are not enough for an estimate. Include attachments, reference lists, connected applications, reports and user access where relevant. The migration scope should explain which items move, which remain available elsewhere and which require a separate decision.
Agree how each record changes
| Mapping area | Decision required | Check after the move |
|---|---|---|
| Identity | How old and new record identifiers relate | References point to the intended records. |
| Fields | Destination names, types and required values | Dates, amounts and text retain the approved meaning. |
| Duplicates | Business rule for possible duplicates | No silent deletion or unwanted merging. |
| Relationships | Connections between parent and child records | Related records remain associated. |
| History and files | What is included and how it is linked | Required history and attachments remain accessible. |
| Exceptions | Treatment of incomplete or invalid records | Unresolved records are reported rather than hidden. |
The business owner approves meaning; the delivery team implements and verifies the agreed transformation. Do not let an automatic format conversion silently decide how an ambiguous date or missing value should be interpreted.
Use a trial migration to find real problems
Work with an authorized copy or suitable sample in a controlled environment. Compare record counts, key totals where meaningful and representative records across the source and destination. Check the application functions that use the records, because a successful import does not prove the application can use them correctly.
In a hypothetical customer-system migration, the trial could reveal that two source address fields were combined into one target field while a delivery instruction was omitted. The remedy is to agree the mapping and repeat the relevant checks. The trial should produce an exception record and decisions, not just a statement that the import ran.
Define the final change and its stop conditions
- Choose the final source of truth and the person authorized to approve cutover.
- Agree how updates made during migration will be captured or paused.
- Confirm backups, access and the recovery route before the final move.
- Use named acceptance checks for records, relationships and application behavior.
- State which failures stop the move and who decides the next action.
- Keep the source available or retained only under the agreed access and retention plan.
Rollback becomes more difficult once the destination accepts new changes. Define that point and the treatment of new records before switching users. A vague promise to restore a backup is not enough if doing so would discard valid work created after cutover.
Hand over the evidence and unresolved items
The delivery record should include mapping decisions, trial results, final reconciliation, exceptions and business acceptance. Provider migration tools can support validation, but their coverage and limitations still need review. AWS's documentation, for example, treats data validation as a distinct activity with resource and time requirements.
We can discuss a migration plan and related application changes using the actual systems and data rules. Do not send live database exports or credentials in an ordinary enquiry. Arrange appropriate access and handling after the scope is clear, and define who maintains the destination and retained source records after handover.