Migrate from Optimiser CRM to Pipedrive

Optimiser CRM Contacts map directly to Pipedrive People. Standard fields (name, email, phone, address) map to Pipedrive's corresponding People fields. Because each Optimiser instance defines its own custom fields on Contacts, we review every active Contact property during scoping, exclude any field with zero data across all records, and create Pipedrive custom fields of the appropriate type for each non-standard property that carries data.

Optimiser Companies map to Pipedrive Organizations. We resolve by company name as the dedupe key during import. Any external ID field on the Optimiser Company record is preserved as a custom Organization field in Pipedrive to maintain the reference for future integrations. Custom properties on Companies are handled the same way as Contact custom fields: individual review, zero-data exclusion, and Pipedrive custom field creation before import.

Optimiser Deals map to Pipedrive Deals with the stage translated through a per-instance stage-mapping table. We extract the full stage list from the Optimiser instance, identify any stages with zero records, and exclude those from the Pipedrive pipeline configuration. Deal value, expected close date, owner assignment, and custom Deal properties migrate directly. Closed-Lost and Closed-Won statuses map to Pipedrive's deal_status values.

If the destination Pipedrive account has the CRM+ tier with Leads enabled, Optimiser Lead records map to Pipedrive Leads with status and source fields preserved as custom fields. If CRM+ is not active, Leads are imported as People records with a custom field lead_source__c carrying the original lead source value. The customer chooses the strategy during scoping.

Optimiser Activities (calls, emails, meetings, notes, and tasks) group into Pipedrive's Activity object with the activity_type field distinguishing each subtype. We preserve chronological ordering by setting the Pipedrive Activity timestamp to the original Optimiser timestamp. Each Activity is linked to its parent record (People, Organization, or Deal) via the Pipedrive deal_id and person_id reference fields resolved at migration time.

Custom fields on Contacts, Companies, and Deals in Optimiser require individual mapping during scoping because no standard field schema exists across instances. We request a full field inventory from the customer, exclude fields with no data, and create typed Pipedrive custom fields for each populated custom property. Pipedrive supports fewer custom field types than some CRMs; unsupported field types are flagged with a recommended workaround during scoping.

Optimiser's Projects module does not have a direct Pipedrive equivalent. Pipedrive does not ship a native Project object. Projects are treated as a secondary migration pass: we export Project records and present the customer with two options during scoping — map Projects to Pipedrive Deals with a custom project-type label, or defer to a dedicated project management platform post-migration.

Optimiser Users map to Pipedrive Users by email address. We extract every distinct user referenced on Contact, Company, Deal, and Activity records and match against the destination Pipedrive account's user list. Any Optimiser Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import continues, because OwnerId references are required on Deals and Activity records.

Optimiser tags applied to Contacts or Deals export as label values. We migrate tags as Pipedrive multi-select picklist fields. If the customer uses Pipedrive's Topics feature for content classification alongside CRM tags, we identify the overlap during scoping and apply the appropriate Pipedrive feature to each tag set.

Workflows, assignment rules, and follow-up triggers built in Optimiser are stored in Optimiser's proprietary logic layer and do not export in a machine-readable format. We do not migrate automations. We deliver a written rebuild checklist enumerating every Optimiser automation with its trigger, conditions, and recommended Pipedrive Workflow Automation equivalent. The customer's admin rebuilds each automation post-migration using Pipedrive's visual workflow builder.