Migrate from Contlo to Pipedrive

Contlo Contacts map directly to Pipedrive People. Email, name, phone, address, and custom properties migrate 1:1 to Pipedrive standard and custom Person fields. We use email as the dedupe key. Any Contlo Contact without an email address is held in a reconciliation queue; Pipedrive requires an email or name for Person creation via API. Segment membership is preserved as Tags on the Person record (see Segments mapping). Owner resolution uses email match against Pipedrive Users.

Contlo Segments are behavioral groupings used to target automations. Pipedrive has no native Segment object; we convert segment membership to static Tags on the Person record. Each Contlo Segment becomes a Tag with the segment name as the tag label. Segment rules (AND/OR filter logic, behavioral conditions) do not migrate as active rules; we document each segment's definition with its filter criteria so the customer's admin can rebuild equivalent Pipedrive filter views or automation triggers. Segment counts per contact are preserved in a custom field segment_count__c for reporting.

Contlo Campaign metadata (name, type, status, send date) migrates as a Note attached to each Contact in the campaign audience. Campaign template content does not migrate as a reusable template in Pipedrive, which does not have a native email template library at Lite and Essential tiers. We deliver a written inventory of all campaign templates with subject lines and body content for manual re-creation in Pipedrive or an integrated email tool. Open, click, and conversion event data from Contlo's analytics export becomes custom fields on the Person record (last_email_open__c, last_email_click__c, conversion_date__c).

Contlo automations are event-triggered sequences with branching, delays, and multi-step actions. Pipedrive automations use a trigger-action format with simpler branching. We extract each automation's trigger type, conditions, and action steps as structured data and deliver a written automation inventory with a recommended Pipedrive Workflow equivalent. Complex branching logic with multi-path conditions does not migrate as active Pipedrive automations and requires manual rebuild. The automation inventory includes trigger events, filter conditions, action types, and delay durations.

If the customer uses Contlo's Deal object (Growth and Enterprise tiers), Deals map to Pipedrive Deals with the Organization resolved via domain-matching or manual mapping during scoping. Deal stage, value, currency, expected close date, and owner migrate to Pipedrive standard Deal fields. Pipedrive Deal required fields (title, visible_to) are satisfied by the migration config. We flag any Contlo Deals without a linked Contact or Organization for manual resolution before import.

Contlo does not have a native Organization object, but Company-level data can exist in custom fields on Contacts. If the customer has company-level data in Contlo, we extract unique company names and domains and create Pipedrive Organization records, then link the Contact's Person record to the Organization via the Organization ID resolved at migration time. This step is gated on whether the customer has company data in Contlo; we confirm during scoping.

Contlo Products (if used in Deal line items) map to Pipedrive Products with name, code (SKU), and price. Products must be created in Pipedrive before Deal import if the Deals contain product line items, so that the Product ID reference is satisfied at migration time.

Contlo custom fields on Contacts migrate to Pipedrive custom Person fields. We pre-create the custom field schema in Pipedrive before migration, using the closest Pipedrive field type: text for strings, number for integers, date for dates, single-select for enumerated strings, and multi-select for multi-value properties. Custom fields that do not map cleanly to a Pipedrive type are stored as a JSON blob in a text custom field with documentation of the original structure.

Contlo event-level data (opens, clicks, conversions) exports as CSV tied to Contact IDs. We map these to custom fields on the Pipedrive Person record: last_open_date__c, last_click_date__c, last_conversion_date__c, email_open_count__c, email_click_count__c, sms_open_count__c. The full event log CSV is delivered as a reference file for the customer to retain outside Pipedrive. Pipedrive's reporting does not natively consume time-series event data, so the CSV serves as the audit trail.

Contlo Voice Agents are AI-driven phone agents built from Contlo's library. Agent configuration, voice settings, and routing logic are extracted as structured JSON data. Voice Agents have no Pipedrive equivalent; the configuration document is delivered as a handoff artifact for the customer's admin to evaluate in a contact center tool (e.g., Twilio Flex, Intercom, or a dedicated voice platform). Voice routing logic is documented but not migrated.