Migrate from Sage CRM to Pipedrive

Sage CRM Companies map to Pipedrive Organizations. We extract the CompanyName, address fields, industry classification, and any custom Company fields. Company is the first object migrated because Pipedrive People require an Organization attachment for the PrimaryCompanyLink relationship to resolve. Sage CRM's match-rule configuration is applied as a deduplication key during Organization insert to prevent duplicate accounts arriving in Pipedrive.

Sage CRM Contacts map to Pipedrive People with the PrimaryCompanyLink resolved to the Organization created in the prior phase. All standard fields (name, email, phone, title, address) and custom Contact fields migrate directly. Email address is used as the Person dedupe key. Sage CRM stores Contacts with a separate Lead entity; we do not merge these during migration since Pipedrive handles both as People types with separate lifecycle states.

Sage CRM Leads are a separate entity from Contacts with their own lifecycle stages, qualification fields, and source tracking. We import all Sage CRM Leads as Pipedrive People with the Person type set to Lead, preserving the original Sage CRM lead status and source fields as custom fields for reporting continuity. Any Sage CRM lead that was already converted to a Contact before migration is handled as a Contact record and does not duplicate the Person entry.

Sage CRM Opportunities map to Pipedrive Deals. We map the Sage CRM pipeline and stage to a corresponding Pipedrive pipeline and stage, with stage probabilities computed from the Sage CRM probability percentages. Each Opportunity's CompanyLink becomes the Pipedrive ActivityKey that links the Deal to the Organization record. Custom Opportunity fields migrate as Pipedrive custom Deal fields, and multi-currency amounts are stored as-is with currency metadata carried in a custom field.

Sage CRM pipelines and stage values are configured in Pipedrive before Deal import begins. Each Sage CRM pipeline becomes a Pipedrive pipeline, and each Sage CRM stage becomes a Pipedrive stage within that pipeline. Stage order, probability percentages, and Closed Won or Closed Lost status carry over. Loss reason and win reason from Sage CRM custom fields become separate stage options or custom fields in Pipedrive depending on the customer's reporting needs.

Sage CRM Cases do not have a direct Pipedrive equivalent because Pipedrive has no native Cases object. We configure a Pipedrive Deal with a service-oriented pipeline for Cases, with case details, severity, status, and assignment stored as deal fields and notes. If the customer's Pipedrive plan does not include Deals, Cases migrate as Notes attached to the related Organization or Person, with the case subject as the note title and case body as note content. Threaded Communications are stored as additional notes on the Case record.

Sage CRM Communications (emails, calls, meetings) map to Pipedrive Activities. Each Communication is attached to the Pipedrive Organization, Person, or Deal that corresponds to the Sage CRM entity it links to. Email body migrates as a note attached to the record; call duration and disposition migrate as custom fields on the Activity. We resolve the Sage CRM entity-type and entity-ID to the Pipedrive ActivityKey at migration time. Meeting location and attendee details migrate as Activity custom fields.

Sage CRM Custom Entities have no native Pipedrive equivalent. We flatten each Custom Entity into Pipedrive's custom field infrastructure on the relevant standard object, or store the entity as a Note with attribution (entity type and original record ID in the note title) attached to the parent record. Relational data between Custom Entities and standard entities does not carry over as active relationships; the customer reviews the flattening decisions during scoping and chooses per-entity how to handle each one.

Sage CRM workflow rules are stored as database records with embedded ASP-script logic, escalation triggers, and conditional actions. These cannot be exported as migratable data and have no equivalent in Pipedrive's automation model. We produce a complete workflow inventory during discovery, documenting every active Sage CRM workflow with its trigger conditions, stage transitions, and action chain. The customer uses this inventory to rebuild automation in Pipedrive's workflow tools, which is outside migration scope.

Sage CRM reports are stored in the Sage CRM report schema with field references by internal ID. Report definitions, formatting, formulas, and scheduling cannot migrate across platforms. We extract a list of Sage CRM reports with their data sources and key filters as a reference document for the customer to recreate in Pipedrive's reporting tools or a connected BI platform. The report handoff document is delivered alongside the workflow inventory during cutover.

Sage CRM Users with role-based security profiles are mapped to Pipedrive Users by email address. Sage CRM role permissions (object access, field-level read/write) are documented for the customer's admin to reconfigure in Pipedrive's access control settings, since the permission models differ structurally. Inactive Sage CRM users are migrated as inactive Pipedrive users with a note flagging their original status for the admin to review.