ATS Implementation Guide 2026: How to Go Live Without Losing Three Months

What ATS implementation actually involves

ATS implementation is not a single event, it is a sequence of decisions and configurations that collectively determine whether the platform works for your team or becomes another system people work around. Understanding what each component involves helps you plan properly and set realistic expectations with your team and leadership.

The six components of any ATS implementation are: data migration, configuration, integrations, team training, testing, and go-live. The time required for each component varies by platform type and company complexity, but the sequence is the same regardless of which platform you choose.

Data migration

Moving candidate records, historical job data, and any pipeline history from your old system into the new ATS. This is typically the most variable component, ranging from a few hours for a company switching from spreadsheets, to weeks of work for companies with years of structured candidate data in a complex ATS. Most migrations involve: exporting raw data from the old system, mapping fields to the new system's schema, cleaning and de-duplicating records, and importing in batches with validation checks.

Configuration

Setting up the ATS to match your hiring process rather than a generic default. This includes defining pipeline stages, creating job templates, configuring approval workflows, setting up scoring criteria, building email templates, and customising the application form. Well-designed self-serve ATS platforms can be configured in a few hours by an HR professional with no technical background. Complex enterprise configurations, particularly those with multi-team approval workflows, custom DEI reporting, and compliance automation, can take days to weeks.

Integrations

Connecting the ATS to the other systems in your HR technology stack: your HRIS, calendar and scheduling tools, Slack for notifications, LinkedIn for job posting and sourcing, background check providers, and your career page. Each integration requires both-sides access, testing, and validation. The number of integrations is the primary driver of implementation timeline variation for mid-market ATS platforms.

Team training

Getting recruiters, HR generalists, and hiring managers comfortable enough with the new system to use it correctly without supervision. Self-serve platforms with intuitive UX can be trained in a 30-60 minute session per user type. Complex enterprise platforms may require structured training programmes for different user types, with separate sessions for recruiters, hiring managers, and system administrators.

Testing and go-live

Running test job postings, submitting test applications, verifying integrations, and walking through the full hiring workflow end-to-end before going live with a real role. A proper pre-launch test takes 2-4 hours but saves significantly more time in production troubleshooting. Most implementations that go wrong do so because testing was skipped or rushed under pressure from a hiring deadline.

Plan the implementation from scope, not a vendor category

A useful timeline starts with release decisions, not with a generic promise about how long an ATS should take. Set separate readiness gates for the core workflow, active candidates, historical records, integrations, and organisational rollout. This makes dependencies visible and gives the team a way to release useful work before every long-tail requirement is complete.

A rollout plan for organisations with 50+ locations

Multi-location teams should normally avoid making every location the first production test. Choose a pilot location or role family that represents the normal workflow, make the operating standard explicit, then roll out in waves once the pilot has passed its acceptance checks.

1. Define the shared operating standard

Agree which parts of the hiring process are genuinely common: requisition data, application questions, pipeline stages, scorecards, approval paths, communications, and reporting fields. Record local legal, language, brand, or hiring-manager variations separately so they do not turn into undocumented exceptions during rollout.

2. Run a controlled pilot

Use one location or role family to test the complete path from a job opening to a hiring decision. Include a test applicant, hiring-manager feedback, calendar or scheduling handoff, candidate communication, permissions, and reporting. The pilot is complete only when the owners can explain how exceptions are handled, not merely when the configuration screen is populated.

3. Decide active-candidate migration by owner

Assign responsibility by job, department, or location before cutover. Greenhouse's public migration guidance uses this type of active-candidate decision and distinguishes it from historical migration. Keep the scope small enough to verify with a representative import and retain the old system until the migration owner and compliance owner have signed off.

4. Release in waves, then stabilise

Group locations by similar workflow and readiness rather than by an arbitrary calendar date. Between waves, capture defects, training questions, and integration gaps; update the operating standard; and confirm that new requisitions, candidate communications, and reporting are working. Only then schedule the next group.

Data migration guide

Data migration is where most ATS implementations encounter the first unexpected complexity. Here is what to expect:

What migrates cleanly

• Active candidate records: name, email, phone, applied role, current pipeline stage
• Historical job postings: title, description, dates, locations
• Basic application data: CV files, cover letters, application form responses
• Hired candidate records: names and roles (useful for reporting continuity)

What requires manual work

• Interview notes and scorecards: often stored in formats specific to the old ATS that do not map cleanly to the new system's schema
• Custom field data: fields you created in the old system need to be mapped to equivalent fields in the new system, or created as new custom fields
• Email correspondence history: most ATS platforms do not export email threads in a portable format
• Offer details and compensation data: typically requires manual review to verify accuracy during import

What you typically lose

• Internal tags, labels, and flags specific to the old platform's data model
• Automated workflow history (which emails were sent, when, to whom)
• Integration-specific data from connected systems
• Candidate experience metrics (email open rates, application completion times)

Practical preparation advice

Run a full data export from your current ATS before cancelling the contract. Agree a written retention and import scope that separates active candidates, records needed for reporting or candidate service, and archive-only data. Test a representative sample, then sign off which fields, attachments, notes, and documents will be retained, transformed, or excluded. Keep the original export securely until the operating and compliance owners approve retirement of the old system.

