A vendor closing its doors sounds like an IT problem: cancel a subscription, pick a new tool, move on. But a good share of what lives in HR and hiring software, Form I-9s, background check consents, offer letters, wage records, carries a legal retention clock that keeps running whether or not the platform that hosted it still exists.
When a vendor sends the “we’re shutting down, export your data” email, most companies treat it as a file-saving scramble. It’s a compliance deadline, and treating it as anything less is where the risk sits.
Retention Is the Employer’s Obligation, Not the Vendor’s
Whatever software stored those onboarding forms, the legal duty to retain them for the required period belongs to the company that hired the person, not the company that sold the software. Vendor terms of service almost always state explicitly that the customer is responsible for its own records and backups. The platform is a place to keep files, not a party to the employer’s compliance obligations, and when it closes, that responsibility doesn’t transfer to anyone. It just comes due.
FormSwift is closing on September 30, 2026, and the pattern is worth watching because it’s playing out in real time. Users get a fixed window to export whatever they built on the platform. After that, the files are gone, and the vendor’s shutdown notice doesn’t extend anyone’s legal retention period. If you’re one of the people staring down that deadline and need somewhere to land, there’s a FormSwift replacement guide that covers what carries over and what doesn’t.
The exposure runs deeper for companies that hire through a staffing partner and then convert contractors to full-time employees. That path often means two separate onboarding paper trails, one from the staffing agency’s systems and one from the employer’s own, sometimes running through two different platforms that never talk to each other. If either one sunsets, nobody notices until someone goes looking for a specific person’s paperwork and can’t find it in either place.
How Long Federal Law Requires You to Keep These Records
Form I-9 is the clearest example, because the rule is specific and the penalties for getting it wrong are real. Federal regulations require employers to keep a Form I-9 for each person they hire for three years after the date of hire, or one year after employment ends, whichever is later, according to USCIS’s Handbook for Employers.
For someone employed for less than two years, that means three years from the hire date. For someone employed longer, it means one year has passed since their last day. Immigration authorities can request these forms with three business days’ notice, so “we’ll track it down eventually” isn’t an option.
I-9 isn’t the only clock running, either. Wage and hour records carry their own separate retention requirement under federal wage law, and equal-opportunity recordkeeping rules add another one on top of that, each with a different agency, a different trigger date, and a different definition of what counts as a covered record. None of them care whether the software where those records used to live is still in business, and none of them pause because a vendor sent a shutdown email instead of a renewal notice.
None of these clocks announce themselves ahead of time. An I-9 audit usually starts with a Notice of Inspection, the same short window described above, not a grace period to find the paperwork. A wage claim or a discrimination charge from a former employee can reach back years, well past the point most people assume old paperwork no longer matters. Nobody gets to schedule when one of these shows up.
What Disappears First When an Account Closes
An export button doesn’t guarantee a usable record. Two details in the FormSwift shutdown process matter here.
First, exporting requires an active paid account. If a subscription lapses or the person who managed it leaves the company, getting the files out means reactivating access before the deadline, not after.
Second, the download link the platform generates expires 14 days after it’s requested. Waiting until the week before a shutdown to start the process leaves no room for a mistake, a missing file, or someone noticing at the last minute that a document is missing a signature page.
Neither detail is unique to FormSwift. Most SaaS platforms build export flows for people leaving on good terms and in no hurry, not for a mass exodus on a hard deadline. And an export often flattens what it hands back: a signed document without the certificate proving who signed it and when, a form without the audit trail showing it was completed the first time correctly. For records that might need to withstand a legal challenge or an audit years later, the flattened version is worth less than what was on file to begin with.
Before the Next Shutdown Notice Arrives
None of this is a reason to panic every time a vendor changes hands. It’s a reason to stop treating export as something that only happens during a crisis.
- Know which vendor holds which record type, and who owns that relationship. IT usually manages the subscription. HR usually owns the compliance obligation. When those two don’t talk to each other, a shutdown notice can sit in an inbox nobody’s watching until the deadline is close.
- Export on a schedule, not only when told to. A quarterly or annual archive pull turns whatever window a vendor gives you into a non-event, because most of what’s needed is already sitting somewhere the company controls.
- Keep the full artifact, not just the form. Signature certificates, audit trails, and timestamps are what make a record defensible later. A flattened PDF of the finished form isn’t the same evidence.
- Store what’s kept as searchable text, not a folder of scans. A record nobody can search is barely better than a record nobody kept. When a retention question comes up years later, someone still has to be able to find the answer without having to read every file by hand.
A vendor’s shutdown timeline and a company’s legal retention timeline are two different clocks, and only one of them cares about the business behind it. The software can disappear on the vendor’s schedule. The obligation to produce what it used to store doesn’t.
