Migrate from Close to Pipedrive

Close Leads with status Unqualified or Not Contacted map directly to Pipedrive Lead. We preserve the Close lead status label as a custom field on the Pipedrive Lead. Leads that are already converted in Close (status set to Customer) require a split decision: they either become Pipedrive People attached to an Organization, or they remain as closed Leads depending on the customer's go-forward pipeline definition. We resolve this during scoping by reviewing the customer's Close lead-status configuration.

Close Contacts map to Pipedrive Person. The Close contact organisation field maps to Pipedrive's Organization lookup. If a matching Pipedrive Organization does not exist at migration time, we create it first to satisfy the lookup dependency. Name, email, phone, and address fields migrate 1:1. Any Contact in Close that has no organisation set maps to a Person with no Organisation linkage, which we flag for manual enrichment post-migration.

Close Contacts carry an organisation field that we extract and dedupe before creating Pipedrive Organizations. Organization name becomes the Pipedrive Organization name. Website, industry, address, and phone migrate to matching Pipedrive Organization fields. The Organization is created before any Person import so that the Organisation lookup is satisfied at the moment of Person insert.

Close Opportunities map to Pipedrive Deals. The pipeline and stage reference from Close becomes the Pipedrive pipeline name and stage label. Deal value, expected close date, and owner migrate directly. Closed-won and closed-lost reasons from Close custom fields map to Pipedrive Lost Reason if configured in the destination pipeline settings.

Each Close pipeline becomes a Pipedrive Pipeline. We create the pipeline in Pipedrive first, then map each Close stage to a Pipedrive stage with matching label and display order. Stage probability percentages from Close migrate to Pipedrive's stage probability where supported. If Close has more stages than the destination pipeline supports, we merge adjacent stages and document the consolidation.

Close call activities migrate to Pipedrive Activities with type = Call. The call outcome, duration, and recording URL from Close's JSON export map to Pipedrive Activity fields. Activity date and time are preserved. We resolve the parent Contact or Lead reference to the correct Pipedrive Person or Lead using the email address as the dedupe key.

Close email activities migrate to Pipedrive Activities with type = Email. Subject, body (plain text), and sent/received status transfer. Email direction (inbound/outbound) is stored in a custom field if the destination pipeline does not have a built-in direction flag. We resolve the parent Contact or Lead reference to the correct Pipedrive Person or Lead by email match.

Close SMS activities migrate to Pipedrive Activities with type = SMS. Message content and direction migrate. We resolve the parent Contact or Lead to the correct Pipedrive Person or Lead by phone number match where email is unavailable. Pipedrive does not have a native SMS activity type by default; we configure a custom activity label or use the note field if the customer's plan does not support custom activity types.

Close tasks migrate to Pipedrive Activities with type = Task. Subject, due date, status, and assignment migrate directly. Completed tasks preserve the completion timestamp. Task priority maps to Pipedrive's priority flag. We resolve the assigned owner from Close's owner email to the Pipedrive user by email match.

Close Custom Fields attached to Leads, Contacts, and Opportunities are read via the API with their type (text, number, date, dropdown, checkbox) and choice labels preserved. We create matching custom fields in Pipedrive using the same type where available, or the closest Pipedrive equivalent. Dropdown fields use the same choice labels. Required flag and display-in-add-view settings are migrated. Custom fields are created before any record import so that the field IDs are available at insert time.

Close Custom Activities require a three-phase import: create the Custom Activity Type, create type-scoped Custom Fields, then import the activity records. In Pipedrive, we replicate this by creating a named Activity with a custom activity_label and type-specific custom fields. We preserve the activity date, the parent Lead/Contact reference, and all type-scoped field values. If the destination Pipedrive plan does not support custom activity types, we attach the activity data as a Note on the related Person or Lead and flag the limitation for the customer's admin.

Close attachments on Leads and Contacts are retrieved via the API as files and re-uploaded to Pipedrive as attachments on the matching Person or Lead. The original filename and MIME type are preserved. We cannot migrate attachment visibility settings or sharing rules; all migrated attachments are private to the record owner post-migration. Attachments on Opportunities migrate as Deal attachments if the destination Pipedrive plan supports deal-level attachments.

Close call recordings are retrieved as audio files and uploaded to Pipedrive as attachments on the matching Activity record. The activity is identified by resolving the call timestamp, caller phone, and parent Contact/Lead to the correct Pipedrive Activity and Person. If the activity cannot be resolved, the recording is attached to the Person record directly with a note indicating the original call date and duration.

Close Smart Views are saved Lead searches with filter criteria. We export the filter configuration as a named saved filter in Pipedrive. Since Close Smart Views can only be exported from the Leads tab, we use the API to query Contacts directly and preserve the filter logic as Pipedrive saved filters on People. The filter criteria are translated to Pipedrive's filter expression format. We flag any filter criteria that cannot be replicated in Pipedrive for manual recreation.

Close Users map to Pipedrive Users by email address. We extract every distinct Close user referenced on Leads, Contacts, Opportunities, and Activities and match by email against the Pipedrive destination user list. Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before record import resumes. Role and team membership from Close do not transfer; Pipedrive roles and visibility are set up post-migration.