Migrate from Salesmate to Pipedrive

Salesmate Contacts (module ID 1) map to Pipedrive People. Standard fields (name, email, phone, address) transfer directly. Custom Contact fields require pre-creation in Pipedrive before migration; we create the equivalent custom field via Pipedrive's field API during the schema setup phase. Email addresses serve as the primary dedupe key. Salesmate lifecycle stage data migrates to a custom field if the customer requires it for reporting continuity.

Salesmate Companies (module ID 5) map to Pipedrive Organizations. Standard fields and custom fields transfer directly. The Organization is created before any linked People import so that the Organization ID is available for the People-Organization link at insert time. If a Salesmate Company has no Contacts, it still migrates as a standalone Organization record.

Salesmate Deals (module ID 4) map to Pipedrive Deals. Each Salesmate pipeline maps to a Pipedrive pipeline with its stages configured as Pipedrive stages before Deal import begins. Pipedrive requires a linked Organization on every Deal; we resolve the Salesmate Deal's associated Company to a Pipedrive Organization ID before inserting. Deals without a Company association enter a reconciliation queue for the customer to resolve manually before continuing.

Each Salesmate deal pipeline becomes a Pipedrive pipeline with stages created in the same order. Stage probability percentages migrate from Salesmate to Pipedrive stage probability settings. If a Salesmate pipeline has stages that share the same name as stages in another pipeline, we qualify them with the pipeline name to avoid duplicate stage labels in Pipedrive.

Salesmate Tasks (module ID 2) map to Pipedrive Activities of type Task. Due date, status, priority, owner assignment, and linked Contact or Deal association all transfer. Task ownership resolves via email matching against the Pipedrive User table. Pipedrive Activity types include Tasks, Calls, Meetings, and Emails; Salesmate Tasks without a specific engagement type land as Tasks in Pipedrive.

Salesmate email history (module ID 3) associated with Contacts migrates to Pipedrive Email activities. Full email body content transfers as available via the Salesmate API; thread metadata (which thread an email belongs to, which team member sent it) is preserved in custom fields on the Pipedrive Person or Deal when no native equivalent exists. Pipedrive does not support importing email body content via CSV; we use the Pipedrive REST API for email activity insert.

Salesmate Products (module ID 6) map to Pipedrive Products with name, pricing, description, and code fields. Currency handling respects Pipedrive's single-currency-per-product model; multi-currency products from Salesmate get separate Pipedrive product entries per currency unless the customer consolidates to a single currency before migration.

Salesmate custom fields across Contacts, Deals, Tasks, Companies, and Products are fully accessible via the API. We pre-create equivalent custom fields in Pipedrive during the schema setup phase using Pipedrive's field creation API, matching the Salesmate field type (text, number, date, dropdown, checkbox) to the closest Pipedrive field type. Pipedrive's Important Fields feature (Growth tier) and Required Fields feature (Premium tier) are configurable per field post-migration.

Salesmate Users map to Pipedrive Users by email address. Per Pipedrive's migration documentation, all destination Users must exist before importing Deals and Activities. Salesmate Owner IDs on Deals and Tasks resolve to Pipedrive User IDs via the email lookup. Any Salesmate Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Salesmate Tags on Contacts and Companies export as string arrays via the API and map directly to Pipedrive Labels. Tags are preserved as-is on both Person and Organization records. Pipedrive Labels support filtering in list views and reporting, matching the functional role that Tags serve in Salesmate.

File attachments associated with Contacts, Deals, and Companies are migratable via the Salesmate API. We download attachments and re-upload to Pipedrive's file storage linked to the corresponding Person, Organization, or Deal. Storage limits vary by Pipedrive plan tier; we flag if the destination plan's storage allocation requires cleanup before migration or if the customer needs a storage upgrade.

Salesmate Team Inbox conversations use a shared-threaded model with team member attribution and conversation threading metadata. Pipedrive does not have a native shared inbox model; thread metadata (conversation ID, team participant list, thread position) is preserved as custom fields on the related Person or Organization record. The customer decides post-migration whether to use a third-party shared inbox tool (Front, Drag, Hiver) or distribute shared inbox emails to individual Pipedrive Activity logs.