Migrate from Corteza CRM to Pipedrive

Corteza Lead records map directly to Pipedrive Lead objects. Standard fields (first name, last name, email, phone, title, company name) migrate directly. The Lead conversion workflow in Corteza creates Accounts, Contacts, and Opportunities in sequence; in Pipedrive, Leads have a separate lifecycle from Deals and can be converted to People (Contacts) attached to Organizations (Accounts) at any time. We preserve any lead rating, lead status, or source fields from Corteza as custom fields in Pipedrive Leads.

Corteza Account records map to Pipedrive Organization. The company name, industry, website, address fields, and social media URLs migrate as standard Pipedrive Organization fields. Account is the parent entity for Contact records in both systems; we create Organizations first in the migration sequence so that the Organization ID is available for Contact linkage. Any Corteza custom fields on Account (such as employee count or annual revenue) migrate as Pipedrive custom fields on Organization.

Corteza Contact records map to Pipedrive Person. Standard fields (first name, last name, email, phone, job title) migrate directly. The contact-account relationship maps to the Person-Organization link in Pipedrive by resolving the Corteza parent Account reference to the migrated Organization ID. If the original Contact has no Account in Corteza, the Person is created without an Organization link and flagged for the customer to resolve post-migration.

Corteza Opportunity records map to Pipedrive Deal. Stage, amount, probability, close date, and owner migrate as standard Deal fields. The opportunity-account relationship maps to Deal-Organization linkage. Close date and stage transition dates from Corteza become visible in Pipedrive's Activity section and deal timeline. Pipedrive's Deal object has no native probability field at the deal level; probability mapping requires a custom field or rule configuration based on stage.

Each distinct stage value in the Corteza Opportunity module becomes a stage within a Pipedrive Pipeline. We create the Pipedrive Pipeline before migration, define the stage names matching the Corteza stage labels, and configure open/closed/won/lost flags per stage. Stage probability percentages from Corteza can be preserved as custom deal fields or used to configure Pipedrive's revenue forecast if the Advanced tier or above is licensed.

Corteza Campaign records have no direct Pipedrive object equivalent. CampaignMember linking Contacts and Leads to Campaigns cannot be preserved as a native association in Pipedrive without custom objects or a workaround using deal-product relationships or tags. We document the full Campaign and CampaignMember structure from the source for the customer's admin to rebuild in Pipedrive using Products, Labels, or a third-party marketing integration (such as a connected HubSpot Marketing instance) post-migration.

Corteza Case records (support issue tracking) have no native Pipedrive equivalent; Pipedrive's core product is sales-focused and does not include a native service desk object. Cases migrate as Deal records with a custom case_type__c field, or as Notes attached to the relevant Organization or Person. The customer should evaluate whether a separate helpdesk tool (Zendesk, Freshdesk) is needed if case management is a core function. We preserve case status, priority, origin, and resolution fields as custom fields on the target object.

Corteza Contract and ContractLineItem records have no native Pipedrive equivalent. Contracts migrate as Deals with a contract_reference__c custom field and terms stored as a Note attached to the Deal or Organization. If the customer uses Pipedrive's Advanced tier or above, Products can serve as a lightweight substitute for ContractLineItem tracking. ContractContactRole relationships from Corteza migrate as Notes on the relevant Person or Organization record.

Corteza Quote and QuoteLineItem records have no native Pipedrive equivalent. Quote records migrate as Deals with quote reference metadata in custom fields; QuoteLineItem relationships are preserved as Notes or as Product-linked Deal entries if Pipedrive Products are configured. Pipedrive's Smart Docs add-on (Professional tier and above) handles proposal and quote document creation post-migration, but the historical quote data requires a custom handling approach.

Corteza Product records map to Pipedrive Products. Standard fields (product name, code/SKU, description, unit price) migrate as standard Pipedrive Product fields. Pricebook and PricebookEntry pricing tiers from Corteza can be stored as multiple price entries on the Pipedrive Product. The product catalog must be migrated before any Deal or Quote records that reference them.

Corteza Task records map to Pipedrive Activities. Standard fields (subject, due date, status, assignee, description) migrate directly. Task assignments resolve by matching Corteza assignee user references to Pipedrive User records by email. Open tasks migrate with the due date preserved; completed tasks migrate with their completion date and status flag. Tasks related to specific parent records (Opportunity, Account, Contact) are linked to the migrated Pipedrive equivalent using the activity_id and associated deal_id or person_id.

Corteza Event records (meetings and calls) map to Pipedrive Meeting activities. Start datetime, duration, location, and description migrate directly. Organizer and attendee references resolve by email against the migrated User and Person records. Events without attendee data migrate as standalone Meeting activities attached to the relevant Deal or Organization.

Corteza Note records migrate as Pipedrive Notes attached to the relevant Person, Organization, or Deal. The note body, creation timestamp, and owner migrate directly. Notes linked to multiple parent records in Corteza (a known edge case in Corteza's data model) create multiple Pipedrive Notes attached to each relevant entity to preserve the association.

Corteza custom modules created via the low-code builder require schema analysis before mapping. If the custom module mirrors a standard object (Account, Contact, Opportunity), its fields migrate as Pipedrive custom fields on the equivalent standard object. If the custom module is a standalone entity with no Pipedrive equivalent, we create a Product entry or a Deal with a custom object name field to serve as a placeholder, and document the full schema for the customer to evaluate Pipedrive's custom object capabilities or a supplemental tool.