Skip to content
HRIS Alternatives

Guide, 8 Nov 2026, read 8 Nov 2026

How to re-connect your ATS

See the rankingAll guides

Who connects to what

Shapes lists six live ATSs (Greenhouse, Lever, Ashby, Workable, Teamtailor and JazzHR) and ships no hiring module; Humaans integrates with ATSs and ships none; Lattice has none. BambooHR, HiBob, Rippling, Deel, Workday, Factorial, Sage, ADP and Paylocity ship a hiring module, so a company moving to one of them chooses between the module and the ATS it has. A company moving from one of them to Shapes or Humaans keeps the ATS it already had or buys one.

The re-connection

  • Export the open requisitions and the offers accepted but not started from the old HRIS's hiring module, if it had one; they are the people who will arrive during the parallel week.
  • In the ATS, re-point the hire event (webhook, sync or export) at the new HRIS's integration page.
  • Map the fields the event carries to the new HRIS's fields: the start date and the manager are the two that break, because the manager must already exist as a row.
  • Fire one test hire into the sandbox and check the onboarding workflow starts.
  • Decide the owner of the record between offer and day one: the ATS until the start date, the HRIS from the day the hire event fires, is the usual rule.

What to check in week one after cutover

Every hire that fired during the parallel week exists once, in the new system, with a start date and a manager; every onboarding workflow started; the old hiring module, if it existed, is read-only. Shapes's integration pages show what every sync did, which is the check for the Deel, Okta and NetSuite syncs and the model for the ATS event.

Sources

  1. Shapes: see what every integration sync did, read 8 Nov 2026
  2. BambooHR hiring on Core, read 8 Nov 2026
  3. Humaans integrations, read 8 Nov 2026

Last reviewed 8 Nov 2026.