You've requested your data and it's on its way to us. But there's a short window where you can't add to your old CRM yet and the migration isn't finished. So where do you actually work in the meantime? Here's the simple answer.

(This assumes you know the wider process already. If not, see Migrating your data to Trail for the full steps, cost and timeline, and When's the best time to request your data for timing.)

Work across two systems

If you're joining KAN, you get free access to Trail during your notice period, so you're never left without somewhere to work. Just split it:

• Old CRM: use it as a read-only reference for existing client history.

• Trail: put all new activity here from day one, new clients, new notes, everything.

• Keep a short list of any existing clients you add new info for. Takes seconds, and it makes the next bit painless.

What about duplicates?

Say John Smith is an existing client. His history is in your old CRM, waiting to migrate. Mid-transition he comes to you for a new home loan, so you enter it into Trail.

After migration you'll briefly have two John Smiths: the old record from your export, and the new one you created.

That's normal and easy to fix. Trail's merge function combines both into one complete profile, full history plus new activity. That short list of updated clients tells us exactly which records to merge, so nothing slips through.

The short version

Work in Trail while you wait, keep your old CRM open as a reference, note who you've updated, and we handle the migration and any merges. The changeover is the easy part. Get in touch and we'll map out your timeline.