Before switching systems in a legacy modernization project, the question is not only “Has the data finished loading?” It is also “Who confirms that the new data can support ongoing work?” SIers, CTOs and PMs in Japan should include reconciliation responsibilities in the offshore engagement scope from the start, alongside development and testing effort.
1. Agree on the data to reconcile
Start with work that must continue after the transition: open orders, receivable balances, inventory or requests awaiting approval. Specify periods, statuses, historical data retained for reference only and any exclusions.
In its SSIS/ETL migration guidance, AWS recommends deciding on a data validation strategy when choosing the migration approach, including rules for comparing source and target data.[1] For business systems, add another question: which results must reconcile so users can continue their work?
2. Write reconciliation rules in business terms
For each data group, define how corresponding records are identified and what result is expected. Where codes are merged, statuses changed or old data excluded, document the transformation rule and its approver.
We suggest checking counts, aggregate values and important cases at detail level. For an open order, for example, review its customer, line items and processing status. Do not use a single total as the entire body of acceptance evidence.
3. Hypothetical example: receivables before cutover
Suppose a company is replacing its sales management system. Both parties plan to reconcile receivables by customer at an agreed cutoff point. This is an illustration, not a TECHNEST project result.
One customer’s balance differs between the two systems. The development team traces source data and transformation rules, while business staff check the related documents, payments and adjustments. If a merged customer code explains the difference, record the mapping and the results of reconciliation after that clarification. Mark the issue complete only when the responsible person confirms the evidence.
4. Separate execution from business approval
The offshore team can prepare migration programs, discrepancy reports and traceability documentation. The client’s data owner confirms the meaning of the figures and any accepted exceptions. The PM coordinates unresolved issues; separately identify the person authorized to approve the system switch.
For every discrepancy, record its cause, impact, resolution approach, owner and confirmation deadline. Avoid leaving an item “under investigation” without stating the decision it needs.
5. Include reconciliation in rehearsals and cutover decisions
Allow time for trial runs, investigating differences and reconciling again after corrections. Define how data created after the cutoff will be handled. Before switching systems, review evidence, open issues and stop or postponement conditions. A “program completed successfully” notification should not replace this decision.
Clarify migration scope with TECHNEST
TECHNEST brings years of experience working with the Japanese market in business-system design and legacy modernization. Start with one important data group, the rules currently used and the person responsible for confirming it. Explore our software outsourcing services or contact TECHNEST to discuss scope, responsibilities and a verification plan.
Reference
[1] AWS Prescriptive Guidance, Determining the migration approach, data validation guidance within the SSIS/ETL migration guide; accessed November 18, 2026. The business recommendations in this article should be adapted to each project.







