Migrate from HighLevel to Nutshell

HighLevel Contacts map to Nutshell Contacts. Standard fields (first_name, last_name, email, phone, address) migrate directly. HighLevel's lifecycle_stage property maps to a custom text field hgl_lifecycle_stage__c in Nutshell because Nutshell does not have a lifecycle model. Tags migrate as a comma-separated multi-select field; we truncate to Nutshell's 255-character field limit and flag any contact with tags exceeding that length for manual review.

HighLevel Companies map to Nutshell Accounts. The Company name becomes Account name, domain becomes Website, and industry and employee count map to custom fields. Nutshell requires Accounts to exist before Contacts are linked, so we migrate all Accounts first in a dependency-ordered pass before the Contact phase begins.

HighLevel Contacts with a linked Company require AccountId resolution during migration. We extract the HighLevel contact-company relationship from the API, create the Account in Nutshell first, then insert the Contact with the resolved AccountId reference. This is the step most naive CSV imports skip, resulting in orphan Contacts in Nutshell with no Account link.

HighLevel Opportunities map to Nutshell Opportunities. The Opportunity name, amount, expected_close_date, and stage (dealstage) migrate directly. The linked Contact and Company become Nutshell's ContactId and AccountId lookups. We resolve these parent references before Opportunity insert to avoid orphaned opportunity records.

HighLevel pipeline stages map to Nutshell Stage values on the Opportunity. We create Nutshell Sales Processes matching the HighLevel pipeline structure, preserving stage order and names. Probability percentages from HighLevel map to Nutshell's stage probability field. Each HighLevel pipeline becomes a separate Nutshell Sales Process.

HighLevel Custom Objects require schema introspection before migration. We inspect the custom object's field types and data, then map them to Nutshell custom fields (text, number, date, picklist, multi-select) on the nearest standard object (Contact, Account, or Opportunity). If the custom object has relationships to standard objects, we replicate those as lookup fields in Nutshell. Complex multi-level custom object hierarchies may require partial manual mapping.

HighLevel tags are flat string labels applied to Contacts. We consolidate all unique tag values from the source export, create a Nutshell custom multi-select field to hold them, and map each Contact's tag list during import. Tags exceeding Nutshell's 255-character field limit are split across a secondary tag field with a flag for manual consolidation.

HighLevel Tasks linked to Contacts or Opportunities migrate to Nutshell Tasks. Task name, due date, completion status, and assignment migrate directly. We resolve the assigned user by email match against Nutshell's User table and resolve the related Contact or Opportunity reference before insert.

HighLevel Users (agency staff and sub-account owners) map to Nutshell Users by email address. Any HighLevel User referenced in an assigned field without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision. Inactive Nutshell users can receive migrated records if the admin enables the user or reassigns ownership.