Configuration checklist

The following configuration should be complete before your first live job posting in the new ATS:

Pipeline and process

• ☐ Pipeline stages defined (recommended: Applied, Screening, Phone Interview, Assessment, Final Interview, Offer, Hired, Rejected)
• ☐ Disqualification reasons configured for each stage
• ☐ Automated stage-move notifications enabled
• ☐ Approval workflow set up if required (job posting approval, offer approval)

Job templates and forms

• ☐ Job templates created for your 3-5 most common role types
• ☐ Application form configured (required vs optional fields; GDPR consent if applicable)
• ☐ Standard screening questions for each role type
• ☐ Scorecard templates for structured interviewing

Career page and branding

• ☐ Career page domain set up (or embedded widget configured on your website)
• ☐ Company logo and branding applied
• ☐ Company description and culture content added

Team and permissions

• ☐ All recruiter and HR accounts created with appropriate permissions
• ☐ Hiring manager accounts created
• ☐ External collaborator accounts set up if applicable

Email templates

• ☐ Application acknowledgement email
• ☐ Interview invitation email
• ☐ Rejection email (at screening stage and post-interview)
• ☐ Offer email template

Integration setup

Integrations are the most technically variable part of ATS implementation. Prioritise them by impact on your daily workflow:

Priority 1: Configure before go-live

Job board connections: LinkedIn job posting integration, your primary paid job board (Indeed, Glassdoor, etc.), and your career page. Without these, you cannot post jobs from the ATS, defeating much of the purpose of the platform.

Calendar/scheduling: Google Calendar or Outlook integration for interview scheduling. This single integration saves the most recruiter time per day, eliminating the back-and-forth scheduling email chain is immediately visible and appreciated by the whole team. Calendly integration is an effective alternative if your calendar integration requires IT involvement.

Priority 2: Configure in first two weeks

HRIS integration: Connecting your ATS to your HRIS so hired candidates flow automatically into HR records. If you are using Treegarden's ATS+HR bundle, this is not an integration, it is a native data flow within the same platform, requiring no configuration.

Communication tools: Slack integration for hiring team notifications when candidates move stages or new applications arrive. Reduces the need for recruiters to constantly check the ATS dashboard throughout the day.

Priority 3: Configure after go-live

Background check providers: Checkr, Sterling, or your preferred provider. Important for roles requiring background screening but not blocking for go-live since these are triggered manually per candidate.

LinkedIn Recruiter: If your team uses LinkedIn Recruiter for sourcing, the ATS-to-Recruiter integration syncs candidate data and reduces duplicate entry. Valuable but not urgent for initial go-live.

Go-live checklist and first 30-day plan

Before announcing go-live to your hiring managers, verify the following:

• ☐ Test application submitted and received correctly in the ATS
• ☐ Acknowledgement email delivered correctly (check spam folder with a personal email address)
• ☐ Career page loading correctly with at least one live job
• ☐ Calendar integration tested by scheduling a test interview
• ☐ All team members have logged in and confirmed access
• ☐ At least one hiring manager has been walked through their view
• ☐ Data export from old ATS downloaded and stored securely

First 30 days after go-live

The first 30 days are about building habits, not adding features. Resist the urge to configure everything immediately, focus on getting your team comfortable with the core pipeline management workflow before adding integrations, automations, and advanced reporting.

Week 1: All new jobs posted in the new ATS only. Old ATS maintained for active applications already in pipeline.

Week 2: First hiring manager interview scheduled through the new ATS's scheduling integration. First rejection emails sent from the new ATS. Team feedback session, what is working, what is confusing.

Week 3-4: HRIS integration configured if not already done. Sourcing integrations added. First reporting pull to establish baseline metrics.

Day 30: Review whether the old ATS can be retired. Confirm that active candidates, reporting obligations, retention requirements, and outstanding integrations have named owners before ending access.

Frequently asked questions

How long does ATS implementation take?

ATS implementation does not have a universal duration. Build a project plan after deciding launch scope, data migration, integrations, user permissions, and training. A pilot can begin before historical migration finishes, but a multi-location rollout needs its own test and change-management checkpoints. Treat any estimate as a planning input, not a committed go-live date.

What data can I migrate from my old ATS?

Start with a written field map and a representative test import. Active candidate contact details, jobs, application status, and selected documents are common candidates for migration, but availability depends on each system. Verify what the export includes and whether attachments, notes, scorecards, consent records, and custom fields can transfer.

Can I implement a new ATS while hiring is actively in progress?

Yes. Decide in advance how active candidates will be routed, who owns each migration wave, and when new requisitions begin in the new system. Keep the old system available through the pilot and end-to-end checks, then decommission it only when operating and compliance owners agree.

What configuration is required before going live?

Before go-live, document a minimum viable workflow: requisitions, pipeline stages, candidate communications, permissions, career page, hiring-manager access, and any integration that is needed to recruit. Test each handoff with a real scenario and defer non-essential reporting, automation, or integration work to a controlled post-launch backlog.