Migrate from Cirqll to Pipedrive

Cirqll Customer records map to Pipedrive Person objects with full field fidelity including name, email, phone, and address fields. We resolve the email address as the dedupe key during import to prevent duplicate Person records. Cirqll custom properties on Customer migrate as Pipedrive custom fields if the customer's Pipedrive plan supports them (all paid plans include custom fields). Note that Pipedrive Persons are optionally linked to an Organization; we set this relationship during the Organization mapping phase.

For Cirqll Customers that represent companies (business name in the name field, or a domain-based email pattern), we create a Pipedrive Organization record first, then link the Person to it. This is a judgment call based on field inspection during the data audit phase; we document the rule and apply it consistently across all records to avoid mixed mappings.

Cirqll Lead records migrate 1:1 to Pipedrive Lead objects. Qualification status, source attribution, and owner assignment transfer as custom fields or standard Pipedrive Lead fields depending on what is present in Cirqll's schema. Pipedrive Lead custom fields share the same field space as Deal custom fields, so any Cirqll Lead custom properties must be checked for naming conflicts against existing Deal fields.

Cirqll Activity records (calls, emails, meetings) map to Pipedrive Activity objects with the Activity type set to call, email, or meeting. Timestamps, duration, and related Contact or Lead references preserve. The Pipedrive Activity must link to a Person or Organization record; we resolve the WhoId by matching the related Cirqll Customer or Lead email to the migrated Pipedrive Person or Lead.

Cirqll Task records (due date, assignee, priority flag, completion status) map to Pipedrive Activity with type = task. Open and completed task states carry forward as done = true or done = false. Assignee maps by email lookup to the destination Pipedrive User.

Cirqll free-text Notes attached to Customers or Leads migrate to Pipedrive Note records linked via ContentDocumentLink to the parent Person, Organization, Deal, or Lead. Creation timestamp and author attribution preserve. Pipedrive Note records are visible in the activity timeline of the linked record.

Cirqll Calendar Events migrate with date, time, title, and attendee list. All-day event flags and recurrence patterns require field-level mapping because Pipedrive Activity does not natively support recurrence; recurring events from Cirqll become a series of individual Pipedrive Activity records with a shared custom recurrence_id field for grouping.

Cirqll documents are binary blobs that do not export via the standard API. We flag this during scoping as a secondary pass: Cirqll's document storage must be accessed via a download-and-reupload workflow, either through Cirqll's UI export or a direct database export if available. We handle this as a separate line item in the migration scope, preserving original filenames and upload timestamps. Document version history does not transfer.

Cirqll User accounts and their assignment to Leads, Tasks, and Activities migrate as owner mappings to Pipedrive User records. Active versus inactive status carries forward. Role-based permissions do not transfer because Pipedrive uses a different permission model; the customer's Pipedrive admin configures access roles post-migration. Any Cirqll User without a matching Pipedrive User goes to the reconciliation queue for admin provisioning before record import.

Cirqll's Lead-to-Customer conversion events are preserved as an Activity record on the migrated Person or Lead in Pipedrive, noting the conversion date and original Lead status. This is informational only; Pipedrive does not have a native conversion event object, so we represent it as a dated activity note for audit purposes.