Trusted by employers nationwide

I-9 Migration — We Handle Every Record, Every Version, Every System

Every HCM and legacy I-9 system exports data differently — and some drop critical fields in the process. Our migration team pulls, cleans, and loads your records from any source system, any paper archive, any form version — with a written statement documenting every decision we made.

Backwards compatible every I-9 version
27+ years of I-9 expertise
Every HCM + paper archive
Migration · Active
In Progress
PROJECT · ENTERPRISE MULTI-SITE
12,847
records migrated · 3 form versions spanning 1996–2024
Discovery
Extract
Audit
Load
Cutover
Section 1 & 2 Records
12,847
Supplement B Reverifications
1,412
E-Verify Case Numbers
9,204
Supporting Document Images
24,189
14
Form versions supported (back to 1987)
20,000+
Records in a single migration
27+ years
Of I-9 and E-Verify expertise
Every
Major HCM, legacy system, and paper archive

TRUSTED BY HR TEAMS ACROSS INDUSTRIES

AIRBUS
FOUR SEASONS
VERIZON
STACY AND WITBECK
YUM! BRANDS
ALPHA BAKING
AIRBUS
FOUR SEASONS
VERIZON
STACY AND WITBECK
YUM! BRANDS
ALPHA BAKING

Every source system has migration quirks worth planning for

Most major HCMs and legacy I-9 platforms have documented export limitations — fields that don't transfer cleanly, formats that need translation, audit trails that require separate handling. Here's what to watch for.

Supplement B data goes in one way

Records converted from HireRight into Workday lose document expiration data. Workday won't send reverification reminders on converted records. Universities running migrations have documented this publicly — organizations are forced to maintain parallel legacy systems.

Onboarding 1.0 is being sunset

SAP has announced end-of-maintenance for Onboarding 1.0 with forced migration to Onboarding 2.0. Active reverification tasks won't migrate — they must be completed in the legacy system first. Cross-module bugs between Employee Central and the I-9 form add remediation work.

Historical data extraction takes custom work

ADP contracts often don't include data portability clauses — customers have "no clear exit path for acquiring full history." UKG's standard exports don't include I-9-specific endpoints. Both platforms typically require custom reports to pull historical I-9 records.

Decades of forms. Fourteen versions.

A company hiring since 1986 may have I-9s across eight or more form versions — each with different fields, different document lists, different acceptable formats. Cursive handwriting, coffee stains, faded carbon copies. OCR alone gets you 60–75% accuracy.

Migration · Chain of Custody
01
Source System Extract CSV · XML · PDF · Paper · Any format
02
Pre-Migration Audit Compliance gaps flagged · Duplicates resolved
03
Standardization & Load Field mapping · 14-version form normalization
04
Migration Statement Formal record of assumptions & decisions
05
Client Sign-Off & Cutover Go-live · Hypercare · Legacy retention

A managed migration — not an export template

You don't send us a CSV and hope it imports. You don't fill out a data dictionary and pray it matches. Our team runs the migration end-to-end, keeps the audit trail chain of custody intact, and hands you a formal Migration Statement when it's done.

1
We pull from any source

Workday EIB, SAP OData API, ADP custom reports, UKG SFTP exports, Mitratech tab-delimited files, paper archives, legacy Lookout Services records — we've seen the export format.

2
We run a pre-migration audit

Incomplete forms, missing signatures, expired documents, unrecorded Supplement Bs — we find them in your data before they become an ICE finding in your new system.

3
We document every decision

Records we brought over, records we excluded, fields we standardized, assumptions we made. The Migration Statement is your permanent record of what happened.

A written record of what we migrated — and what we didn't

Every migration we run ends with a written statement from our compliance team. It spells out the assumptions we made, the records we excluded, and the decisions your legal or compliance reviewer might want to question years later.

If ICE ever knocks, the provenance of every record in the system is already documented. Your audit defense doesn't have to be reconstructed from memory.

Exhibit A
Migration Statement
Client · Enterprise Multi-Site · Project 2026-047
Source System
SAP SuccessFactors Onboarding 2.0, migrated from 1.0 in 2023
Records Scope
12,847 I-9 records across 3 form versions (Rev. 03/08/13, 10/21/2019, 08/01/2023)
Excluded Records
217 incomplete Section 1 (no employee signature) — documented, not imported
Supplement B Handling
All reverification blocks preserved in chronological order per USCIS guidance
Audit Trail Disposition
Source-system audit trail archived by client; not imported (does not meet 8 CFR 274a.2)
Signed, i9 Intelligence Compliance Team
§

Every field. Every form version. Every format.

We're backwards compatible with every version of Form I-9 ever issued by USCIS — and we've built ingestion paths for every major HCM, I-9 vendor, and paper archive in the country.

01

Sections 1, 2, and Supplement B

Full record migration including all reverification blocks in chronological order. We don't drop historical Supplement Bs to simplify — ICE expects the complete chain during an inspection.

02

14 Form Versions Since 1987

From Rev. 03/20/87 through Rev. 08/01/2023. Field mapping across the 1-page era, the 2013 expansion, and the 2023 return to two-page + supplements. No HCM touches this range.

03

E-Verify Case Numbers & Status

Case numbers, TNC resolution history, photo-matching results — all preserved and linked to the correct I-9 record. E-Verify audit defense stays intact after the cutover.

04

Supporting Document Images

Driver's licenses, passports, green cards, EADs, Social Security cards. PDF, TIFF, JPEG — whatever your source system produced. 300 DPI minimum, legibility-preserved.

05

Paper I-9 Digitization

