How to migrate into SuiteDash without breaking your CRM

Moving into SuiteDash fails the same way most CRM moves fail: the file arrives before the destination is ready, and staff are told the new system is live while they still cannot find this week's work. The sequence below is the one we use before anyone calls the import finished.

Decide whether to migrate or start clean

Migrate when the records are current and someone still works them. Start clean when the old CRM is mostly dead leads and you would spend longer cleaning the file than re-entering what still matters.

Stay on the old CRM a little longer if any of these are true:

• Open deals have a next step this month, and only one person knows where they live.
• Companies and contacts are mixed in a single cell, and nobody has split them.
• You need last year's closed revenue for reporting, not just the live pipeline.

Start clean in SuiteDash, and keep the old system as a read-only archive, if:

• Most rows have not been touched in a year.
• Stages mean different things to different people, so an import would freeze the argument in place.
• You are changing how you sell, not just where the spreadsheet sits.

A portal for clients is a separate question from the CRM import. Sort roles before you invite anyone — the client portal guide covers that.

Export contacts, companies, and open deals first

Export contacts, companies, and open deals before notes, files, or closed history. Those three are what staff need on day one. Everything else can wait until the new records have a home.

Export these, in this order, from the system you are leaving:

1. Companies. One row per company. Legal name and the name staff actually say. A single website or domain if you have it, so duplicates are easier to spot.
2. Contacts. Name, email, phone, and the company they belong to. One email per person where you can. Leave marketing-only lists out of the first file.
3. Open deals. Name, company, value if you use it, stage, owner, and the next step. Closed-won history can be a second file after the live board is trustworthy.

Do not lead with attachments, email archives, or every custom field the old tool invented. If a column has no owner on the SuiteDash side, it will become a junk drawer.

Stage the import before anyone calls it live

Create the fields and pipeline stages in SuiteDash first, then import a small test batch. Keep the old CRM readable until a staff member who is not the admin can find a real open deal and its next step.

Before go-live, the staging checklist is short on purpose:

• Custom fields exist in SuiteDash before the spreadsheet is imported.
• Pipeline stages match words your team already uses. Rename stages now, not after fifty deals land in the wrong column.
• A test import of about ten records, including one awkward company with two contacts.
• Each open deal in the test has an owner and a next step.
• Someone who is not the account admin can find that deal without asking you.
• The old CRM stays available, read-only if you can, until that test passes.
• Clients are not invited yet. Portal permissions are a later step.

If you bought SuiteDash on a promo and are not sure which import and automation tools your plan includes, confirm that before you design the move. The AppSumo setup guide is the day-one version of that check.

Check the mistakes that break a CRM import

Watch for duplicate companies, a status field staff will treat as the live pipeline, and automations that email the imported list. Do not invite clients until internal notes are confirmed hidden.

• Duplicates. "Acme", "Acme Inc", and "Acme Incorporated" become three companies, and the open deal attaches to the empty one.
• Status dumped into the wrong field. A free-text status from the old CRM looks official. Staff will treat it as the pipeline even when the real stage is blank.
• Notes that clients can see. Internal comments imported onto a record that a portal user can open. Check a client view before the invite goes out.
• Automations aimed at the whole file. A welcome FLOW or a payment reminder that runs on create will talk to people who did not just become customers. Turn those off until the import is done. See which automations to delay.
• Going live because the file uploaded. An import with no errors is not a CRM your team trusts. Trust is the ten-record test, done by someone other than the person who built it.

Call WrightClick when the move is the business

Ask for help when more than one system is the source, open deals represent real revenue, or a previous import already made SuiteDash harder to trust than the old CRM.

WrightClick's migration help is scoped after a Free Assessment — pricing on request. It sits next to setup and ongoing support on the SuiteDash setup page. If you want the full sequential package instead of a migration-only pass, the published all-in figure is on the SuiteDash implementation page.

Bring the exports, a list of what "open" means in your business, and one example of a deal that must not be lost. That is enough to tell whether this is a staged import or a clean start.