Understanding the topic
A provider migration affects candidate invitations, disclosure and authorization workflows, package design, user permissions, integrations, open orders, billing, reports, disputes, adverse action, retention, and support. Treating it as a simple login replacement can interrupt hiring or carry old configuration problems into the new platform.
The migration is also an opportunity to review whether current packages still match roles and locations. Employers should avoid copying every legacy package, form, user, and exception without understanding why it exists.
What to inventory before migration
The project team needs a reliable picture of the current program and its dependencies.
- Roles, locations, packages, optional searches, client requirements, prices, and third-party fees.
- Disclosure, authorization, state notices, adverse-action templates, and candidate communications.
- Recruiter, manager, administrator, billing, integration, and report-access permissions.
- ATS or HRIS mappings, webhooks, status values, custom fields, and candidate identifiers.
- Open orders, pending disputes, report retention, exports, invoices, credits, and contractual obligations.
A controlled migration sequence
A phased cutover is safer than moving every user and candidate on the same day without reconciliation.
- 1
Establish governance and success criteria
Assign owners for compliance, operations, technology, finance, data, training, and vendor coordination.
- 2
Rationalize the program
Remove obsolete packages and users, verify forms, and resolve unexplained exceptions before configuration.
- 3
Configure and test
Build packages, permissions, integrations, communications, and billing in a non-production or pilot workflow.
- 4
Plan the cutover
Define the last order date, treatment of open candidates, support contacts, data migration, and rollback criteria.
- 5
Reconcile after launch
Compare orders, statuses, invoices, delivery, user access, and candidate issues during a defined stabilization period.
Migration risks to address
Most failures come from hidden dependencies and unclear ownership rather than from the screening search itself.
- Old ATS links or automated workflows continue sending candidates to the former provider.
- Users receive broader report access in the new system than they had before.
- Legacy forms, notices, or packages are copied without legal or operational review.
- Open disputes and adverse-action cases lose their audit trail during the cutover.
- Data exports are kept indefinitely in uncontrolled folders after the migration.
Questions for the new provider
A migration plan should specify what the provider will configure, test, document, and support.
- Which package, user, integration, candidate, and billing data can be imported or configured?
- How will status mappings and corrected reports appear in the ATS or HRIS?
- What training, test cases, implementation support, and escalation contacts are included?
- How are historical reports, audit logs, disputes, and adverse-action records retained or exported?
- What is the plan if an integration or candidate invitation fails during cutover?
Putting the information into a screening program
Do not close the former account until open orders, disputes, invoices, retention needs, data exports, and required access have been reconciled. At the same time, avoid retaining unnecessary duplicate access and data indefinitely.
After launch, review turnaround, candidate completion, errors, disputes, user access, package use, support cases, and invoices. Early metrics help distinguish normal transition volume from configuration defects.
RELATED SERVICES
