Migrate from Sales Creatio to Pipedrive

Creatio Accounts (companies) map 1:1 to Pipedrive Organizations. The Account name, address fields (street, city, state/province, postal code, country), phone, website, industry, and type fields map to their Pipedrive equivalents. We use the Organization name as the dedupe key during import to prevent duplicate Organizations from being created if multiple Contacts reference the same Account.

Creatio Contacts map 1:1 to Pipedrive Persons. Name fields, email addresses, phone numbers, communication preferences, and job title transfer directly. The Contact's parent Account reference resolves to a Pipedrive Organization ID at migration time so the Person-Organization link is established on insert. Owner assignment migrates by email lookup against the User mapping table.

Creatio Leads map directly to Pipedrive Leads. Lead source, status, rating, and conversion date transfer as custom fields or standard fields depending on Pipedrive tier. Pipedrive distinguishes Leads (unqualified prospects) from Persons (qualified contacts); if the customer converts Leads in Creatio before migration, we map them as Persons attached to Organizations. If Leads remain unconverted, they land as Pipedrive Leads pending qualification.

Creatio Opportunities map 1:1 to Pipedrive Deals. The Opportunity's name, amount, probability, expected close date, and pipeline stage transfer. Stage names are customizable in Creatio per organization; we extract the active pipeline configuration and map each Creatio stage name to a corresponding Pipedrive stage within a configured Deal pipeline. Owner assignment resolves by email against the User mapping table. The Opportunity-Account lookup becomes the Deal-Organization link.

Creatio Products map to Pipedrive Products with code, name, unit type, pricing, and tax categories transferred. Pipedrive Products have a different data model from Salesforce PricebookEntries; they function as standalone product records that can be linked to Deals as line items. We migrate the product catalog as a standalone import before Deal migration so that Deals can reference valid product IDs.

Creatio Orders are order headers containing line items referencing Products, linked to an Account. We map order headers to Pipedrive Deals (or optionally to a separate Orders custom object if the customer licenses Pipedrive's custom objects), and the line items attach as product links to the Deal. Order-to-Product lookup relationships resolve during migration by matching Product names against the migrated product catalog.

Creatio Cases map to Pipedrive Tickets if the customer licenses Pipedrive's Service add-on. Case status, priority, owner, linked Account, linked Contact, and resolution notes transfer. If the Service add-on is not licensed, Cases map to Pipedrive Deals as a custom field tracking case reference, or the customer creates a separate project plan to license Service before migration. SLA timers do not migrate as active timers; they migrate as historical SLA metadata fields.

Creatio's unified Activities object covers tasks, calls, emails, and meetings with a type enumeration field. We split this into Pipedrive's separate Call, Email, Meeting, and Task objects based on the activity type value. The Regarding field (lookup to Account, Contact, Lead, Opportunity) maps to the corresponding Pipedrive object ID (Organization, Person, Lead, or Deal). Activity timestamps and duration fields transfer directly. Email content migrates as the email body field with attachments linked via Pipedrive's file attachment mechanism.

Creatio custom objects created in Studio have user-defined schemas with custom field types. Pipedrive does not support arbitrary custom objects; instead, we map each Creatio custom object to a set of custom fields on the nearest Pipedrive standard object (Person, Organization, Deal) or to a Pipedrive custom object if the customer has licensed that feature on their plan. We perform schema discovery during scoping, extract the field list, and pre-create custom fields in Pipedrive before migration so that field types (text, number, date, dropdown, checkbox) are correctly configured.

Creatio custom fields on standard objects (Accounts, Contacts, Leads, Opportunities, Cases, Activities, Orders) map to Pipedrive custom fields on the corresponding object. Dropdown fields in Creatio with defined value sets map to Pipedrive drop-down fields with the same options. Lookup fields in Creatio referencing other Creatio objects map to text fields in Pipedrive holding the referenced record ID, with a note in the migration guide for the customer to manually link if the target object supports lookups. We create all custom fields in Pipedrive before any data import begins.

Creatio users (owners) map to Pipedrive users by email address. We extract every distinct user referenced on any record and attempt to match by email against the Pipedrive destination. Any Creatio user without a matching Pipedrive user goes into a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive user flags transfer to Pipedrive user status.

Creatio files stored in the database or in external storage (AWS S3, Azure Blob) require extraction before migration. On-site Creatio instances can use Creatio's FileMigrator utility to export files to S3; cloud instances require opening a support ticket with Creatio to initiate file extraction. We coordinate the extraction, re-link files to the corresponding Pipedrive Person, Organization, Deal, or Ticket record after primary data migration is complete, and validate file counts against the Creatio source.