Your spreadsheets to SuiteDash migration plan
Clean your sheets before saving the CSV
Merge duplicate records, split names into first and last name columns, and use consistent phone numbers and dates.
Keep one header row and remove repeated headings. Save as UTF-8 CSV rather than an Excel workbook.
Decide which columns become standard fields, custom fields or tags. Add a role column when different client types share a sheet.
What imports into SuiteDash?
SuiteDash imports contacts, companies, or both through CRM Target Import. Choose the import that matches your records.
Contact imports support names, primary email, addresses, tags and custom fields. You can also assign roles, companies and Circles.
Company imports support names, categories, phone numbers, websites, addresses, background information, tags and custom fields.
CRM Target Import pairs a company and person in one row. Detailed contact and company custom fields use dedicated imports.
Prepare a CSV that SuiteDash can read
Save as a UTF-8 CSV, 20 MB or smaller. Include a header row, at least three columns and one data row.
Create custom fields beforehand or during mapping. Assign one role to the whole file, or map a role column.
Test a small file first. Keep Portal Access Invitation unchecked until the portal is ready.
Checking that option immediately invites imported Prospects and Clients. Review any selected import automations before running the file.
What does not transfer through the CRM import?
The CRM import documentation covers contacts and companies, not projects, invoices, deals or files.
We rebuild agreed open work and billing. Files move into portal folders separately, and historical exports remain reference records.
Templates, forms, contracts, workflows and automations are recreated. A data export does not recreate your previous system’s behavior.
Turn tracking columns into a working process
Import client and company data into the CRM. Recreate project trackers, forms, templates and billing separately.
Use CRM Target Import when a row holds both a company and contact. Detailed entity custom fields use dedicated imports.
Move shared files into agreed portal folders. Pipelines need Thrive; automated workflows and onboarding FLOWs need Pinnacle.
Check a small sample before importing the full sheet
Test a few rows and inspect names, roles, company assignments and field values. Correct the mapping before importing the rest.
Keep portal invitations off until client pages and files are ready. Walk your team through the record structure before launch.
Official documentation
Vendor details checked 3 October 2026. We confirm your account's options before work starts.