# Moving off an enterprise suite at 300 people

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** A 300-person company leaving Workday, ADP, Paylocity or a Rippling suite plans a quarter, not a month: the exit terms are in the contract, payroll and finance have their own migrations, and the security groups and business processes have to be rewritten as roles and workflows. Decide where payroll goes first; everything else follows from that.

## Why a quarter

The calculator's Workday to Shapes example at 800 people is 340 People hours and seven weeks before the enterprise agreement's notice period is added; at 300 people the hours fall and the notice does not. Workday publishes export tooling through the term and no notice period; ADP and Paylocity publish neither; Rippling's terms sit behind a login. The ledger grades Workday C and the other three D, and the first task in each case is the written request for the contract's dates.

## Payroll first

A suite ran payroll natively. The company decides between a destination that runs it (Rippling, HiBob for US and UK, Personio for Germany, Gusto for the US) and a destination that connects to a provider (Shapes with any of its seven live payroll systems: Papershift, Hilan, Xero, Papaya Global, Deel, Remote or ADP). The first choice adds a parallel payroll month; the second adds a provider selection and a connector test. Both are on the parallel payroll guide.

## Security groups and business processes

Workday's security groups and business processes, ADP's and Paylocity's module permissions, and Rippling's attribute-keyed policies become roles and workflows in the destination. Count them before signing: a workflow nobody can describe cannot be rebuilt, and the guide on migrating sixty workflows on the network's onboarding site is the companion to this one. Shapes holds unlimited roles on Plus with up to five filters each and drafts workflows from a sentence; Humaans holds unlimited roles on Enterprise; HiBob configures permissions by group.

## The order of the quarter

- Month one: the contract's dates in writing; exports started with the platform team; payroll decided; the field map.
- Month two: the import into a sandbox; roles and workflows rebuilt; the ATS and identity re-pointed; the parallel payroll month if payroll moves.
- Month three: cutover at a quarter end; the finance migration continues on its own track; the old suite read-only until the retention window closes.

## Sources

- Workday Launch: https://www.workday.com/en-us/customer-experience/deployment.html (read 8 Nov 2026)
- Workday export and deletion: https://www.workday.com/en-us/why-workday/trust/privacy.html (read 8 Nov 2026)
- Shapes roles and entities by plan: https://shapes.co/pricing (read 8 Nov 2026)
- Rippling pricing: https://www.rippling.com/pricing (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://hrisalternatives.com/guides/moving-off-an-enterprise-suite-at-300-people/
