Migrate from Salesboom to HighLevel

Salesboom Leads map to GoHighLevel Contact records. The Lead's email, phone, company name, status, source, and rating migrate directly. GoHighLevel does not have a separate Lead object; all prospect records live as Contacts. We preserve the original Salesboom Lead status in a custom Contact field (e.g., sb_lead_status__c) for reporting continuity. Custom Lead fields migrate to GoHighLevel Contact custom fields, and any sales rep assignment maps to the GoHighLevel User assigned to that Contact.

Salesboom Accounts represent company-level records with hierarchy, billing/shipping addresses, and industry data. GoHighLevel has no standalone Account object; company data attaches to a Contact as a Location. We map the primary Account name to the Contact's primary company name field, billing/shipping addresses to Location records under that Contact, and industry/sic codes to custom Contact fields. Multi-location accounts create multiple Location records on a single Contact. The split requires customers to choose which Contact represents the primary account holder.

Salesboom Contacts map directly to GoHighLevel Contacts, preserving name, email, phone, address, title, department, and any custom Contact fields. The Contact-to-Account association from Salesboom is resolved into the Contact's primary company name and Location fields in GoHighLevel. GoHighLevel distinguishes between Contact custom fields and Opportunity custom fields; we pre-create the destination custom fields during schema setup and map each Salesboom field to the appropriate GoHighLevel field type.

Salesboom Opportunities map to GoHighLevel Deals with stage, amount, close date, probability, and owner preserved. The Salesboom pipeline assignment maps to a GoHighLevel Pipeline with its own stage values. Closed-Won and Closed-Lost reasons from Salesboom custom properties migrate to custom Deal fields. GoHighLevel Deal probability is set per-stage within each Pipeline configuration.

Salesboom Tasks migrate to GoHighLevel Tasks, preserving subject, status, priority, due date, assigned owner, and any related Contact or Opportunity reference. GoHighLevel Tasks attach to the migrated Contact record via the contact_id reference. We resolve Salesboom task owners to GoHighLevel Users by email match. Recurring Salesboom tasks are flattened into individual task records.

Salesboom Notes attach to any parent record (Account, Contact, Opportunity) and migrate as GoHighLevel Notes attached to the corresponding Contact or Deal. Rich-text formatting in Salesboom Notes is preserved as plain text in GoHighLevel to ensure compatibility. Note ownership resolves to the GoHighLevel User by email match.

Salesboom Cases (ticket-style support records) map to GoHighLevel Tasks with a custom Case status field if the customer does not use a separate support tool. For customers that plan to use GoHighLevel's inbox or a connected support tool, Cases migrate to a custom object that mirrors the Case schema. Auto-assignment rules and escalation workflows from Salesboom do not migrate; we document these in the automation inventory for rebuild.

Salesboom allows unlimited custom fields on any standard tab with no per-field cost. GoHighLevel supports Contact custom fields and Opportunity (Deal) custom fields separately, with a once-created, not-switchable constraint. We pre-create all destination custom fields before migration, mapping each Salesboom field to the correct GoHighLevel object and field type. The mapping phase resolves data type differences (e.g., Salesboom date fields become GoHighLevel date fields; multi-select picklists become GoHighLevel multi-select options).