Migration assurance
Find Amazon SP-API migration blockers before removed resources stop working
Scan source code, validate sample data, compare fixes and generate an evidence-backed migration plan for the Amazon SP-API resources scheduled for removal.
- Legacy settlement reports removed: November 11, 2026
- Orders API v0 operations removed: March 27, 2027
- Finances v0 financial-event operations removed: August 27, 2027
- Method: Static analysis only. No code executed, no Amazon credentials.
Real report preview
This is the same structured finding shape produced by a scan: scoped status, typed evidence, official mapping and a concrete validation step. Source-based findings include the file, line and redacted evidence where available. Changes that automated analysis cannot conclusively verify require manual verification by your development or QA team.
| Severity | Rule | Evidence | Required change |
|---|---|---|---|
| BLOCKER | AMZ-ORD-OPERATION-001 | src/orders.ts:84 — getOrderBuyerInfo(orderId) | Use getOrder with includedData=BUYER; compare v0 and v2026 payloads. |
| HIGH | AMZ-FIN-PAGINATION-001 | finance/sync.ts:117 — stop on empty transactions[] | Continue until nextToken is null, including empty pages. |
What the scanner detects
- Deprecated operations, endpoints and settlement report types.
- Parameter, enum, fulfillment, status and includedData migrations.
- Parser risks: positional columns, locale amounts and recursive breakdowns.
- Data-loss risks in Finances windows, pagination, completeness and deduplication.
- Configuration and source patterns that need verification by your development or QA team.
What paid reports unlock
The commercial value is the migration outcome package: a developer-ready plan, evidence for review and repeatable checks that show progress before cutover.
| Outcome | What the team receives | Why it matters |
|---|---|---|
| Prioritized migration action plan | Tasks grouped by dependency, severity and validation step | Engineering knows what to fix first. |
| Re-scan before/after comparison | Fixed, remaining, new, moved and regressed findings | Progress is measurable after each upload. |
| Migration quality gate | BLOCKED, AT_RISK, READY_WITHIN_TESTED_SCOPE or NOT_VERIFIED | Cutover status is evidence-backed, not an unscoped score. |
| Orders functional parity | Same-order v0 versus v2026 sample comparison | Staged rollout can compare behavior before switching. |
| Settlement sample validation | Flat File V2 header, locale and canonical-row checks | Parser requirements and accounting sample risks become visible. |
| Finances reconciliation | Window, page-chain, transaction-ID and breakdown-total checks | Financial totals can be reconciled within supplied scope. |
| Evidence package | HTML, CSV, JSON, SARIF, action plan and quality gate | Reviewers get portable artifacts. |
| Project history and access recovery | Private report links, project records and recovery flow | Teams can return to the work during the access window. |
Three migration modules
| Module | Removed | Replacement | Deadline |
|---|---|---|---|
| Orders | Six Orders API v0 operations | Orders API v2026-01-01 | March 27, 2027 |
| Settlement | Legacy flat-file and XML settlement reports | Flat File V2 | November 11, 2026 |
| Finances | Three v0 financial-event operations | listTransactions v2024-06-19 | August 27, 2027 |
How it works
- Submit a pasted snippet or a source-only ZIP; dependencies are never installed.
- Select one or more migration modules and run deterministic static analysis.
- Review typed evidence, confidence, official mappings and unverified scope.
- Apply the dependency-aware action plan, validate samples, then re-scan.
Migration assurance workflow
A report is more than a list of matches. Findings are grouped into an ordered action plan, evaluated by a deterministic quality gate and exported as an evidence package for implementation and review.
- Action plan groups related findings and shows dependencies.
- Quality gate returns BLOCKED, AT_RISK, READY_WITHIN_TESTED_SCOPE or NOT_VERIFIED.
- Evidence package includes report data, SARIF, coverage, quality gate and action plan.
Re-scan comparison and quality gate
Upload the changed source again and compare the new report with the baseline. Stable fingerprints classify findings as fixed, remaining, new, regressed or moved; ruleset changes are disclosed.
Sample-data validators
| Validator | What it checks | Output |
|---|---|---|
| Orders Payload Parity | Same-order v0 vs v2026-01-01 fields and semantics | Missing, moved and remapped fields |
| Settlement Sample Validator | Headers, canonical rows and locale-safe amounts | Parser requirements and sample risks |
| Finances Reconciliation | Windows, pages, tokens, transaction IDs and recursive breakdown totals | Completeness and delta findings |
Orders parity Settlement sample validator Finances reconciliation
Security and retention
- Source code is statically analyzed, never executed and never retained in the report store.
- ZIP bomb, unsafe path, symlink, nested archive and encrypted archive guards run before scanning.
- Possible secrets are masked; analytics excludes filenames, snippets, emails, IDs and tokens.
- Private report links expire and reports can be deleted; re-scans require a fresh source upload.
Supported languages, formats and exact scope
Programming languages include TypeScript, JavaScript, Python, Java, Kotlin, C#, Go, Ruby and PHP. Structured/config inputs include JSON, YAML, XML, CSV/TSV, Terraform, .env, properties and INI. Unsupported or skipped files remain visible as unverified scope.
Pricing preview
Prices and entitlements below come from the same backend product catalog used by checkout.
| Product | Price | Modules | Includes |
|---|---|---|---|
| Free Quick Scan | Free | all | Sample scan and quick real scan; Readiness summary; Finding titles and affected files |
| Single Migration Report | $39 | 1 | All detailed findings for one module; Prioritized migration action plan; Migration quality gate |
| Complete Amazon Bundle | $79 | 3 | Orders + Settlement + Finances detailed findings; Cross-module migration action plan; Migration quality gate |
| Agency Pack | $249 early access | 3 | Early-access pricing — available during beta; 5 client project credits; Client-ready report |
Customer outcome
The intended outcome is a defensible cutover decision: known blockers have owners, sample data reconciles, re-scans show progress, and remaining uncertainty is explicitly assigned to development or QA verification rather than hidden behind a green score.
Frequently asked questions
Do you execute my code?
No. The scanner performs static analysis only. It never runs your code, installs dependencies, or calls Amazon with your credentials.
Is a clean result a guarantee?
No. A clean result means ready within the tested scope. Static analysis proves the presence of a problem, not the absence of every possible one.
Official sources
Turn migration uncertainty into an evidence-backed plan
Run a scoped static scan now, then use validators and re-scans to prove each change.
Last reviewed: 2026-07-02.
Open the interactive scanner: /app#/