A small recruitment agency can usually roll out a new ATS in about 30 days: a week to set up and move the data, then three weeks of live use while the team builds habits and you fill the gaps. The data move itself often takes days rather than months; what takes longer is getting every consultant to work in the new system.
We found no independent survey of how long small agencies take to go live, so treat any "typical" figure with care. Vendors publish their own: Bullhorn, for example, says small agencies go live in under two weeks. This guide gives a practical week-by-week plan for a one-to-five person agency, who should do what, what to migrate first, and the pitfalls that slow adoption. It is illustrative, built from common practice rather than a benchmark. It was last updated on 15 October 2026.
How long does an ATS rollout take for a small agency?
Enterprise rollouts can take months, but they do not reflect a five-person agency on a modern tool. For a small agency with reasonably clean data, moving records takes days to a few weeks; messy data is what makes it slow. Some review sites report vendor migration queues slipping from a promised four to six weeks to eight to ten, which is painful when you are running two systems in the meantime.
In Crumblelead, migration is free on any paid plan and typically takes about a week, with a sandbox dry run so you can check the result before the final import. That leaves most of the month for the part that decides whether the rollout succeeds: daily use.
Who should own the rollout?
Name one owner, usually the founder or a senior consultant, who decides how stages, templates and permissions should work and makes the final call on what to migrate. Without an owner, decisions stall and everyone keeps a private workaround.
Give each consultant a clear role in the first month: connect their own email and calendar, move their live jobs, and check their own candidates after the import. In Crumblelead, roles are Admin, Manager and Consultant, so the owner can control settings while consultants work their desks.
What should you migrate first?
- Active jobs and their pipelines: who is submitted where.
- Clients and contacts, especially live and warm accounts.
- Candidates contacted in the last 12 to 24 months, with their CVs. Older records should go through a retention review first, not a blind import.
- Placements and fees, for reporting and rebate periods.
- Everything else, such as archives and old notes, only if you need it, and only after a GDPR review.
Importing years of stale candidates is a liability under the retention principle, not an asset. Our guide to switching ATS without losing data covers exports, dry runs and sign-off in detail.
What does a 30-day rollout plan look like?
| When | Focus | Key tasks |
|---|---|---|
| Days 1 to 3 | Set up | Start the trial, connect email and calendar for every user, set pipeline stages to match how you work, add email templates and your privacy wording |
| Days 4 to 7 | Clean and import | Export spreadsheets and old ATS data, remove duplicates and records you have no reason to keep, test 50 to 100 rows, run the full import, upload CVs |
| Week 2 | Live work only | All new jobs and candidate activity go in the ATS, set up your LinkedIn workflow, make the old spreadsheet read-only, hold one 60-minute team session |
| Week 3 | Fill the gaps | Bring older live pipelines across, set client follow-ups, settle how you will handle job advertising and invoicing |
| Week 4 | Review | Check data quality and activity logging, set retention rules, build the two or three reports the owner will read, cancel the old tool once nothing is missing |
Days 1 to 3: set up
Keep configuration light. Set pipeline stages to the steps you actually use, add the handful of email templates you send every week, and connect every consultant's email and calendar on day one. In Crumblelead, email sends from each person's own Gmail or Outlook address and the calendar syncs both ways, so activity starts building on the record straight away.
Days 4 to 7: clean and import
Export each sheet or old system to CSV in UTF-8, separate candidates, clients and contacts, and drop people you no longer have a reason to hold. Import a test of 50 to 100 rows, fix the column mapping, then run the full import and upload CVs in bulk. If we run the migration for you, this is the week we map your data and you check the sandbox dry run.
Week 2: live work only
From now on, if it is not in the ATS, it did not happen. Make the old spreadsheet read-only so there is one source of truth, and run a single hour-long session where everyone works a real job together. Set up how you capture people from LinkedIn; see what an agency ATS should connect to for the options and LinkedIn's rules.
Week 3: fill the gaps
Rebuild pipelines for any older jobs still in play, and give each live client a next action so follow-ups are not forgotten. Decide where job advertising and invoicing will live: Crumblelead does not post to job boards or raise invoices, so agree the process with your boards and accounting software.
Week 4: review
Spot-check records for duplicates and missing CVs, and look at who is logging activity. Set your retention rules, build the few reports the owner will actually read, such as placements, pipeline and consultant activity, and only then cancel the old tool.
How long does it take to train a team?
We found no sourced figure. The common view among practitioners is about one to two hours of initial training per user for a simple modern tool, followed by a week of supported use. The owner's setup of stages, templates, email connections and permissions takes longer. A short session on a real job usually works better than a feature tour.
What are the most common adoption pitfalls?
- Running the old spreadsheet in parallel "just in case", so the data splits.
- Importing duplicates and stale records, so the team distrusts the system from day one.
- Over-configuring, with too many custom fields and stages.
- Leaving some users' email unconnected, so activity history has gaps.
- No named owner or champion.
- No rule that work happens in the ATS.
- Buying an enterprise tool and using a small fraction of it.
Remember that free migration does not mean zero effort: you still decide the mapping, the duplicate rules and what to leave behind.
Where Crumblelead fits
Crumblelead is built for perm-focused small agencies, at $30 per user per month or $25 billed annually, with a 14-day trial and free migration on any paid plan. If you are coming from spreadsheets, read spreadsheets versus an ATS; if you are switching systems, see migration help.
FAQ
How long does it take to train a recruiter on a new ATS?
There is no sourced benchmark. Practitioners commonly suggest one to two hours of initial training per user for a simple tool, then a week of supported use on real work.
Which records should a small agency migrate first?
Live jobs and their pipelines, then active clients and contacts, then candidates contacted in the last one to two years with their CVs. Review older records for retention before importing them.
Who should own an ATS rollout in a small agency?
One named person, usually the founder or a senior consultant, who decides on stages, templates and what to migrate, and makes sure every consultant moves their own work across.
Sources
Bullhorn, small agency implementation, 13 July 2026.
https://www.bullhorn.com/?p=108363
ICO, Keeping recruitment records (draft guidance).
Capterra review snippets on vendor migration timelines, 2025 to 2026.