Greenhouse Migration Checklist for SMB Recruiters (Before You Switch ATS)

ATS migrations fail less because of software and more because of unplanned process changes. This checklist helps SMB teams evaluate migration readiness before committing budget and timeline.

If you're comparing options first, refer to this guide on alternatives to Greenhouse for SMB and agency hiring teams.

Pre-migration checklist

Process mapping

define current workflow stages
document approval bottlenecks
decide what to standardize vs customize

Data readiness

candidate record cleanup
job template cleanup
duplicate pipeline removal

Integration dependencies

calendar/video tools
sourcing platforms
assessment providers
reporting exports

Success criteria

target time-to-shortlist
recruiter admin time reduction
hiring manager feedback SLA compliance

30-day transition plan

sandbox workflow testing
pilot with one live role family
rollback safety plan
team onboarding and job aids

Frequent migration mistakes

copying legacy process complexity as-is
over-customizing too early
no owner for data validation
weak hiring manager training

Final takeaway

Switching ATS should be treated like an operations redesign, not a tool swap.

Migration readiness questions before kickoff

Which workflows are non-negotiable for your team?
Which reports are used weekly in hiring decisions?
Which integrations break critical recruiter actions if unavailable?
Which historical data must be migrated vs archived?

If your team cannot answer these upfront, migration risk is high regardless of platform.

Day-0 to Day-30 owner matrix

Recruitment ops: workflow design + permission model
Recruiter lead: template and stage usability review
Hiring manager lead: feedback SLA and scorecard adoption
Tech/admin owner: integration checks and data validation

Assigning explicit owners avoids the most common SMB migration failure: everyone assumes someone else is handling a key dependency.

Migration cost model (what teams miss)

Most SMB teams budget only for license cost and underestimate transition cost. Build your migration budget with:

platform subscription
migration/setup support fees
recruiter retraining hours
hiring manager retraining hours
temporary productivity dip during cutover

A tool that is cheaper on paper can still cost more if adoption takes longer and pipeline velocity drops.

Pre-migration data audit checklist

Before importing anything:

remove duplicate candidates
normalize stage names across open requisitions
archive dead pipelines
clean custom fields no one uses
verify source attribution consistency

Dirty data imported into a new ATS creates immediate reporting noise and weak trust in the system.

Cutover playbook (safe rollout)

Phase 1: Parallel readiness (Week 1)

configure core pipelines
map candidate statuses
test integrations in sandbox

Phase 2: Pilot migration (Week 2)

run one live role family end-to-end
compare speed and reporting quality vs old system

Phase 3: Controlled go-live (Week 3)

migrate active roles in sequence
keep rollback path for one week

Phase 4: Stabilization (Week 4)

measure SLA compliance and stage aging
patch workflow friction points

This phased approach reduces operational shock and avoids "big bang" failures.

Roles and ownership matrix (expanded)

Recruitment Ops: workflow architecture, data rules, governance
Recruiter lead: usability validation and training adoption
Hiring manager lead: scorecard and feedback compliance
IT/admin: integration stability and access controls
Leadership sponsor: decision escalation and policy enforcement

Without leadership sponsorship, migration decisions tend to stall when teams hit friction.

KPI set for migration success

Track before vs after:

time-to-shortlist
time-to-interview scheduling
feedback SLA compliance
recruiter admin hours per requisition
report accuracy confidence score (internal)

If these metrics do not improve within 30-45 days, your migration is not complete.

Common failure patterns

over-customization before team basics are stable
no standardized interview scorecards
missing fallback process for integration outages
weak stakeholder training after go-live

Fix order matters: stabilize workflow first, optimize advanced features second.

Final recommendation

Run ATS migration as an operations program with measurable outcomes, not a software implementation project. Teams that treat it this way achieve faster adoption and better recruiting performance.

Migration risk register template

Track these risk categories during rollout:

data integrity risk
integration compatibility risk
user adoption risk
reporting continuity risk
hiring velocity disruption risk

For each risk, define:

likelihood
impact
owner
mitigation action
review cadence

This gives leadership visibility beyond project status updates.

Post-migration stabilization checklist (first 2 weeks)

verify all active requisitions map to correct stages
audit candidate status history for migrated records
confirm interview scheduling sync accuracy
validate scorecard completion behavior
compare weekly funnel report against live workflow

Most migration failures appear in this window, not during demo testing.

Leadership sign-off criteria

Do not declare migration complete until:

recruiter adoption crosses target threshold
SLA performance returns to baseline or better
reporting accuracy is validated in two consecutive cycles
no Sev-1 integration incidents remain unresolved

This prevents "premature completion" declarations that hide operational regressions.

Migration communications plan (internal)

Send structured updates to stakeholders:

weekly project status
upcoming workflow changes
known issues and temporary workarounds
expected impact windows

Clear communications reduce user frustration and increase adoption confidence.

Training plan by audience

Recruiters

pipeline operations
scorecard discipline
reporting basics

Hiring managers

feedback SLA behavior
debrief expectations
decision documentation standards

Admin/ops owners

integration monitoring
incident handling
data governance

Target role-specific training instead of one generic session.

Post-go-live performance guardrails

Set minimum acceptable thresholds:

feedback SLA compliance >= target baseline
no critical integration outages over defined period
stage aging within normal operating range
candidate communication lag below agreed maximum

If thresholds are missed, trigger stabilization sprint before expanding advanced features.

90-day optimization cycle

At 90 days, review:

which migrated workflows improved cycle time
where admin burden increased
where hiring manager adoption lags
which automation changes are needed

Then implement targeted process refinements rather than broad reconfiguration.

Final migration rule

A successful ATS migration is measured by sustained operational improvement, not just go-live completion. Keep measuring until workflow stability and decision quality are both proven.

Executive summary template (post-migration)

Share this one-page summary after stabilization:

baseline vs current time-to-shortlist
baseline vs current feedback SLA compliance
major incidents and resolution status
adoption coverage by stakeholder group
next 30-day optimization priorities

This gives leadership a clear signal that migration outcomes are being measured and managed, not assumed.

Final success indicators

Declare "migration complete" only when all are true:

users rely on new workflows without fallback spreadsheets
reporting confidence is stable across two consecutive cycles
recruiter admin burden does not exceed pre-migration baseline
hiring manager compliance is sustained without manual chasing

These indicators are the most practical proof that migration delivered value, not just technical completion.