Skip to content

Who will account for the rows?

Choosing between an in-house acceptance procedure, the Toledo Migration Acceptance Kit and QuerySurge.

Migration acceptance · comparison · reviewed 1 October 2026

You have an exported-data migration approaching sign-off. Start with the inputs you can actually inspect, the evidence the approver needs, and who will maintain the checks after this run.

The Toledo kit’s ceiling: one source file against one target file, delimited text only, with both read into memory. No database, Excel, JSON, XML or Parquet input. It supplies evidence for your review; it is not an audit or attestation.

When each approach fits

Keep an in-house procedure when you already own the checks

If your team has tested queries or scripts, documented mappings and an accountable reviewer, build on them. You control the inputs, transformations and acceptance rules. You also own the tests, maintenance, exception record and proof that every row was accounted for.

Start with the free acceptance checklist. Agree keys, field mappings, exclusions and unresolved scope before writing a sign-off. Buying a tool does not make those decisions for you.

Use the Toledo kit for a bounded pair of exports

The kit supplies a standard-library Python comparison tool, a written procedure and a sign-off template. It accounts for source and target rows separately and writes JSON, printable HTML and a findings CSV. You declare the mapping, normalization and blank-value policy, then investigate the findings.

It fits when you can produce delimited-text exports that fit in memory and want inspectable local reports. It does not establish that the exports include all the original data, model one-to-many transformations or check every business rule. You still decide whether to accept the migration.

Inspect the complete fictional acceptance packet before choosing. Its input files, actual generated report and findings show what the kit produces and what remains a human decision.

Evaluate QuerySurge for broader enterprise validation

QuerySurge describes automated source-to-target validation, repeatable migration test suites and API-driven execution. Its integrations cover broader data sources than this kit’s file pair. That makes it a candidate when the requirement is connected systems and repeated validation across migration waves. Confirm your sources and operating requirements in an evaluation. Source: QuerySurge’s data migration testing page.

Its official trial comparison offers hosted cloud, downloadable and guided proof-of-concept paths. Those are different evaluation arrangements; check the current conditions against your environment.

Two rows can still hide a failed migration

Synthetic illustration, not customer data or generated tool output. Each file below has two records and a total balance of 30.00. Row counts and totals agree; record identities do not.

Two fictional records per file; balances in the same units
Source keyBalanceTarget keyBalance
10110.0010110.00
10220.0010320.00

With the key compared as written and no declared rejection, source 102 is missing and target 103 is an orphan. Ask who owns the discrepancy, whether it is an agreed exception, and what evidence is needed before sign-off. Any approach you choose must answer those questions.

Compare the purchasing arrangements, too

These products cover different scopes. A licence price alone does not compare implementation effort, validation coverage or total cost.

As checked on , QuerySurge’s published pricing lists a named Full User at US$12,642 perpetual, or US$6,006 per user for a 12-month subscription with a two-user subscription minimum. It also lists packages, cloud hourly options and enterprise quotes. Perpetual maintenance is listed at 18% annually, with the first year included and subsequent annual increases. Check regional conditions and current configuration costs with QuerySurge.

The Toledo kit has two perpetual licence choices, with full source and no licence expiry. Read the complete licence and the product’s purchase and delivery details. Consultancy rights cover client work; clients receive the outputs, while the kit stays with you.

Delivery uses an encrypted archive and a release key shown on the Stripe payment confirmation page. Do not rely on the receipt email to contain the key. Python and OpenSSL are required. Read the installation, delivery and receipt-recovery instructions before paying.

Take one decision to your reviewer

Identify the exact source and target, name the acceptance owner, and list what will remain untested. If the bounded export comparison fits, open the worked packet and judge the evidence yourself. If it does not, use your own procedure or evaluate a platform against the requirements the kit cannot meet.

Written by Toledo Technologies, the kit’s vendor. QuerySurge facts above come from its linked official pages, checked 1 October 2026; fit recommendations are our assessment. This is not a hands-on benchmark or an endorsement by QuerySurge.