Migrate from Cloze to Pipedrive

Cloze People map to Pipedrive Person records. Email address is the dedupe key for import. Standard properties (name, email, phone, address, social links) migrate directly. We preserve Cloze's relationship score in a custom field cloze_score__c if the customer requests it. Organization linkage in Cloze (Person tied to a Company) maps to Pipedrive's Person.OrgId lookup; we resolve by email domain match against imported Organizations.

Cloze Companies map to Pipedrive Organizations. Domain name is the dedupe key. We import Organizations before People so the OrgId lookup is satisfied at the moment of Person insert. Cloze's Company-specific fields (industry, employee count, address) map to Pipedrive Organization standard fields or custom fields created to match.

Cloze Projects (Deal/Property aliases) map to Pipedrive Deals. The Cloze Stage (Potential, Active, Done, Lost) maps to Pipedrive Stage, but stage values must be configured in Pipedrive's pipeline settings before import. We strip any hardcoded real estate terminology (Property, Listing) from stage labels and normalize to the customer's chosen Pipedrive stage names. Deal value, expected close date, and custom project fields migrate directly.

Each Cloze pipeline becomes a Pipedrive Pipeline with corresponding Stage values. Cloze's Stage order (Potential > Active > Done/Lost) maps to Pipedrive stage order with probability percentages computed from Cloze's stage probabilities if available. If Cloze's stage probabilities are not exposed in export, we apply default probabilities and the customer adjusts post-migration.

Cloze Segments and Audiences group contacts by Stage or custom criteria. We preserve segment membership by mapping each Person's stage and tag assignments to Pipedrive Tags. The customer chooses during scoping whether segment membership becomes Pipedrive Tags (native) or a multi-select custom field (better for reporting). Both options are supported; Tags is the default unless the customer specifies reporting-first segmentation.

Cloze call logs migrate to Pipedrive Activities with type = Call. We map call duration, disposition, and timestamp to Pipedrive Activity fields. Activity is linked to the parent Person or Organization by resolved ID. If Cloze records a call without a linked Person, the activity migrates as a standalone Activity linked to the associated Deal if one exists.

Cloze email records migrate to Pipedrive Activities with type = Email. Subject, body, and timestamp transfer; full email content is migrated if the content length is within Pipedrive's field limits. Emails without a linked Person or Organization are linked to the associated Deal if one exists. We flag any emails with truncated content due to Cloze's storage policy during extraction.

Cloze meeting entries migrate to Pipedrive Activities with type = Meeting. Start time, end time, location, and attendees transfer. If attendee email addresses are present, we attempt to link them to migrated Person records. Meeting content or agenda notes migrate to the Activity description field.

Cloze Notes migrate to Pipedrive Note objects linked to the parent Person, Organization, or Deal. We preserve note content, creation date, and the Cloze user who created the note. If the note references other People or Deals, we include that context in the note body since Pipedrive Notes do not support cross-record lookups.

Cloze text message records (SMS) do not have a native equivalent in Pipedrive's activity model. We migrate text content as Pipedrive Note objects with a prefix tag [SMS] in the note title and link them to the parent Person or Organization. The customer should confirm whether SMS history is business-critical before committing to this approach.

Cloze custom fields on People, Companies, and Projects migrate to Pipedrive custom fields of matching type. Cloze field types (text, number, date, choice) map to Pipedrive field types (varchar, numeric, date, enum). We pre-create all custom fields in Pipedrive before any data import so that field IDs are available during the load phase. Deprecated or deleted Cloze custom fields are flagged and excluded from the field mapping workbook.

Cloze Tags are flat labels applied to People and Companies. We preserve all tag assignments by creating matching Tags in Pipedrive and linking them to the migrated Person or Organization records. Pipedrive's tag model supports unlimited tags per record, matching Cloze's flexibility.

Cloze Teams control access and assignment. We map team membership to Pipedrive Users with matching email addresses. Role assignments (Admin, Manager, Member) map to Pipedrive permission levels; Cloze Admin maps to Pipedrive admin users. If a Cloze team member has no corresponding Pipedrive User, we hold the assignment in a reconciliation queue for the customer's admin to provision before final migration.

Cloze Campaigns are only available on the internal Business Platinum plan. We preserve campaign definitions (name, audience, trigger logic, sequence steps) as a custom migration document, not as active Pipedrive Campaigns. The Pipedrive Campaigns add-on (Growth and above, $13.33/company/month) must be purchased to activate campaign functionality. We deliver a written rebuild guide mapping each Cloze Campaign step to the Pipedrive Campaigns workflow equivalent.