Migration guide

Moving a live desk without dropping anything

Switching CRM is not risky because the data is hard to move. It is risky because you have to keep billing, placing and answering candidates while you do it. This is the order we would do it in, with an honest list of what does not come across.

00

Find your renewal date and notice period

Ten minutes

Before you export anything, before you look at a demo. Two numbers decide whether this is a move you can make this quarter or one you plan for: the date your current term ends, and how much notice you have to give before it. Both are on the order form you signed, not anywhere in the product — which is why almost nobody knows them. Miss the notice window and most of these contracts renew for the same length again: a three-year agreement renews for another three years, not another month.

Cannot find the paperwork? Email your account manager and ask, in writing, for your renewal date and the notice period. It is a reasonable question and they have to answer it. Do that today rather than after you have migrated.

01

Export before you give notice — not after

Half a day

Pull a CSV of each of these out of your current system, in this order: companies, contacts, jobs, deals or placements. Most systems bury this under Admin, Reports or Data Export; if yours only offers it by support ticket, raise that ticket now — it is usually the longest-lead part of the whole move. The reason for doing it first is not convenience. Several of these contracts delete your database shortly after you terminate, and one of them destroys it unless you asked for a copy beforehand. Export while your licence is live, keep the files somewhere of your own, and do it whether or not you end up switching to us.

If you are coming from Bullhorn, export the Candidate and ClientCorporation objects as they come. Deskspark recognises a Bullhorn export on sight and fills in the whole column mapping for you.

02

Import companies first, then people

An hour

Order matters, and it is the one thing most migrations get wrong. Import companies before contacts and jobs, and Deskspark links each new record to the right company automatically by matching the name. Do it the other way round and you get a database of people and roles floating free of the businesses they belong to, which then has to be relinked by hand. Every import shows you the mapping and a preview before a single row is written.

Notes come across with contacts if your export has them — map the column and they land on the record rather than in a spreadsheet nobody opens.

03

Bring the CVs across

Minutes

Bulk-upload your CV folder from the Contacts page. Deskspark matches each file to the right candidate by the email address in the filename, uploads the ones it can place, and tells you plainly which it could not rather than dropping them silently. Most systems export CVs named by email already; if yours names them by candidate ID, a bulk rename is worth the ten minutes.

04

Connect the live rails

Half an hour

Connect your mailbox so sent history and replies sync into the record, set up SMS and WhatsApp if you use them, and invite your desk. Everyone works from the same contacts, jobs and pipeline from the first day, so there is no window where half the team is on the old system and half on the new one because the invites hadn't gone out.

Outlook and Microsoft 365 connect for any account. Gmail is in limited release while Google finishes reviewing our app — tell us and we'll get you added.

05

Run both, and serve notice by your date

Two weeks to run, then wait out the term

Keep the old system read-only and work entirely in Deskspark. Two weeks covers a full cycle of the things that only surface occasionally: an invoice going out, a placement hitting its guarantee window, a monthly report. Check those specifically rather than checking that contacts exist. Then treat serving notice and switching off as two separate events, because they usually are: serve notice by the date you found in step 00, keep both systems running until the term actually ends, and let the old licence lapse rather than paying to leave early.

Your trial is 14 days, deliberately the same length as the parallel run — so you can decide on real evidence. Ending a contract early almost always costs more than waiting for the renewal date, so the calendar, not the migration, is what sets the timing.

What comes across

  • Companies, with their own records and offices
  • Candidates and client contacts, with tags and status
  • Notes attached to contacts
  • Jobs and roles, with salary, location and status
  • Deals and placements, with stage and value
  • Business-development prospects
  • CVs, matched to candidates in bulk
  • Structured addresses, so radius search works from day one

What doesn't, and why

  • Historic email threads

    Your mailbox is the system of record for those. Connect it and everything from that point syncs into the contact; older threads stay searchable where they already live.

  • Invoices and timesheets already raised

    Deskspark drafts invoices from placements going forward. Closing out billing in the old system is cleaner than migrating half-paid history into a new one.

  • Interview records and stage history

    There is no import for these yet. Open placements are worth re-entering by hand; closed ones are usually not.

  • Anything from JobAdder or Vincere as a one-click preset

    Bullhorn publishes its export field list, so we auto-map it. JobAdder does not publish one. Vincere lets each agency choose, reorder and rename its own export columns, so there is no fixed set anyone could preset — a canned mapping would be wrong for most of you. Both still import fine: you map the columns once, we remember that mapping, and the next file maps itself.

What your current contract probably requires

From each vendor's own published terms, checked 29 September 2026. Terms change, and the order form you signed overrides anything on a public page — so treat this as the question to ask, not the answer. Get your own contract out.

Bullhorn

Notice to leave
30 days before expiry to decline renewal. 90 days to terminate early, with no refund of the remaining term.
Your data afterwards
Destroyed on termination unless you request a copy beforehand — and returned at your expense.

Recruit CRM

Notice to leave
Cancel any time from settings. Charges already paid are not refunded, including for seats you switch off.
Your data afterwards
14 days to ask for an export. After that it is deleted and cannot be recovered.

Loxo

Notice to leave
Cancel at least 24 hours before the renewal date. It takes effect at the end of the term, not immediately.
Your data afterwards
No further access to your data once the term ends. One full backup free on request.

JobAdder

Notice to leave
Not published — ask for your own terms.
Your data afterwards
90 days before permanent deletion. A backup you request is itself deleted 14 days after it is made.

Vincere

Notice to leave
Reported as a 12-month minimum with three months' notice. Not published — ask for your own terms.
Your data afterwards
Not published.

If your contract has months left to run

That is the usual answer, and it does not have to end the conversation. Paying for two systems at once is a real cost and we would rather not ask you to. Tell us when your term ends and we will work something out that lets you migrate now, at your own pace, without carrying both bills until it does.

Moving calmly across a few months, while your old system is still there to check against, is a considerably better migration than one done in the fortnight after a licence lapses.

Tell us when yours ends

The move is an afternoon. The contract is the long pole.

The import itself takes a couple of hours and the fortnight of parallel running fits inside the free trial. What actually sets the date is your notice period — so start with step 00, today, even if you are months away from moving.

Weighing up more than one system? Score your shortlist against what actually matters on a desk.