Migration assurance
Validate migrated data, not only source patterns
Static analysis identifies risky code. These three sample-data validators check whether representative payloads, reports and financial pages behave as expected after migration.
- Orders: Same-order v0 versus v2026-01-01 payload parity
- Settlement: Flat File V2 sample structure, locale and canonical-row requirements
- Finances: Request manifest, one or more page samples, duplicate detection and breakdown reconciliation
- Method: Deterministic comparison. No code executed and no Amazon credentials.
Choose a validator
| Validator | Use it for | Result |
|---|---|---|
| Orders Payload Parity | Compare representative responses before staged rollout | Mapped, moved, changed, unavailable or not-verified fields |
| Settlement Flat File V2 Sample | Exercise a reference header- and locale-safe parser before cutover | Compatibility requirements and sample parsing risks |
| Finances Reconciliation | Validate request manifest plus one or more listTransactions page samples | Window, safety, token, duplicate and accounting deltas |
Orders payload parity Settlement sample validator Finances reconciliation
How validator evidence is scoped
A validator result applies to the supplied samples and manifest. It does not prove all production traffic is complete, so reports distinguish PASS, PARTIAL, FAILED and NOT_VERIFIED rather than presenting a universal guarantee.
Frequently asked questions
Do validators call Amazon?
No. They process only the samples you submit.
Do they replace staged rollout?
No. Use them before and during a staged rollout with production reconciliation.
Official sources
Validate a representative migration sample
Open the interactive validator workspace and select the matching module.
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/validators