Migrate your Close data

Leads is Close's primary record type for prospects. We migrate Leads with all standard fields (name, email, phone, status, owner) and preserve the lead status label. Where the destination lacks a separate Lead object, we merge Leads into Contacts and carry the original status as a custom Contact property.

Contacts in Close are associated with a company and carry direct contact details. We migrate Contact records with name, email, phone, organisation, and owner assignment. Contacts and Leads share much of the same schema but are queried separately via the API.

Opportunities sit on Pipelines and carry value, stage, expected close date, and owner. We map Opportunity fields 1:1 and preserve the pipeline-stage reference, recreating the pipeline structure in the destination if it does not already exist.

Pipelines are containers for Opportunity stages. We create the Pipeline record first, then map each stage in order. Stage names and ordering are preserved. Custom pipeline columns are carried as Opportunity custom fields if the destination supports them.

Stages belong to a Pipeline and have a display order and optional probability weight. We migrate stage definitions alongside their parent Pipeline and map the stage probability to the destination's close probability field where available.

Activities are the event history attached to a Lead or Contact. Call logs, emails, and SMS are stored as distinct activity types. JSON export captures the full activity array; CSV export omits it entirely. We always request JSON for activity data and chunk records by date range to stay within Close's rate limits.

Custom Fields exist per-object: Lead Custom Fields, Contact Custom Fields, Opportunity Custom Fields. We read the field definition (type, choices, required flag) via the API, then create matching fields in the destination before importing values. Choice-based fields require us to sync the option list explicitly.

Custom Activities are user-defined activity types with their own schema. The parent Custom Activity Type must be created in the destination first. We sequence this: create type, create type-specific Custom Fields, then import activity instances. This is the most complex object to migrate correctly.

Custom Objects are fully user-defined record types introduced for data that does not fit Leads, Contacts, or Opportunities. They require the same two-step approach as Custom Activities — create the Custom Object Type and its Custom Fields before importing instances. Support depends on the destination platform.

Attachments on Leads and Contacts are downloadable via the API. During migration we retrieve them and re-upload to the destination's corresponding record. The attachment file itself is preserved; any in-app annotation or comment on the attachment is not carried.

Smart Views are saved Lead searches with filter criteria. We export the filter configuration as a named saved view. Since Smart Views can only be created from the Leads tab (not the Contacts tab), we note this constraint and replicate the filter logic in the destination's equivalent saved-search feature.

Users in Close carry name, email, role, and team membership. We map Users to the destination's user records but cannot replicate internal permissions, role-based access control settings, or Lead visibility rules without explicit configuration from the customer.

Workflows automate tasks and outreach sequences based on triggers and steps. They are only available on Growth and Scale plans and contain rule logic tightly coupled to Close's event model. We do not migrate Workflows; we flag them during scoping and advise customers to document their active workflows manually for reconfiguration in the destination.

Call recordings are stored in Close and accessible via the API as audio files. We download recordings and upload them to the destination as attachments on the matching activity record. Retention of metadata (duration, date, owner) is preserved through the activity mapping.