Migrate from Bolten CRM to HighLevel

Bolten Contact records map directly to GoHighLevel Contact. We map name, phone (with country code preservation), email, address fields, and all custom properties 1:1. Tags applied to Bolten Contacts migrate as GoHighLevel Contact tags. The bolten_crm_external_id__c field stores the Bolten record ID for dedupe and future delta sync reference. Lead source attribution stored on the Bolten Contact maps to GoHighLevel's dnc_DO_NOT_CONTACT_reason and source_custom field.

Bolten's separate Lead list maps to GoHighLevel Contact records with an optional pipeline assignment flag. If the Bolten Lead has an active deal attached, we create a GoHighLevel Opportunity linked to that Contact and set the pipeline stage at migration time. Leads without deals migrate as Contacts without pipeline association for the customer to route manually post-migration. The original Bolten Lead lifecycle status is preserved in a custom field bolten_lifecycle_stage__c.

Bolten Kanban Deals map to GoHighLevel Opportunities. The deal name, value, currency, and owner migrate directly. The Kanban stage name maps to the GoHighLevel pipeline stage; the stage ordinal position (which Bolten stores in the UI but not the API) is explicitly encoded as the stage rank value in GoHighLevel so that stage order is guaranteed regardless of alphabetical sorting. Closed-won and closed-lost reasons from Bolten custom fields migrate as Opportunity custom fields.

Each Bolten Kanban pipeline maps to a GoHighLevel pipeline. Stage names are encoded as GoHighLevel stage labels, and the stage rank value is set from the ordinal position confirmed during pre-migration scoping. Stage probability percentages are set based on the customer's historical stage-to-close data; we ask for this during discovery and configure the GoHighLevel pipeline probability values before migration begins.

Bolten Tasks with assignee, due date, status, and linked Contact or Deal migrate to GoHighLevel Tasks. Task associations are preserved by resolving the Bolten Contact or Deal ID to the newly created GoHighLevel Contact or Opportunity ID during migration. Recurring task rules in Bolten do not transfer; we flag this for the customer to rebuild in GoHighLevel Workflows post-migration.

Bolten's full change-audit history per record (every edit, assignment, and stage move) migrates as a chronological Activity feed attached to each GoHighLevel Contact and Opportunity. Each audit entry is created as a GoHighLevel Activity with the original timestamp, operator name, and change description preserved. This captures the audit trail that Bolten stores natively without requiring a separate compliance export.

Bolten conversion attribution data (Google, Meta Ads, direct source, UTM parameters) migrates to GoHighLevel Contact custom fields. UTM source and medium values map to utm_source__c and utm_medium__c custom fields. Real-time conversion event flags migrate as boolean or multi-select custom fields depending on the destination schema. We note that UTM attribution may require re-validation in GoHighLevel reporting if the attribution window differs from Bolten's.

Bolten per-object custom fields (text, number, date, dropdown, multi-select) map to GoHighLevel Contact or Opportunity custom fields of equivalent type. Multi-select picklists from Bolten map to GoHighLevel multi-select custom fields. Dropdown fields with defined value sets map to GoHighLevel option-set fields. We pre-create the GoHighLevel custom field schema before migration and flag any Bolten field types with no direct GoHighLevel equivalent (such as AI autofill suggestion logs, which are not stored as accessible field values in Bolten).

Bolten Users are resolved by email match against GoHighLevel Users. Suspended or inactive Bolten users are flagged for remapping to active GoHighLevel users during migration scoping. We do not provision GoHighLevel Users; the customer creates those before migration begins. Inactive Bolten users who are still referenced on records are held in a reconciliation queue until the customer assigns a destination user.

Bolten tags (flat-label strings applied to Contacts and Deals) migrate as GoHighLevel tags. Tag assignment per record is preserved by linking the tag name to the migrated GoHighLevel Contact or Opportunity record. GoHighLevel tags are not hierarchical; if Bolten tags used a hierarchical naming convention, we flatten them to the most granular label and document the original hierarchy for the customer to reproduce in GoHighLevel.