Switching guide
Leaving Gusto without losing your records
By the Capstan team at PeopleCap · Last updated 17 August 2026 · About 6 min read
Leaving a payroll provider is mostly a timing and export exercise, not a technical one. Get your records out in open formats, move at a clean payroll boundary, and confirm your year-end tax forms are filed before you close the account. Do those three things and the switch is calm rather than fraught.
This guide covers what to export, when to move, and the one honest question worth asking before you go: whether a startup HRIS with partner-integration payroll is actually the right shape for you.
What to export before you close the account
There are four kinds of data you cannot afford to lose. Pull all of it while the account is still active and billing, because read access to filed documents narrows once you cancel, and support is slower for a former customer.
- Employee records. Names, contact details, start dates, job titles, compensation history, tax withholding elections, and bank details where you are permitted to hold them. Export the employee roster and any custom fields you added.
- Documents. Signed offer letters, policy acknowledgements, direct-deposit forms, and anything uploaded to each person’s profile. Check whether these come out in bulk or one at a time before you plan the work; per-employee downloads are common and they set the timeline.
- Pay history. Pay stubs for every employee, the payroll journal for each run, and year-to-date summaries. Get these as both PDFs and CSVs.
- Tax documents. Every form and return filed on your behalf. These are the hardest to recreate after the fact, so treat them as the priority and confirm you hold a copy of each before anything else happens.
Store the lot in a dated folder you control, not only inside the next tool. Records you own are records nobody can revoke.
Timing the move around payroll and year-end
The two boundaries that matter are the pay cycle and the tax year.
Move at the end of a completed pay run, never in the middle of one. If you switch mid-period, you split a single pay cycle across two systems and then have to reconcile hours, deductions, and taxes by hand. A month boundary is cleaner than a mid-month one, and a quarter boundary is cleaner still.
Year-end is the bigger constraint, because annual filings are produced from the payroll that was actually run. If you leave part way through a tax year, you either wait for your outgoing provider to complete the filings for the period it handled, or you take on reconciling a split year across two providers. The simplest path is to let the current provider finish the tax year, download everything, and start the new system from a clean year boundary. If you cannot wait, agree in writing which provider files what, and for which period, before you cancel anything. Do not leave that as an assumption; it is the single most expensive thing to get wrong here.
How to move
Payroll timing shapes the order below, but it sits on top of the general sequence rather than replacing it. Use the standard checklist to stand the new system up, and read what follows as the payroll-specific overlay.
- Export everything above and confirm the files open and read correctly. A CSV that will not parse is not a backup.
- Set up your people in the new system in parallel, while the old one is still live. Load the directory, documents, and leave balances, and check a handful of records against the originals.
- Run one cycle in overlap if you can. Keeping both systems live for a single period lets you compare outputs before you commit. It costs one extra month of subscription and buys you certainty.
- Point your payroll partner at the new inputs. With Capstan, you compile the payroll inputs in the HRIS and hand a documented export to your payroll partner, who computes gross-to-net and handles the filings. Their results come back as a file Capstan reconciles line by line before storing. Confirm the first export matches what the old system would have produced.
- Cancel only after the first clean cycle in the new system and after your final tax forms are filed and downloaded.
The payroll module explains the partner-integration model in full, and the Gusto comparison sets out where the two products differ in scope.
Who should stay where they are
This is the honest part. A dedicated payroll provider is strong at what it is built for. If you are a single-country small business whose core need is running payroll, administering benefits, and filing taxes in one self-contained tool, that product runs the payroll itself and owns the filings, which is exactly what you want when payroll is the centre of your operation.
A startup HRIS that hands payroll to a partner is a different shape, and it is worth being precise about it rather than blurring the difference. Capstan computes no statutory payroll of any kind, in any country. It holds no rate, slab, bracket, threshold or formula, and that absence is structural rather than a gap awaiting a release. What it does is compile the inputs, export them in a documented format, and file the partner’s returned results and payslips back onto each record, with a reconciliation that refuses a results file whose totals do not add up rather than importing half of it. That model suits teams whose priority is the system of record, who operate across more than one country, or who already have a payroll partner they trust. It is not a like-for-like swap for a self-contained payroll engine, and pretending otherwise would waste your time.
So the deciding question is simple. If payroll and tax filing are the whole job, staying with a payroll product is a reasonable answer. If the job is a clean, portable system of record for a small or cross-border team, with payroll handed to a partner, that is where a startup HRIS earns its place.
Where to go next
If you operate in India, the statutory payroll guide sets out the partner model in detail, including exactly what crosses the line in each direction. For the wider picture of what a small team actually needs, the HR software for startups guide is the place to start. When you are ready to price it, the pricing page is public and complete: the core is free up to twenty active employees, paid plans raise that limit and are what let you switch a module on, and prices are adjusted by country. Check the current pricing on both sides before you decide.
Common questions
When is the best time to leave a payroll provider?
After a completed pay run and, ideally, after the year-end tax forms for the current year have been filed. Moving mid-cycle means you carry a partial pay period across two systems, which is the one situation guaranteed to create a reconciliation headache. Wait for a clean boundary, and agree in writing which provider files what for which period before you cancel anything.
What payroll records should I take before closing an account?
Pay stubs for every employee, the payroll journal for each run, year-to-date summaries, and every filed tax form and return submitted on your behalf. Take them as PDFs for the human-readable record and as CSVs for the next system to ingest, and check each file opens before you rely on it. Keep your own dated copy regardless of what the new system holds, because records you control are records nobody can revoke.
Does Capstan replace Gusto payroll?
Not directly, and the difference matters enough to weigh honestly. A payroll provider computes gross-to-net and files the returns itself. Capstan works in partner-integration mode: it compiles the payroll inputs, hands a documented export to your payroll partner, and files the returned results and payslips back onto each employee record. It holds no tax rate, slab or formula and files nothing with any authority. If self-contained payroll and tax filing are the whole job, that is a different product shape.