Skip to content
Quantum9
DataHiring

Migration between banks: validate equivalence before the change

2 min reading
Editorial illustration: Migration between banks: validate equivalence before the change

Migrating a bank is not just about transferring records. Query types, ordering, precision and behavior can change and affect the application even when the row count matches.

How to evaluate this decision

Inventory application structures, queries, and dependencies. Define equivalence criteria according to use: values, links, calculations and performance. Plan initial load and handling of changes during transition. The return to origin needs to consider data recorded in the new environment; Restoring an old copy may lose later operations.

Criteria for comparing proposals

  • Conversion: map types, precision, encoding, and relevant constraints.
  • Conference: compare totals, samples and integrity rules, in addition to number of lines.
  • Turnaround: establish window, responsible parties, necessary freezes and criteria for reversing.

A scenario to discuss with the supplier

Hypothetical example: a numeric field changes precision and changes rounding used in reports. The base seems complete, but the results are no longer consistent.

What to validate upon delivery

Reproduce critical journeys and queries at the destination with controlled data. Test a rehearsed turnaround and document how to reconcile operations that occurred during the transition.

Prepare the conversation about the project

Bring Quantum9 technologies, volumes, required availability and dependencies. The proposal must include functional testing and validation, without promising no interruption before knowing the conditions.

Data engineering · Map the company's priority

Deepen the assessment

Read the context guide for this hire.

Let's evaluate your company's scenario?

Tell us about the problem, the systems involved and what needs to change. From there, we define the next step and the scope of the conversation.