How to leave Rippling cleanly

Leaving Rippling is less about the export button and more about untangling where your data lives. Rippling sells HR, IT and finance as connected modules, so your people records, device assignments, and spend or payroll data all reference the same employees from different places. Get a clean copy of each while the account is active, work from a map of which module holds what, then rebuild your HR system of record in the replacement. One honest caveat up front: if you depend on device management and app provisioning, that breadth is real, and a pure HRIS will not cover it.

Why the untangling matters first

Most HR tools hold one pile of data. A bundled platform holds several that overlap, because the whole pitch is that HR, IT and finance sit together. That is convenient while you are in it and awkward when you leave, because “an employee” is not a single record. The same person appears in the HR module as a hire, in the IT module as a set of device and app assignments, and possibly in the finance module as a spend or payroll entry.

So the first task is not exporting. It is listing every module you actually use and deciding, for each, whether the data is HR (moves to your new system of record), IT (needs a dedicated tool), or finance (goes to your accounting or payroll stack). Skip this and you will migrate the directory cleanly while leaving your real offboarding process, half of which was IT provisioning, stranded in a tool you just cancelled.

The export checklist

Run this while the account is live and paid, because access to reports ends with billing in every tool.

1. Employee directory. Export the full list of people in a spreadsheet, with status, role, country, start date, and manager. This is your master index for everything that follows.
2. Documents. Contracts, offer letters, tax and identity documents, and any signed forms held against each profile. Save them under a consistent naming scheme by person, since a vendor’s internal filing does not survive the move.
3. Leave and time data. Current balances, accrual policies, and any historical time-off records you need for continuity. Balances in particular have to carry over accurately or your first month on the new tool starts with disputes.
4. Payroll and finance history. If you run payroll or spend through the platform, export the historical records at the level of detail your accountant needs. Reconcile against your books before you move.
5. IT and device records. Export the inventory of who holds which device and which app access each person has. Even if a new HRIS will not manage these, the record is your handover to whatever IT tool takes over, and your evidence for the next offboarding.
6. Onboarding and offboarding workflows. Write down the automations you rely on before you lose sight of them. Much of what feels automatic in a bundled platform is a workflow that spans modules, and you will want to rebuild the HR parts and reassign the IT parts deliberately.

Where it tends to be hard

The tangle is the hard part. A single export rarely captures everything when the data is spread by design, so completeness depends on your module map rather than on one download. Device management is the other sticking point: those records describe physical laptops and live software access, and moving means deciding what actually manages those going forward, not just where the spreadsheet lives. Finally, cross-module workflows hide dependencies, so an offboarding you thought was one process is often three, and pulling one thread can quietly break the others.

Standing up the replacement

Once the data is out and checked, rebuilding the HR system of record is quick with a tool that imports open formats. What that rebuild involves in full is a checklist of its own, so use it to stand the new system up and read the steps below as the parts particular to untangling Rippling.

1. Import the directory so every person exists in one place again, employees and contractors together.
2. Re-file documents against each record so everyone carries their own paper trail.
3. Rebuild leave policies and load balances from the figures you exported, and check a few people by hand before trusting the whole set. Expect this to be manual: most tools import employees well and almost nothing else, so ask specifically what can be loaded from a file and plan the rest as data entry.
4. Route IT and finance to the right homes. Hand device and app management to a dedicated IT tool, and point payroll and spend at your accounting stack. Your HRIS should hold the people truth, not pretend to be an IT department.
5. Confirm the exit before you commit. Check what the new tool hands you on the day you leave, in what container, and whether the export still works when billing lapses. Capstan’s export is a plain archive of documented JSON, a matching CSV and your original document files, with a manifest whose row counts you can check the archive against, and it sits outside the billing check on purpose. Its pricing is published rather than quoted, and the core product is free up to twenty active employees.

Who should stay on Rippling

Be fair about the breadth. If you are deep in device management and app provisioning, that is genuine capability, and a pure HRIS does not replace it. Locking a laptop and cutting software access the moment someone is offboarded is real value if your security posture depends on it.

The question is whether you are paying for the whole platform to use one strong part of it. If IT provisioning is the thing keeping you there, the honest move may be to run a dedicated IT tool for that and take your HR system of record somewhere cheaper and transparent, rather than buying the entire bundle to get one module. If you are still deciding what belongs in your HRIS versus a broader suite, the difference between HRIS, HRMS and HCM is worth reading, and the wider startup HR guide covers what your system of record has to do on its own.