Switching applicant tracking systems has a reputation for taking months and making everyone miserable for the duration. It does not have to. A team of two to twenty recruiters can be fully working in a new ATS in five business days if the week is planned around one principle: get real candidates flowing through the real pipeline as early as possible, and configure everything else around what that reveals. Here is the plan we use with teams moving onto Apex ATS. It works for most systems.
Before day one: decide three things
- Who owns the rollout. One person, with the authority to make small decisions without a meeting. Committees turn a week into a quarter.
- What comes over from the old system. Active candidates, open jobs, and the last 12 months of hires for reporting. Not everything. A ten-year archive of rejected applicants is a liability, not an asset.
- The cutover date for messaging. After that date, every text and email to a candidate goes through the new system. No parallel running. Parallel running is how conversations get lost.
Day 1: accounts, jobs and the pipeline
Morning: create user accounts, set roles, and connect the calendar for everyone who runs interviews. Afternoon: enter the open jobs (or import them) and set up the pipeline stages. Resist the urge to design a perfect ten-stage process. Applied, screened, interview, offer, hired covers most teams, and you can add a stage later when you have evidence you need it. Attach requirements to each job so ranking works from the first applicant. By end of day, one recruiter should have submitted a test application and watched it parse, rank and land in the pipeline.
Day 2: import candidates and go live on messaging
Import active candidates and the trailing 12 months of hires. Check a sample of 20 records by hand: contact info, stage, source. Fix mapping problems now, while the import is small. Then hit the messaging cutover. Set up the shared team number, confirm consent capture on the application form, and send the first real texts from the applicant record. This is the moment the team stops treating the new system as a sandbox. Someone should be replying to candidates in the shared inbox by 3pm.
Day 3: templates, self-scheduling and posting
Write the core message templates, seven or eight of them, in the voice of your best recruiter. Turn on interview self-scheduling for the two or three interviewers who do the most screens, and have a candidate actually book a slot so you see it land on a calendar. Then connect the job boards and social pages and multi-post every open job in one go. From this point on, new applicants arrive tagged with their source, which is what makes the analytics worth reading next month.
Day 4: integrations and the people who are not recruiters
Connect the HRIS, payroll and background-check providers so the hired stage does something useful. Run one candidate all the way through to confirm the employee record is created and the background check is triggered. Then spend an hour with hiring managers. They do not need training on the whole system. They need to know three things:
- 01Where to see the candidates for their job and how to leave a note.
- 02How to accept or decline an interview that lands on their calendar.
- 03Who to ask when something looks wrong. One name, not a help desk.
Day 5: shut off the old system and read the first report
Set the old system to read-only. Not deleted, read-only, so nothing is lost and nobody is tempted to keep working in it. Then open the analytics and look at the week: applicants by source, stage counts, first response times. The numbers will be small and a little messy. That is fine. The point is that the team has seen the report exists and knows it will be looked at. Close the week with a 30-minute session where everyone says the one thing that annoyed them most. Fix the top two the following Monday.
The things that go wrong, and how to avoid them
- Over-configuring on day one. Every custom field and stage you add before seeing real data is a guess. Start plain, then adjust.
- Training before doing. An hour of slides teaches less than 20 minutes of moving a real candidate through the pipeline.
- Keeping the old system alive "just in case." Two systems means two sources of truth, which means none.
- Skipping the sample check on import. A source field that maps wrong is invisible until the report is wrong in three months.
- Nobody owning it. Rollouts without an owner stretch until everyone quietly gives up.
One week is not a stunt. It is what happens when a team stops treating software as a project and starts treating it as the place where the work happens. Get candidates in on day one, messages out on day two, and by Friday the old system is a read-only memory. If you are planning a move and want a hand with the import or the day-by-day, write to management@apexsales.ai. We have done this enough times to know where the potholes are.