SAP is Decommissioning ONB 1.0 on May 14 — Is Your Organization Ready?
ONB 1.0 Is Being Retired.
Here’s What You Need to Do.
SAP will permanently decommission Onboarding 1.0 on May 14, 2026. Your data, your compliance records, and your new hires are at risk if action isn’t taken before the deadline.
A Major System Shutoff Is Coming.
On May 14, 2026, SAP will permanently remove Onboarding 1.0 from the SAP SuccessFactors ecosystem. This is not a migration — it is a shutoff. Once it happens, 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.
This is more than a technical upgrade. It requires careful coordination between HR, IT, and compliance teams to ensure employee records — including I-9 documentation and onboarding files — are preserved before the system goes dark.
Why This Matters
Two Compliance Risks That Can’t Wait.
Onboarding systems store critical documentation and employee compliance records. When ONB 1.0 is retired, anything not migrated or downloaded beforehand is gone permanently. Two areas present the greatest risk:
I-9 Reverification Tracking
Records with reverification dates within the next 90 days will not migrate automatically. These employees must be identified and tracked manually before the deadline.
Onboarding Documents
Any document stored in ONB 1.0 that is not migrated or manually downloaded before May 14 will be permanently and irreversibly lost — with no path to recovery.
ONB 1.0 is gone on May 14. The data goes with it. Any new hire still in the system loses access immediately. There is no recovery path — only preparation.
If a new hire is still onboarding in ONB 1.0 after May 7, 2026, you may not have enough time to complete Path A or Path B before the May 14 shutoff — putting their access and your compliance records at risk.
What Clients Need to Do
Your Required Actions Depend on Where You Are.
The steps your organization must take before May 14 depend on whether you have already implemented Onboarding 2.0. Both paths require action — there is no scenario where doing nothing is safe.
Path A — ONB 2.0 Already Implemented
Migrate all I-9 reverification data from ONB 1.0 to ONB 2.0 — paying close attention to records within the 90-day window, which will not transfer automatically. Then run the ONB 1.0 document migration job to move all stored documents to SAP SuccessFactors document storage.
Path B — ONB 2.0 Not Yet Implemented
The timeline no longer allows for a full ONB 2.0 implementation before decommissioning. Your immediate priority is to manually download all ONB 1.0 documents and export or record all employee reverification dates — then establish a manual tracking method going forward.
- !One-time migration job warning (Path A): The document migration job cannot be re-run. Ensure no onboarding activities remain active in ONB 1.0 before executing it, and confirm that SuccessFactors document storage capacity is sufficient before you start.
- !Active new hires (all clients): Proactively transition or complete all active ONB 1.0 onboarding processes by May 7. Waiting until the May 14 shutoff creates unnecessary disruption for employees mid-onboarding and leaves no time to complete your migration steps.
Action Checklist
Everything That Must Be Done Before May 14.
| Scenario | Required Action | Deadline |
|---|---|---|
| All All Clients | Ensure new hires in ONB 1.0 are all in “Completed” status | May 7, 2026 |
| Path A ONB 2.0 Implemented | Migrate I-9 reverification data (>90 days) to ONB 2.0 | May 14, 2026 |
| Path A ONB 2.0 Implemented | Run ONB 1.0 document migration job | May 14, 2026 |
| Path B Not Implemented | Manually download all ONB 1.0 documents | May 14, 2026 |
| Path B Not Implemented | Manually track all I-9 reverification dates | May 14, 2026 |
See It in Practice
We’ve Done This. Here’s the Proof.
Worldwide Flight Services (WFS) faced exactly this challenge — a live ONB 1.0 environment, a hard deadline, and the complexity of migrating to Onboarding 2.0 without disrupting operations for one of the world’s largest cargo handling companies.
Intrizen led that modernization end-to-end. The full story — including the migration approach, the compliance safeguards, and the outcomes — is documented in our published white paper.
Case Study — Worldwide Flight Services
How WFS successfully modernized from SAP SuccessFactors Onboarding 1.0 to 2.0 with Intrizen — protecting employee data, maintaining compliance, and setting the foundation for scalable onboarding across global operations.
Why Intrizen
You Don’t Navigate This Alone.
Navigating a system decommissioning is complex — especially when it intersects with compliance, employee data, and HR operations. Intrizen has guided enterprise organizations through SAP SuccessFactors for over a decade: American Airlines, Grainger, NRG, and Worldwide Flight Services. We know what a high-stakes deadline requires.
If you’re unsure where to start, an expert review by the Intrizen team can clarify the fastest and safest path forward — whether you’re on Path A, Path B, or somewhere in between.
Multiplying Happier Human Connections through Digital Transformation — including making sure the systems that support your people are protected when it counts most.
Ready to Confirm Your Path Before the Deadline?
Connect with an Intrizen SAP SuccessFactors consultant to review your environment, validate your approach, and make sure everything is done before May 14.
Schedule a Conversation →Related Posts
Q2 2026: Highlights, Milestones & What’s Next at Intrizen
A Quarter of Growth, Transformation & New Possibilities Q2 was a season of momentum at…
Intrizen Named to Inc. 5000 for Second Consecutive Year, Rising 836 Spots in 2026
Two years on the list. 836 spots higher. And 238% three-year revenue growth. Intrizen has…
Replay Now Available: Attracting & Retaining Top Talent in the Public Sector
Turning Today's Talent Challenges into Tomorrow's Competitive Advantage Thank you to everyone who joined our…