Migrate from SuperOffice CRM to HighLevel

SuperOffice Contact maps to GoHighLevel Contact with all standard fields preserved (name, email, phone, address, custom properties). The SuperOffice Contact ID is stored in a custom field so_origin_id__c for reference and cross-validation. Tags from SuperOffice migrate to GoHighLevel tags via the contact tag export. If the SuperOffice contact has no email address, it is held in a remediation queue because GoHighLevel requires email for Contact import via API.

SuperOffice Company maps to GoHighLevel Company. The Company-Contact relationship is preserved by importing Companies first, then Contacts with company_id resolved via the GoHighLevel API. We use SuperOffice company.name as the GoHighLevel company name field. The so_origin_id__c custom field is applied to Companies as well for reconciliation.

SuperOffice Sales map to GoHighLevel Opportunities. The SaleType and stage values from SuperOffice are exported as a configuration object during discovery, and the customer configures GoHighLevel pipeline stages to match before migration begins. Closed-won and closed-lost reasons from SuperOffice become custom Opportunity fields in GoHighLevel. Amount, expected close date, and sale probability migrate directly.

SuperOffice Quote root records map to the Opportunity in GoHighLevel. The primary QuoteAlternative line items migrate as the Opportunity line items. SuperOffice quote fields (validity period, delivery terms, payment terms) become custom Opportunity fields. Because GoHighLevel does not have a native multi-version quote object, the primary QuoteAlternative is used as the main quote content.

SuperOffice QuoteAlternative structures (the Quote → QuoteAlternative → line item hierarchy supporting multi-version proposals) cannot map to a native GoHighLevel object. The primary QuoteAlternative migrates as Opportunity line items. Secondary QuoteAlternatives are serialized as a JSON blob in a custom Opportunity field called so_quote_alternatives__c, with each alternative named, priced, and dated. The post-migration handoff document enumerates each alternative so the customer's admin can recreate them in GoHighLevel if needed.

SuperOffice Activities (calls, tasks, appointments) linked to Contact or Company records migrate to GoHighLevel Activities. Timestamp, duration, completion status, and description fields transfer directly. Activity associations to SuperOffice Sale records are preserved by linking the Activity to the corresponding migrated Opportunity. We sample 25-50 activity records post-import to verify association accuracy.

SuperOffice email activities linked to Contacts, Companies, or Sales migrate to GoHighLevel Activity records. Email subject, body, direction (sent/received), and timestamp transfer. Email attachments are exported as file references in the activity notes, with the customer informed that files need a separate migration step via GoHighLevel's document import.

SuperOffice Projects have no native GoHighLevel equivalent. We migrate Projects as a GoHighLevel Custom Object that the customer admin must create before migration begins. Project type and status from SuperOffice's ProjType and ProjStatus list tables become custom fields on the Custom Object. The admin configures any lookup relationships (e.g., Project to Contact or Opportunity) in GoHighLevel before we import. We flag this as a required pre-step during scoping.

SuperOffice Selections are named dynamic lists of Contacts, Companies, or Sales. GoHighLevel has no native dynamic list equivalent. We export Selection membership as tagged records: each Contact in a Selection receives a tag prefixed with the Selection name (e.g., enterprise-clients-qualified). Static Lists in GoHighLevel can be built from these tags post-migration. The selection-membership cross-reference is stored in the post-migration handoff document.

SuperOffice userDefined table custom fields on Contacts, Companies, Sales, and Projects map to GoHighLevel custom fields on the equivalent object. Dropdown list values from SuperOffice (list table entries) must be recreated as GoHighLevel custom field options by the admin before migration because GoHighLevel does not auto-create picklist values. Free-text and numeric custom fields map directly with type matching.