Migrate from Exsalerate to Pipedrive

Exsalerate Accounts map directly to Pipedrive Organisations. Account Name becomes Organisation name; address fields map to Pipedrive address fields (address, city, state, postcode, country). Exsalerate custom fields on Account migrate to custom Organisation fields in Pipedrive. We use Organisation name as the dedupe key during import to prevent duplicate Organisations from multiple CSV export runs.

Exsalerate Contacts map to Pipedrive Persons. The Account-Contact relationship becomes the Organisation-Person link in Pipedrive using the Person's Organisation field. Email address is the dedupe key for Person records. We run duplicate detection across the Contact set before import, flagging records with identical email addresses for the customer's admin to resolve.

Exsalerate Pipelines map to Pipedrive Pipelines. Pipeline name and stage sequence transfer directly. Exsalerate's colour-coded stage labels migrate to Pipedrive's stage colour metadata. Each Pipedrive pipeline requires at least one stage; we confirm stage names and order match during scoping before creating the Pipedrive pipeline structure.

Exsalerate Pipeline Stages map to Pipedrive Deal Stages within the corresponding Pipeline. Stage order is preserved. The Exsalerate stage colour value is stored as a custom field on each Deal stage for visual consistency. Pipedrive stage probabilities are set to match Exsalerate's configured percentages where available; otherwise we use Pipedrive defaults and flag the discrepancy for the customer's admin.

Exsalerate Opportunities map to Pipedrive Deals. Opportunity value maps to Deal value; expected close date maps to Pipedrive close_date; stage assignment maps to the correct Pipedrive Pipeline stage. Owner assignment migrates by resolving the Exsalerate user email to a Pipedrive User. Deals without an Account reference are flagged in the reconciliation report; Pipedrive allows Deals without an Organisation but we document the orphan count for the customer.

Exsalerate allows WorkflowMax quotes to be imported as Opportunities, creating a cross-reference attribute that is not a standard Opportunity field. Pipedrive has no native WorkflowMax reference field. We store the WorkflowMax quote ID or job reference in a custom Deal field (wfm_quote_reference__c) created before migration. We flag this linkage in the reconciliation report so the customer's admin can manually reconnect WorkflowMax records in Pipedrive or via a Zapier/Make integration.

Exsalerate To-Do Items map to Pipedrive Activities (Task type). Due date, status (open/closed), and assigned owner transfer directly. Exsalerate's colour-coded activity tile encoding is preserved in a custom Activity field called tile_colour__c. Not all Pipedrive plans expose custom fields on Activities at no cost; we confirm this during scoping and adjust the mapping to use Activity labels or note text if custom fields are not available on the customer's target plan.

Exsalerate Email Activities map to Pipedrive Activity records of type email. Subject, body, sender, recipients, and timestamp migrate. The activity is linked to the corresponding Person and Organisation. Attachments are migrated as separate file records linked to the Activity. Email threading relationships (in-reply-to references) are not guaranteed to transfer; we document the email thread break count in the reconciliation report.

Exsalerate custom fields on Accounts migrate to Pipedrive custom Organisation fields. Field type awareness applies: picklist values map to Pipedrive picklist options with exact value matching; date formats are normalised to ISO 8601 (YYYY-MM-DD); numeric fields map to Pipedrive numeric fields. Any Exsalerate custom field that has no Pipedrive equivalent is held in a gap list for the customer to configure in Pipedrive before migration or to accept as a note-field migration.

Exsalerate custom fields on Contacts migrate to Pipedrive custom Person fields following the same type-awareness rules as Organisation custom fields. Picklist values, date formats, and numeric precision are normalised at migration time. Person custom fields are created in Pipedrive before the Contact (Person) import phase begins.

Exsalerate custom fields on Opportunities migrate to Pipedrive custom Deal fields. The Deal-level custom field creation sequence must complete before the Opportunity (Deal) import phase begins. We map each Exsalerate field to a Pipedrive field type that can accommodate the data; multi-select values in Exsalerate become comma-separated text in Pipedrive or a multi-select picklist depending on the target Pipedrive plan.

Exsalerate user accounts map to Pipedrive Users. We resolve Exsalerate users by email address to Pipedrive User email. Inactive Exsalerate users are flagged in the reconciliation report; their records can be assigned to a placeholder User (e.g., exsalerate_migration_inactive) or to the primary admin for the customer's team to reassign post-migration. New Pipedrive Users must be provisioned by the customer's admin before the migration phases that require Owner assignment.