How to leave a PEO

First, decide whether to leave

A renewal increase is a prompt to compare, not a reason to go. Put four lines side by side for the coming year: the admin fee, the benefits premiums, the payroll taxes and workers’ comp the PEO prices in, and what it would cost to run the same company on your own HRIS and payroll with benefits through a broker. The four-line comparison is laid out in our renewal guide.

As a rule of thumb, below about 30 people in one state the PEO usually wins on benefits alone. Above 50, or across several states, it usually does not. Three other things start an exit:

• The renewal quote arrived. PEO pricing scales with headcount whether or not the service does.
• An investor asked a question. Co-employment complicates diligence. A data room where the employer of record is somebody else raises questions, better answered before the raise than during it.
• You outgrew the service tier. Attentive support at thirty employees becomes a ticket queue at ninety.

If the comparison says stay, negotiate the admin fee with the numbers in hand. If it says leave, the rest of this guide is the sequence.

What the PEO was doing for you

Under a PEO you were co-employed. That arrangement hid a list of things that now become yours:

• State tax accounts. You paid withholding and unemployment tax under the PEO’s accounts and at the PEO’s unemployment rate. You need your own accounts in every state where you have people.
• Workers’ compensation. Your coverage sat on the PEO’s policy. You need your own policy in force from the first day after the PEO.
• Benefits. Your people were on the PEO’s master plan. You need your own plans through your own broker, with no gap in coverage.
• Payroll and filings. The PEO ran payroll, filed the returns and issued the W-2s. You need a payroll system and someone who owns the filings.
• The employee record. Your HR data lived in the PEO’s system. It has to move, and some of it has to be rebuilt.

Most exits that go wrong miss one of these, usually the registrations, because nobody on your side has opened a state account before.

Set the date

Work backward from the cutover date, not forward from today. Four things set it:

Payroll taxes also run on calendar quarters, which is why January 1 is the cleanest go-live and a quarter start is the fair fallback.

Step 1: Read the contract and pull your data

Before anything else, find three things in the PEO agreement: the notice period and how notice must be given, any early termination fee, and how long you keep access to your data after the contract ends. Access terms after cancellation are rarely what people assume, so agree the export format and the read-only window in writing.

Then pull everything while you still have full access: payroll registers and year-to-date figures, tax filings, benefit elections, time-off balances, garnishments, and employee documents. You will need all of it to load and reconcile the new system.

Do not give notice yet. Notice comes when the registrations and benefits are in hand.

Step 2: Open state registrations first

This is the step that takes longest. In each state where you have employees, you typically need five things:

1. An income tax withholding account, in states that tax wages.
2. An unemployment insurance account. This is the one that carries a rate, and new employers generally receive a standard rate rather than one based on their own history. Check the industry classification you are assigned, because an incorrect code is both common and expensive.
3. Local or city tax accounts, in the minority of places that have them. They are the most commonly missed.
4. Workers’ compensation coverage that meets that state’s rules, including the states that require a state fund policy.
5. Foreign qualification of the entity, where a remote employee triggers it. That one belongs with your counsel.

Most can run in parallel, so the constraint is processing time, not sequence. Treat every published estimate as the optimistic case and never plan a payroll date on the assumption that a number will arrive by then. The state registration guide covers each item and the four traps.

Step 3: Move benefits without a gap

Your broker quotes against your census, you choose the plans, and the new coverage starts the day the PEO coverage ends. Three decisions matter:

• Timing. Move at the plan year if you can. Mid-year moves are possible, but deductibles and out-of-pocket totals may reset for employees, which they notice.
• Retirement. If the PEO sponsored a retirement plan, your own plan has to be set up and the transfer of balances planned with the provider.
• Deductions. Every benefit deduction has to be re-mapped in the new payroll system and checked against the last PEO register before the parallel run.

Get the census, the plan summaries and the renewal history from the PEO early. Brokers cannot quote without them.

Step 4: Build your own HRIS and load the data

Leaving a PEO means running your own system on day one, so the HRIS is built inside the exit, not after it. Sort the data into three buckets before anyone exports a file: what moves as data, what has to be rebuilt, and what stays behind.

People, jobs, compensation, balances and year-to-date payroll move as data, loaded in dependency order with entities and locations first and payroll history last. Permissions, approval chains, workflows and reports have to be rebuilt, because they never transfer between systems.

Year-to-date figures must be cut as of the exact cutover boundary, because a figure taken from the wrong date loads without complaint and fails at the tax cap or at the W-2. HRIS data migration: what moves and what stays has the load order.

If you are still choosing the platform, settle that first. Rippling vs HiBob compares the two we implement.

Step 5: Run one parallel payroll

A parallel run processes one live pay period in both systems. The PEO pays and files as usual. The new system calculates the same period from migrated data and transmits nothing. Then you compare them employee by employee: gross, then deductions, then employer taxes, then net.

Every variance needs an explanation. The standard is explanation, not size. Schedule it two pay periods before cutover so there is room to fix what it finds and run it again, and name three people to sign it off: whoever owns payroll, finance, and the implementation owner. The parallel payroll run, step by step covers what to freeze and which variances are benign.

Step 6: Give notice and tell your people

Give notice once the registrations are issued or far enough along, the benefits are bound, and the parallel run is scheduled. Confirm in writing which payroll is the PEO’s last and who files the final quarter.

Then tell employees before anything changes for them. Three messages cover most of it: when the first paycheck from the new system arrives and what the paystub looks like, what happens to their benefits and when new cards arrive, and where to find old pay stubs and W-2s.

A mid-year exit usually means two W-2s for the year, one from the PEO and one from you, so say so before January. People who know what is coming do not panic when the paystub looks different.

Step 7: Cut over on a pay-period boundary

The last PEO payroll runs. Your first payroll runs on the next period, on the new system, previewed against the parallel run before it is submitted, with a named person confirming that deposits land on payday. Then for the first month: audit the first invoices, confirm the first filings went to the right accounts, and close the punch list.

What it costs

The comparison that started the exit already holds most of the numbers: your own HRIS and payroll software at the vendor’s price, your own benefits through a broker, your own unemployment and workers’ comp rates, and whoever runs the work afterwards. Add the project itself.

We run PEO exits as a fixed-scope project with the HRIS implementation built in, priced from $55k all-in for one entity and up to three states. Extra entities, more states, more carriers, prior years of data or custom integrations are quoted in writing. Every price band is on our pricing page.

Where PEO exits go wrong

• Giving notice before the registrations are open. The contract clock starts and the state clock does not care.
• Assuming the platform opens your state accounts. Some platforms file once you are registered. Fewer open the registrations themselves. Establish which items are yours, in writing.
• A benefits gap. New coverage that starts the day after the old coverage ends is a decision, not a default. Confirm the dates with the broker and the carrier.
• Year-to-date cut at the wrong date. It loads cleanly and fails at the W-2.
• No parallel run. Making the first live payroll the test is the most expensive way to find a mapping error.

On one page

1. Compare before you decide. Four lines, not one.
2. Count back from the date you want.
3. Pull the contract terms and all your data while you have access.
4. Open state registrations first.
5. Bind benefits so new coverage starts the day the old one ends.
6. Build the HRIS and load the data, with year-to-date cut at the boundary.
7. Run one parallel payroll two periods before cutover.
8. Give notice, tell your people, and cut over on a pay-period boundary.

If you want the sequence mapped against your own contract, states and plan year, start with the free HR Systems Review, or book a 20 minute call.

This is practitioner guidance, not tax, legal or benefits advice. Your tax advisor, counsel and broker own those decisions.