Migrate from Creatio to Pipedrive

Creatio Accounts map directly to Pipedrive Organizations. The Account Name becomes the Organization name, address fields map to the standard address block, Industry maps to Pipedrive's Industry dropdown, and website maps to the URL field. We use Organization name as the dedupe key during import to prevent duplicate Organizations from merging mismatched Accounts.

Creatio Contacts map to Pipedrive People. We resolve the parent Organization by matching Creatio's Account lookup against the migrated Organization record, populating Pipedrive's org_id field at writeback. Name, email, phone, title, and address fields migrate directly. Lifecycle stage from Creatio (Lead, Customer, Evangelist, etc.) is preserved as a custom field creatio_lifecycle__c on the Person record.

Creatio Opportunities map to Pipedrive Deals. Stage maps to a Pipedrive Pipeline Stage; we create the pipeline and stage structure during setup using Creatio's pipeline definition as the source. Amount, Close Date, and Probability migrate directly. Pipedrive does not have a native Probability field on Deals; we store the original Creatio probability as a custom field deal_probability__c.

Creatio Pipelines (configurable per product line) map to Pipedrive Pipelines. Each pipeline's stage names and order are recreated as Pipedrive Pipeline stages. Stage probabilities from Creatio are stored as custom fields rather than native Pipedrive fields. Automation triggers on Creatio pipeline stages are documented but not migrated.

Creatio Leads map to Pipedrive Leads (available from Advanced tier). Lead Status and Source fields migrate to Pipedrive's built-in Lead fields. Any HubSpot-style lead scoring value stored in a Creatio custom field is preserved as a custom field lead_score__c. Pipedrive's Lead object feeds the People/Organization model; the customer configures the lead routing during Pipedrive setup.

Creatio Activities of type Call, Email, Meeting, and Task under the unified Activity schema are split into Pipedrive's separate object types at writeback. Call duration, disposition, and recording URL map to Pipedrive Call custom fields. Meeting start and end times map to Pipedrive Meeting fields with Location preserved. Emails land as linked email records in Pipedrive's email history.

Creatio Cases (Service module) have no direct Pipedrive equivalent because Pipedrive is sales-focused. We map Cases to Pipedrive Activities (Tasks) with Case Number and Status preserved in custom fields case_number__c and case_status__c. Resolution SLA and priority fields migrate as custom fields. Cases that require service-level tracking should be routed to a dedicated helpdesk tool post-migration.

Creatio Products map to Pipedrive Products with SKU, name, and unit price preserved. Creatio's multi-currency pricing on Products requires currency mapping during writeback; we detect the base currency and apply it to the Pipedrive Product price, flagging any multicurrency pricing records for manual configuration in Pipedrive if the customer does not hold Enterprise-level multi-currency.

Creatio Users assigned as record owners are mapped to Pipedrive Users by email match. We build a user lookup map during discovery and resolve OwnerId on every Contact, Account, Opportunity, and Activity record before writeback. Any Creatio User without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before migration continues.

Creatio custom objects built in the Object designer are exported from the package schema during discovery. Each custom object's columns are reverse-engineered from the package definition and mapped to Pipedrive custom fields on the equivalent standard object (Person, Organization, or Deal). Complex custom objects with multiple lookups may be represented as structured Note records with a custom field type tag. The customer receives the full column map as part of the migration documentation.

Creatio v8.3.2+ file storage mode is detected during discovery via the UseEntityFileApi flag. Files stored in-database are exported via Creatio's File API and re-uploaded to Pipedrive as attachments linked to the parent record (Person, Organization, or Deal). Files stored in S3 or Azure Blob are retrieved from the external storage location and uploaded to Pipedrive. The storage mode redirect is critical; missing this step results in broken attachment links at the destination.