01 A&D migration preflight

Check Your A&D Export Before You Migrate.

Find structural problems, mapping gaps, duplicate identifiers, missing values, and date conflicts before changing systems. You get the result before we ask for contact information.

See what is checked

Runs locally in your browser. Your CSV is not uploaded for the preflight.

02 Local workbench

Select. Map. Inspect.

Generic CSV is the only supported profile in this release. Every critical mapping remains under your control.

1Select 2Map 3Run 4Results
Step 1

Select an export

No file selected

UTF-8 CSV · tested browser limit shown after performance verification · one header row

The selected file is processed locally and is not uploaded for preflight validation.

06 What this proves

A migration check with boundaries.

The preflight creates a repeatable data-quality artifact. It does not decide what the correct historical value should be.

01

Inspect the file

Detect UTF-8 text, delimiters, headers, malformed rows, column-count changes, and browser safety limits.

02

Review the mapping

Confirm required identity, acquisition, disposition, source, and status fields. Suggestions always remain editable.

03

Run versioned rules

Evaluate stable PASS, WARNING, and BLOCK rules without changing a record or calling an external AI provider.

04

Preserve the evidence

Download a redacted report tied to the exact local file fingerprint, then use it to plan correction and reconciliation.

Checked now

  • File structure and mapping completeness
  • Missing identity and source values
  • Duplicate rows and serials
  • Date parsing and chronology
  • Disposition-state conflicts
  • Formula-like and unsafe cell content

Not certified here

  • Legal sufficiency or ATF approval
  • Accuracy against original paper records
  • Unknown proprietary export semantics
  • Type 07 manufacturing workflows
  • Enterprise multi-location cutovers
  • Automatic import into BoundStack