Migrate from Cordis CRM to Pipedrive

Cordis CRM Contacts (marketed as Profiles in the platform UI) map directly to Pipedrive People. Standard fields including name, email, phone, address, and owner assignment migrate via CSV or API insert. The dedupe key is email address. Custom contact properties are identified during scoping and mapped to Pipedrive custom fields, which are created with matching data types before import. Any Cordis contact linked to a Company exports a relationship that we remap to the corresponding Pipedrive Organization using company-name matching.

Cordis CRM Company records map to Pipedrive Organizations. The company name becomes the Organization name, domain becomes the website field, and industry or type properties map to Pipedrive custom fields where no native equivalent exists. We export the contact-company relationship graph and re-establish it in Pipedrive by resolving Organization IDs at insert time. Parent-company hierarchy in Cordis, if present, maps to the Organization's parent_id field in Pipedrive.

Cordis CRM pipeline stages map to Pipedrive Pipeline stages. The stage names and order are preserved from the customer's configured pipeline, with stage probability percentages migrated to Pipedrive's stage probability settings. Pipedrive supports multiple pipelines on all paid tiers; if Cordis CRM has multiple pipelines, each becomes a separate Pipedrive Pipeline. Stage mapping is validated against Pipedrive's allowed stage name lengths and character set during the transform phase.

Cordis CRM Deals map to Pipedrive Deals. Each Deal carries a title, value, currency, owner, stage, and expected close date. The Cordis pipeline stage assignment determines the Pipedrive Pipeline and stage assignment. If Cordis CRM stores close reason (won or lost) as a custom property, we map it to Pipedrive's Lost or Won status and preserve the original reason in a custom field. Activities linked to a Deal are migrated separately and re-associated via activity_id in Pipedrive.

Cordis CRM Tasks map to Pipedrive Activities with Task type. Status (open, completed), priority, due date, and owner assignment migrate directly. Recurrence rules from automated Cordis tasks are flagged in the migration inventory for the customer's admin to rebuild in Pipedrive's workflow automation since recurrence is a configuration rather than a data record. Tasks linked to Contacts, Companies, or Deals are re-associated using the ID mapping table generated during record insertion.

Cordis CRM Campaigns with member contacts map to Pipedrive Lists. Campaign membership (which contacts are enrolled) translates to List membership in Pipedrive. Note that Pipedrive Lists are static segments for targeting rather than automated enrollment; if Cordis uses Campaigns as enrollment-based sequences, those migrate as a written inventory for the customer's admin to rebuild using Pipedrive's automation features. Campaign engagement data (opens, clicks) does not have a direct Pipedrive equivalent and is preserved in the migration inventory as a reference document.

Cordis CRM documents attached to Contact, Company, or Deal records are exported individually as files. We handle filename preservation and re-associate each file post-import using the record ID mapping table. Document version history is not guaranteed to export as a complete lineage; we extract the latest version of each document and flag any records with multiple versions for the customer's admin to decide whether earlier versions require manual restoration. Files are attached via Pipedrive's file upload API or linked as Google Drive attachments if the customer maintains that integration.

File attachments linked to Cordis CRM records are exported with filename and MIME type preserved. We re-associate attachments to the migrated Pipedrive records using the ID mapping table generated during insertion. Large file attachments are handled in batches to avoid API timeout. Any attachment exceeding Pipedrive's file size limit is flagged and the customer decides whether to store externally and link, or to truncate.

Cordis CRM custom fields are identified during scoping by surveying the customer's instance, since the platform does not publicly document custom field data types or naming conventions. Each identified custom field is created in Pipedrive with the appropriate field type (text, numeric, date, dropdown, multi-select, checkbox, phone, email, address, or organization link) before any record import begins. Custom field mapping decisions are documented in the migration scope and validated during sandbox migration before production cutover.

Cordis CRM Owners referenced on Contacts, Companies, Deals, and Tasks are mapped to Pipedrive Users by email address. Owners without a matching Pipedrive User are placed in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Cordis CRM owners are mapped to inactive Pipedrive users where the customer requires historical owner assignment preserved.