Migrate from Close to HighLevel

Close's Lead is the primary record container for B2B — it holds the company name, status, and owner. We map Close Lead to GoHighLevel Contact as the primary record, with the company name stored on the Contact record or linked to a GoHighLevel Company where the customer uses both objects. The Close Lead status label migrates as a GoHighLevel Tag or Contact Custom Field. Any Close Lead with multiple associated Contacts is handled as a primary Contact plus additional Contact records, all linked to the same GoHighLevel Opportunity.

Close Contacts are person-level records nested inside a parent Lead. We flatten them into standalone GoHighLevel Contact records linked back to the parent Company. The Contact's name, email, phone, and title migrate directly. If a Close Contact is the primary contact on an Opportunity, that relationship is preserved by linking the Contact to the corresponding GoHighLevel Opportunity record.

Close Opportunities sit on Pipelines and carry value, stage, expected close date, and owner. We map Opportunity fields to GoHighLevel Opportunity, preserving the monetary value, probability (as a GoHighLevel custom field since GHL Opportunity does not have a native probability field), and expected close date. The Opportunity's parent Lead becomes the GoHighLevel Contact and Company link. Owner assignment resolves via email match against GoHighLevel Users.

Close Pipelines are containers for Opportunity stages and are recreated as GoHighLevel Pipelines before any Opportunity records are imported. Pipeline name, display order, and stage structure are preserved. GoHighLevel Pipelines are created under Settings > Pipeline before migration begins, and the pipeline ID is captured in the source-to-target crosswalk for stage resolution.

Each Close Pipeline stage maps to a GoHighLevel Pipeline stage with its display order and stage name preserved. Stage probability from Close (if used) migrates as a GoHighLevel Opportunity custom field since GHL Pipelines do not have a native probability-per-stage model. Stage status options (won, lost, open) are mapped to GoHighLevel's stage status labels.

Close call activities include call disposition, duration, recording URL, and transcript (if available). We export via JSON to capture the full call log. Calls migrate to GoHighLevel as Tasks with call type, or as Conversations linked to the Contact record. Call recordings are downloaded from Close and uploaded as GoHighLevel attachments on the matching activity record. The original timestamp is preserved to maintain the activity timeline order.

Close email activities store body content, direction (sent/received), and participant addresses. Rich text and HTML emails are preserved as GoHighLevel Conversation entries or as Note records with full body content. The linked Contact reference is resolved via the source-to-target ID crosswalk. Attachments on emails migrate as separate file attachments in GoHighLevel.

Close SMS activities include message body and any attachments. We map SMS to GoHighLevel Conversations on the Contact record. If the SMS has media attachments, they are uploaded to GoHighLevel's Media Library and linked to the Conversation. SMS direction and timestamp are preserved in the Conversation metadata.

Close Tasks (standalone task records not tied to a call or email) migrate to GoHighLevel Tasks. Task title, body, due date, status, and assignee migrate directly. Assignee resolution uses email-to-User mapping. Completed tasks retain their completion timestamp; open tasks retain their due date.

Close Lead Custom Fields map to GoHighLevel Contact Custom Fields. We read the Close field type (text, number, date, dropdown, checkbox) and create the matching GoHighLevel field type under Settings > Custom Fields > Contact before migration. Choice-option labels from Close dropdowns are preserved as GoHighLevel field options. Note: GoHighLevel Custom Fields must be designated as Contact or Opportunity at creation and cannot be changed after. We confirm this designation with the customer during scoping.

Close Opportunity Custom Fields map to GoHighLevel Opportunity Custom Fields. Field type and choice options are preserved. GoHighLevel Opportunity custom fields appear only within the Opportunity record and do not surface on Contact records, so field placement is confirmed against the customer's reporting requirements during scoping.

Close Custom Activities are user-defined event types with their own schema and type-scoped Custom Fields. GoHighLevel does not have a direct Custom Activities equivalent, but Custom Objects can be used to represent custom event types. We assess whether the customer's Custom Activity data is reportable (requiring a Custom Object) or archival (better represented as Note records with structured field values). The decision is made during scoping based on how the customer uses the data.

File attachments on Close Leads and Contacts are downloaded via the Close API and re-uploaded to GoHighLevel as Contact attachments or Media Library files. Large files (>10MB) are handled via the GoHighLevel Media Library API. If a file was linked to a specific activity, it is re-linked to the corresponding migrated activity record.

Close Users carry name, email, role, and team membership. We map Users to GoHighLevel Users by email match. Any Close User without a matching GoHighLevel User is held in a reconciliation queue for the customer to provision before record import resumes. Role and permission settings do not migrate; we document the original role assignments for the customer to reconfigure in GoHighLevel.