Malformed rows
Quoted commas, duplicate headers, mixed delimiters, and changing column counts can shift values into the wrong fields.
FastBound migration · generic CSV available now
Move Records Without Trusting a Blind Import.
Preserve the source export, run it through a local A&D preflight, review every mapping and exception, then plan import and reconciliation. BoundStack does not claim a verified FastBound-specific profile in this release.
Where migrations fail
The dangerous part is the silent assumption.
Rows can parse successfully while meaning changes. A useful migration process exposes transformations and exceptions before any destination record is written.
Duplicate or altered serials
Whitespace, spreadsheet coercion, and separator changes can create collisions or disguise duplicates.
Incomplete history
Missing acquisition context, incomplete dispositions, and date conflicts can produce records that cannot be accepted automatically.
Wrong field matches
A familiar label can carry different source semantics. Critical suggestions require explicit review.
Hidden normalization
Date, whitespace, and case normalization must be visible and reconcilable against the original export.
No acceptance artifact
Without a hash, rule version, exception list, and before-and-after counts, a successful request is not migration evidence.
Conservative sequence
Export → preflight → reconcile.
Preflight is the first gate, not the import button.
Export
Create a fresh CSV through the source system’s supported export process.
Preserve
Keep the original file unchanged and identify it with a local SHA-256 hash.
Preflight
Check structure and expose the headers before assigning meaning.
Map
Confirm every critical target field and review transformations.
Review
Resolve BLOCK findings and document WARNING decisions.
Reconcile
After a separately approved import, compare counts and spot-check records.
Current release boundary: the public preflight never imports or modifies records. A later assisted migration must use a separate, explicit data-handling and acceptance process.
Supported and unsupported
Truth before vendor keywords.
Generic CSV mapping is supported. FastBound-specific semantics, versions, and field transformations are not yet verified by a representative fixture.
Available now
- UTF-8 generic CSV
- Manual header-to-target mapping
- Versioned structure, identity, date, state, source, and data-quality checks
- Local SHA-256 file fingerprint
- Redacted JSON and printable HTML reports
Not claimed
- Direct FastBound compatibility
- Coverage of every proprietary field or version
- Type 07 manufacturing migration
- Enterprise multi-location cutover
- Automatic record correction or import
- Legal certification or ATF approval
Privacy boundary
The preflight file stays with the dealer.
The raw CSV, filename, fingerprint, serials, names, addresses, and rows do not enter BoundStack analytics or the migration-review form.
CSV processing
Parsing, mapping, validation, filtering, fingerprinting, and report generation happen in the browser.
Product analytics
Only event names, versions, profile category, and coarse row, issue, and elapsed-time buckets may be recorded.
Human follow-up
After results, the dealer may submit contact details and safe result buckets through a separate consented form.
Start with the export you already have.
Choose Generic CSV, review every mapping, and keep the result before deciding what to import.