SPREADSHEET-TO-ATS MIGRATION CHECKLIST
TiLab planning resource - adapt to your organization and chosen system.
This checklist is not an import specification or a promise of an available importer.

Business owner:
Migration owner:
Chosen system and package:
Confirmed transfer method:
Pilot role:
Target cutover date:

PREPARE
[ ] Name the business owner and the person responsible for each transfer step.
[ ] Keep a recoverable untouched source copy with its observation date.
[ ] List included roles and applications; explain exclusions and unresolved records.
[ ] Confirm operator limits, active-job limits, accepted fields, and any transfer assistance.
[ ] Review which data is appropriate to transfer under the organization's data-handling process.
[ ] Map source candidate IDs and application IDs separately.
[ ] Map jobs, stages, dates, source labels, and intended owners explicitly.
[ ] Define how missing values, conflicting duplicates, and unknown labels will be handled.

REHEARSE
[ ] Use synthetic records before real candidate information.
[ ] Check one person with applications to two different roles.
[ ] Confirm candidate and application counts separately.
[ ] Check job and stage assignments against the field map.
[ ] Check representative dates, including the source timezone and midnight boundaries.
[ ] Verify intended access and an excluded-user case using test accounts.
[ ] Document discrepancies and resolve material mapping issues.

PILOT
[ ] Obtain the required internal approval for the agreed pilot scope.
[ ] Transfer the small agreed dataset using the confirmed method.
[ ] Reconcile counts and representative details against the source.
[ ] Ask a future operator to complete a review, handoff, and recorded decision.
[ ] Log limitations and agree the next action for each exception.

CUT OVER
[ ] Agree a source-edit freeze and account for changes after the source copy.
[ ] Identify which system is authoritative during and after the move.
[ ] Rehearse when to pause and how to recover without duplicate candidate communications.
[ ] Transfer only the approved scope.
[ ] Reconcile counts, identities, jobs, stages, dates, and ownership.
[ ] Obtain business-owner acceptance before moving new work to the destination.
[ ] Tell operators where to manage new applications and whom to contact for an exception.

STABILIZE
[ ] Review open actions and resolve or explicitly accept remaining exceptions.
[ ] Keep the mapping, crosswalk, and reconciliation notes with operational documentation.
[ ] Confirm the source archive and retention process with the internal policy owner.
[ ] Record the first workflow review and the owner of any follow-up changes.

Outstanding exceptions and owners:

Business-owner sign-off and date:

Resource: https://talentintelligences.com/resources/spreadsheet-to-ats-migration-kit