Docs · Migrating from Another CRM

Will importing my contacts text my existing customers?

Not if you map your stages on the way in. Import everything as leads, then convert customers to Clients one at a time as you work them.

Who this is for

Anyone about to run their first import. Read this before, not after.

Steps

Import your whole file as leads. Don't try to split it first.
If your file has a stage/status column, the importer adds a step where you match their stages to ours — map anything meaning sold, closed-won, active client or policyholder.
Those leads import parked at the closed end of your pipeline: not dialed, not texted, waiting for you.
As you work through them, convert the real customers to Clients from each lead's page. That creates their client record and policies and stops the AI for good.

The short version: import everything as leads, then promote. Lead → Client is the supported direction and it does real work — it creates the client record, migrates their text history, sets up policies and locks the lead so the AI stops. There is no way back from a Client to a lead, which is exactly why you don't want to guess up front.

Why import everything as leads first

It's the reversible direction. A customer sitting in your lead list is a to-do; a lead wrongly filed as a Client is a record you have to unpick by hand. You also usually can't tell from the file alone — one row says "Sold" but the policy lapsed, another says "Active" but it's a different household member. Working them one at a time is how you find that out, and converting as you go costs nothing extra.

The stage mapping is what keeps them safe

This is the part that actually prevents the cold text. When your file has a stage column, the importer collects every distinct value in it and asks you to match each one. Map "Sold", "Closed Won", "Client" or "Active" and those leads land somewhere nothing reaches them — out of the dialer queue and excluded from AI texting, even if auto-enroll is switched on. It also shows you the count for each stage before you commit, so you can see how many people you're about to park.

If your file has no stage column at all

Then nothing distinguishes a customer from a lead, and every row imports as a fresh lead. In that case turn OFF "Auto-enroll into AI SMS" on the import screen, work the list, and enrol the genuinely-new ones afterwards. It's the one case where the checkbox matters a lot.

What converting actually does

From the lead's page, converting creates the Client record and any policies, brings their text history across, marks the lead converted and locks it so no automation touches it again. If a matching lead already existed when you imported clients separately, the two are linked and the lead is locked the same way.

How to check it worked

After importing, filter your leads by the stage you mapped for customers and confirm the count matches what you expected.
Open one of them and confirm no AI conversation started.
Convert one to a Client and confirm they appear in the Clients list with their policy.

Common mistakes

Skipping the stage-matching step and letting sold customers import as brand-new leads — that's the cold-text scenario.
Leaving auto-enroll on when the file has no stage column to protect anyone.
Trying to import customers as Clients up front on a guess. Convert as you work them instead — it's reversible right up until you do.

Moving from another CRM — start hereWhat comes across, what doesn't, and the order to do it in — whichever platform you're leaving.Matching your old CRM's stages to oursYour stage names don't have to match ours — the importer maps them for you, and shows what each one will do to those leads.How do I bring my opt-outs and DNC list across?Map the opt-out column during import.

Where this lives in the app

Open this screenOpens in the app

This is documentation for Virtual Closer. Book a walkthrough or sign in.