Trained data-entry specialists transcribe paper records field-by-field. Not pure OCR — human review catches the handwriting, the cross-outs, the staple holes, and the cursive.

06

Audit Trail Chain of Custody

Source-system audit trails are archived with documented provenance. The Migration Statement records what was brought forward and what remains with the client's original system.

Five phases. One team. A documented outcome.

Most migrations take 2–8 weeks depending on volume and source system. Paper-heavy or multi-format projects run longer. We scope timing during the discovery call, not after you've signed.

1

Discovery

Source system, record volume, form versions, condition of data. 60-minute working session.

2

Extract

We pull from your source system, coordinate with your current vendor's export process, or digitize paper.

3

Audit

Pre-migration compliance review. Incomplete records, missing signatures, duplicates, expired docs — all flagged.

4

Load

Field mapping, version normalization, QA review. Migration Statement drafted and reviewed with you.

5

Cutover

Client sign-off, production go-live, hypercare support. Source-system data retention handed back to you.

Built for every reason you'd move I-9 records

You've outgrown the built-in I-9

Your Workday, SAP, ADP, or UKG module creates the form but can't handle remote verification, Supplement B reminders, or audit-ready reporting.

You're leaving Equifax or Tracker

Your previous provider was acquired, priced up, or service degraded. You need to bring your history with you without starting over.

You received a Notice of Inspection

Records are scattered. Some paper, some digital, some lost. Migration plus a compliance audit gets you to a defensible posture before the deadline.

You just acquired a company

You've inherited an unfamiliar I-9 portfolio from another payroll system, another vendor, or three of them. Everything needs to land in one compliant repository.

You still have filing cabinets

Decades of paper I-9s in storage. Some legible, some not. Some past retention, most not. Digitization with compliance review, not just scanning.

SAP is forcing your hand

Onboarding 1.0 end-of-maintenance is approaching. Rather than migrate to 2.0 and inherit its limitations, bring your I-9s to a purpose-built compliance platform.

Migration is a competitive category. Here's how we stack up

Straightforward comparison — no disparagement. Comparison reflects publicly documented capabilities. Specs change; verify current offering before making a final decision.

Capability
i9 Intelligence
Purpose-built migration team
Equifax / LawLogix
GUARDIAN
Mitratech Tracker
HISTORICAL CONVERSION
HCM Built-in Module
WORKDAY / SAP / ADP
14 form versions (back to 1987)
included in every plan
Partial
Partial
Formal Migration Statement
Paper I-9 digitization (manual transcription)
Pre-migration compliance audit
Separate fee
Supplement B — all reverifications preserved
Separate fee per record
Varies
Data loss documented
E-Verify case history preserved
Partial
Often lost
Remote Section 2 for employees needing re-verification
$95/ appointment
Any source format (CSV, XML, PDF, paper, proprietary)
Data dictionary required
PDF + tab-delimited only
Proprietary
No per-I-9 excluded-record fee
Fee charged either way
Varies
N/A
Dedicated compliance team (not an implementation queue)
Enterprise only
Enterprise only

Priced per record. Scoped to your portfolio.

Migration pricing is per-I-9, not per-seat. Final quote depends on volume, source system, form-version spread, and paper-to-digital ratio. Discovery call is free — no migration scope is binding until you sign the Statement of Work.

Electronic Migration

For HCM or vendor-to-vendor transitions with clean source data.
Pricing
Per-record · Quoted in SOW
Field extraction from source system
14-version form-field normalization
Supplement B reverification chain preserved
E-Verify case numbers & status
Supporting document images migrated
Formal Migration Statement
Paper digitization
Full compliance audit with remediation plan
Get a Quote

Paper + Full Audit

For companies with decades of paper I-9s or mixed-format archives.
Pricing
Per-record · Quoted in SOW
Everything in Migration + Audit
Paper I-9 digitization (manual transcription)
Scanning & image attachment
Legibility review & illegible-record flagging
Retention-period calculation for each record
Past-retention I-9s flagged for client disposition
Remote Section 2 for employees needing re-verification
Get a Quote

Questions companies ask before migrating

How long does an I-9 migration take?

2–8 weeks depending on volume, format, and source system. Paper-heavy runs longer.

What is a Migration Statement, and why does it matter?

Formal document recording every decision. No other vendor produces one. Tied to 8 CFR 274a.2.

What happens to my Supplement B reverification records?

Every block preserved in chronological order. Call out Workday/HireRight data loss.

Can you migrate from any HCM or legacy system?

Yes. List Workday, SAP, ADP, UKG, Mitratech, Equifax/LawLogix, Lookout Services, paper.

What about I-9 form versions from the 1980s and 1990s?

14 versions back to 1987. No HCM matches this range.

What does "per-record pricing" mean in practice?

Per I-9, no excluded-record fees (unlike Equifax/Guardian). Quote via SOW after discovery.

Do we still need our old system after migration?

Yes, typically 12–24 months for audit trail retention per 8 CFR 274a.2.

Can you handle an acquisition that brought in three different I-9 systems?

Yes. Each entity audited, source attribution documented.

What if we have compliance problems in our existing I-9s?

Common. Audit surfaces them, corrective action plan provided. Section 1 can only be fixed by employee.

Is remote Section 2 verification included if we need to re-verify some employees?

Yes, in Paper + Full Audit tier.

Your records. Our migration team. A defensible outcome.

The discovery call is free. We'll review your source system, record volume, and form-version spread — then tell you what a migration would actually take. No sales pitch, no hand-off to an implementation queue.

No credit card required. No long-term contracts. Just compliance done right.