Changing Your ATS Provider: A Practical Evaluation Guide
Moving to a new applicant tracking system is a business change, not just a software purchase.
The useful question is not which ATS has the longest feature list, but which one removes the specific bottlenecks your team can name. This guide turns that question into a checklist you can use in demos, reference calls and contract reviews.
Start with the failure you are leaving behind
A vendor switch usually begins with a symptom: search feels slow, a job board no longer syncs, or recruiters keep a shadow spreadsheet because the pipeline view does not match how they work. Symptoms are useful signals, but they are not yet a brief. Turn each one into a testable statement about the current system, then decide whether the cause is the software, the configuration, or the process around it.
A simple way to do this is to write a one-page exit memo. List the three to five moments in a typical week where the current ATS costs the team time, money or candidate goodwill. For each moment, note what a better system would need to do differently. That memo becomes the yardstick for every demo and reference call, and it stops the evaluation from drifting toward whichever vendor tells the best story.
Separate business needs from attractive extras
Feature lists are designed to impress, and that is exactly why they are a poor starting point. A more reliable method is to write requirements as scenarios. For example, "a contract recruiter can submit a candidate to a client without leaving the ATS" is a need if submissions are the core of your revenue. "The dashboard can be themed to match our brand" is a want unless client-facing presentation is part of the service you sell.
Score each scenario on two axes: how often it happens in a normal week, and what breaks if it is unavailable. High-frequency, high-impact scenarios belong on the shortlist criteria. Low-frequency, low-impact items belong on a tie-breaker list. This keeps the evaluation anchored to the work rather than to the demo.
Check the feature set against current practice
Recruitment technology moves quickly, and a feature that was optional two years ago can now be table stakes. Cloud delivery, AI-assisted matching, structured data metrics and skills assessment all appear in current market conversations. The practical question is not whether a vendor mentions them, but whether the version you would buy supports the workflow your team runs today and expects to run next year.
Ask for a live walkthrough using one of your own open roles. Watch where the vendor's team hesitates or reaches for a workaround. A native feature that fits the process is worth more than a longer feature list that requires manual steps to deliver the same outcome.
Use references and reviews as evidence, not decoration
Reviews and peer referrals are most useful when you read them for patterns rather than for verdicts. Look for repeated comments about the same themes: how quickly support responds, how clean the migration was, and whether recruiters actually adopted the system after go-live. A single enthusiastic review and a single frustrated review are both anecdotes; a cluster of similar comments is a signal.
When you speak to a reference, ask about the first month after go-live rather than the sales process. That is usually when configuration gaps, data issues and training shortfalls surface. Ask what they would do differently if they were switching again, and listen for whether the answer is about the software or about their own preparation.
Plan setup and configuration before signing
Setup is where optimistic timelines meet real work. Ask for a written sequence covering demos, configuration, testing and go-live, with a named owner on each side for every step. Ask what happens if a step slips, and who decides whether a configuration choice is in scope or a change request.
A shared project board is a reasonable expectation because it gives both teams one place to record decisions and open questions. Without that record, small configuration choices can turn into disputes later. Treat the setup plan as part of the contract, not as a courtesy document.
Treat data migration as a contract term
Candidate and client records are the operating memory of a recruitment agency. A migration that loses notes, attachments or history damages relationships that took years to build. Ask the vendor to describe what will be migrated, what will be transformed, what will be excluded and how exceptions will be handled. Get that description in writing before signing.
Also ask what happens if you leave the vendor later. You need to know how you can retrieve your own client and candidate information. A vendor that cannot answer that question clearly is a risk, regardless of how good the demo looks.
Map the integrations your team uses daily
Most recruiting teams work across email, job boards, social platforms and career sites. List the tools that must connect to the ATS and check each connection with the vendor. Ask whether the integration is native, requires a third-party connector, or is only available on a higher plan.
A simple integration test is to trace one candidate from application to interview invitation. If the data has to be copied manually at any point, that is a workflow cost you should price into the decision. Repeat the test for the two or three tools your team touches most often, because a single broken link in a daily workflow can erase the benefit of the rest of the stack.
Budget for training and onboarding
A new ATS only creates value when recruiters use it consistently. Ask what training is included, whether it is live or recorded, and how new team members are onboarded after the initial rollout. A resource library of guides and videos is helpful, but it does not replace a named person who can answer process questions.
Set an adoption measure before go-live, such as the percentage of candidate submissions completed inside the new system in the first month. That gives you a factual way to judge whether training worked, and it turns a vague promise about onboarding into something you can check.
Compare pricing models on total cost of use
Vendors price recruitment software in different ways. Common models include per-user subscriptions, per-hire charges and per-recruiting-manager fees. The headline number is less important than the cost at your expected usage level.
Ask for a quote based on your actual team size and hiring volume, and ask which features are excluded from the base plan. A lower subscription price can become more expensive if essential integrations or support are add-ons. A useful exercise is to model three scenarios: your current volume, a busy quarter, and a year of growth. The model that stays predictable across all three is usually the safer commercial choice.
Test support before you need it
Support quality is difficult to judge from a sales call. Ask about average response time, the channels available, and whether there is a dedicated contact for your account. Check whether demos and training are available after go-live, not only during the sales process.
A practical test is to send a non-urgent question during evaluation and note how long the answer takes and whether it resolves the issue. That gives you a small piece of evidence rather than a promise. If the answer is vague or slow before you have signed, assume it will not improve afterwards.
A decision checklist for the final shortlist
Use this checklist in the final vendor review. Each item should have a named owner and a written answer.
- The top three current bottlenecks are documented and each vendor has addressed them.
- Must-have features are separated from nice-to-have features.
- The migration scope, exclusions and data retrieval process are in writing.
- Every daily-use integration is confirmed as native, connector-based or unavailable.
- Setup milestones, owners and escalation paths are agreed.
- Training format, timing and post-go-live support are specified.
- Pricing is quoted at your real team size and hiring volume.
- Support response expectations are documented and tested with a real question.
Frequently asked questions
What should I investigate first when my current ATS is failing?
Start with the specific workflow that breaks. Document where the process slows down or stops, then rank those points by business impact. This gives you a clear brief for vendors and prevents you from replacing a system without fixing the underlying process problem.
How do I separate must-have ATS features from nice-to-have features?
Ask what happens if a feature is missing for a month. If recruiters cannot complete a core task such as submitting a candidate or issuing an invoice, it is a must-have. If the impact is only on presentation or convenience, it belongs on the secondary list.
What should I ask about ATS data migration?
Ask what data will be migrated, how exceptions will be handled, and how you can retrieve your client and candidate information if you leave the vendor later. Get the answers in writing before signing.
How can I check ATS integrations before committing?
List the tools your team uses daily and ask the vendor to confirm each connection. Establish whether it is native, requires a connector, or is limited to a higher plan. Then trace one candidate through the full workflow to see whether manual copying is needed.
Which ATS pricing model is most common?
Recruitment software vendors commonly charge by feature or per user through a monthly subscription. Other models include pay-per-employee, pay-per-hire and pay-per-recruiting-manager. Compare the total cost at your actual usage level rather than the headline price.
How do I evaluate ATS customer support?
Ask about average response time, available channels and whether a dedicated contact is provided. Check whether demos and training remain available after go-live. A useful test is to send a real question during evaluation and measure how quickly and completely it is answered.