On May 14, 2026, SAP SuccessFactors Onboarding 1.0 is shut off for good. Every I-9 record, audit trail, and supporting document still living in the system will be deleted. New hires mid-onboarding will lose access. There is no rollback.
If your company runs SAP and you haven't finished migrating to Onboarding 2.0 yet, your I-9 compliance data is now on a 30-day clock. And even if you have migrated, the 2.0 module you're landing on has a documented history of I-9 bugs, compliance gaps, and missing functionality that your HR team is now responsible for. This is why a growing number of SAP customers are treating the sunset as a decision point — not a migration.
SAP's Onboarding 1.0 end-of-maintenance date was November 6, 2025 — meaning no more patches, no more bug fixes, no more new I-9 form updates. The deletion date is May 14, 2026. Once the shutoff happens, according to SAP implementation partner Intrizen, "all data stored in ONB 1.0 will be irreversibly deleted, any new hires still onboarding in the system will immediately lose access, and no recovery options will exist."
For I-9 compliance, that means:
If ICE sends a Notice of Inspection in 2027 or 2028, the I-9 records you're being asked to produce will be the ones that successfully made it through this migration. Everything else will be unrecoverable.
The federal I-9 deadline hasn't changed. Section 1 must be completed by the new hire on or before their first day of work. Section 2 must be completed by the employer within three business days of the start date. A system migration is not a valid reason to miss the deadline. If your HR team loses days on a migration, the compliance clock keeps running — and those gaps are exactly what ICE auditors look for.
If you're on SAP Onboarding 1.0 today, there are two paths forward. You can run the 2.0 migration and hope the reverification sync, document storage, and audit trail data all land cleanly — or you can move I-9 to a dedicated compliance platform and keep the rest of your SAP stack intact. Talk to a compliance expert about which path fits your situation, or start with an I-9 audit to see exactly what you have before you migrate anything.
This is the question we hear most often from HR and operations leaders at SAP and ADP shops. It's a fair one. You've already paid for an HCM that handles payroll, benefits, onboarding, and time tracking. Why add another system?
The answer starts with a story. We recently migrated an enterprise client off SAP SuccessFactors onto our platform. Before the switchover, their HR team had built a custom-coded script that pulled data from eight different SAP reports and stitched them together just to reconstruct what a complete I-9 record actually looked like. The data existed. But SAP's I-9 module didn't surface it as a single, audit-ready record. Without that custom script, an ICE auditor asking for a specific I-9 would have seen fragments, not documents.
That's not an edge case. That's what happens when I-9 compliance is one small module inside a massive HCM platform that prioritizes payroll and core HR features over niche compliance workflows. The I-9 data is there — but assembling it, validating it, and defending it under audit pressure requires work the HCM doesn't do for you.
This isn't our opinion. It's what SAP has published about its own product. As of early 2026, SAP's knowledge base contains:
Each of these is a compliance risk. If Section 2 displays blank but the hiring manager signed it anyway, the I-9 is out of compliance — and SAP's own documentation includes a workflow where the system offers to terminate the employee for failing to present documents, when the actual failure was a system bug.
In January 2026, SAP released a fix to close a real compliance gap: in certain configurations, Onboarding 2.0 let hiring managers complete Section 2 without uploading any of the documents the new hire presented. Per SAP's own blog post, "previously, it was possible in some scenarios to complete Form I-9 Section 2 without uploading the document(s) presented by the employee."
Within weeks, SAP announced it was reversing the fix. Customer pushback was significant enough that SAP had to add a configuration toggle to let employers opt out of the new requirement. The episode tells you two things. First, for years, SAP customers were quietly completing Section 2 without capturing document images in some configurations — a gap an ICE auditor could exploit. Second, when SAP finally shipped the fix, the implementation was disruptive enough that customers revolted. A specialized I-9 platform handles document retention correctly on day one, with no reversal required.
SAP's 1H 2026 release notes announce that Form I-9 reverification details are "now displayed directly on the New Hire Details page." Until that release, HR teams had to navigate elsewhere to see reverification status for their workforce. Configurable reverification trigger windows — 30, 60, 90, 120, 180, 240, and 540 days — also just arrived in 2026. For companies with employees on work authorizations, this is foundational functionality that a dedicated I-9 platform has had for a decade.
SAP's approach to remote I-9 verification is simple: find your own authorized representative. Per SAP's own knowledge base, "Section 2 document verification must be completed by a verification representative. The I-9 form must be physically signed by someone designated by the company as an Authorized Representative, who then faxes or emails the I-9 form to the corporate office."
There is no built-in video verification. No managed service. No trained representative network. If you hire a new employee in a city where you don't have an office, SAP leaves you to source a representative, coordinate the meeting, manage document transmission, and then manually complete the SAP workflow. For companies hiring remote employees across the country — which is now most companies — this is a daily operational problem SAP does not solve.
Remote verification is one of the reasons specialized I-9 platforms exist. Our remote Section 2 service uses a trained U.S.-based team and a live video call to complete verification anywhere in the country. No notary, no travel, no fax.
Path 1: Run the migration carefully. If you're committed to SAP Onboarding 2.0, don't wait. Run the pre-migration audit reports now. Resolve record errors before the migration job. Confirm document storage capacity. Plan for a second migration pass to catch records that fail the first run. Manually spot-check reverification records after migration to make sure active processes from 1.0 actually landed in 2.0. Budget for the cases that don't migrate cleanly — because there will be some.
Path 2: Move I-9 to a dedicated compliance platform. You don't have to migrate I-9 into Onboarding 2.0. You can move it to a standalone I-9 platform that integrates with SAP for employee data and HR workflow, while giving you a purpose-built system of record for Form I-9, E-Verify, reverification, and document retention. This is the path a growing number of SAP customers are choosing — not because SAP isn't a good HCM, but because I-9 compliance is a specialist problem and the HCM isn't built for it.
Either way, the deadline is fixed. May 14 is not negotiable. The decision is how much of your compliance infrastructure you want riding on SAP's 2.0 cutover versus how much you want under your control.
The next 30 days are the difference between a clean I-9 program and a compliance problem you'll be explaining to an auditor in 2027. Whether you're sticking with SAP 2.0 or evaluating alternatives, the worst outcome is running out the clock without a plan. Book a free compliance call — we've migrated enterprise clients off SAP, and we can tell you exactly what to watch for.
Our compliance team has 27+ years of Form I-9 and E-Verify specialization. If you have questions about a specific migration scenario, a reverification edge case, or how to evaluate your SAP I-9 data before the cutover, reach out directly.
