Migrate from Drift / Salesloft to Message

Check the import scope

Supported import scope: The contacts, conversations and messages present in your prepared file. CSV mapping includes authors, timestamps, status and private-note visibility.

This is a file-based import, not a native Drift / Salesloft API connection. A raw vendor export may need conversion. Missing fields and unavailable attachments cannot be reconstructed by the importer.

Prepare the source

Export records you are authorized to move, then map the fields to the Message CSV or normalized JSON format.

Keep an original export or source backup. Confirm that you are authorized to move the records and select the correct destination workspace.

Preview before importing

Open https://app.message.com/settings/integrations/migrate and choose the supported provider or file-import path. Review discovery or file mapping, agent and department mapping, private notes and attachments before importing the full dataset.

Verify records and failures

Inspect sample customers and conversations in Message. Compare authors, dates, message order, status and internal-note visibility. Review the migration job’s errors and warnings. Do not mistake a contact-only import for a complete support-history migration.

Reconfigure operations

Keep your original export. Use stable source IDs and the same dataset name when preparing follow-up files. Validate internal-note visibility before importing the rest.

Review product entitlements and billing separately. A migration does not grant unlimited seats, free phone usage or every AI feature.

Switch channels after testing

Install the current widget snippet and test inbound and outbound conversations. Move email forwarding and any other channel connections separately. Keep access to the original system until the remaining data and operational checks are complete.

Identity and private data

The shipped widget does not provide a public identify, signout or userHash login API. Browser continuity and a pre-chat email are not proof of account ownership. Use the connector’s supported customer-verification flow before disclosing private order information.