Migrate from OplaCRM to HighLevel

OplaCRM Accounts map directly to GoHighLevel Contacts with the Company toggle enabled. The account name becomes the Contact's company name field, and address data maps to GoHighLevel's address compound fields. We use the account external_id as GoHighLevel's custom identifier for deduplication. If multiple OplaCRM Accounts share the same domain or name, we flag them during pre-flight for the customer to resolve before import to avoid duplicate GoHighLevel Contacts.

OplaCRM Contacts map to GoHighLevel Contacts without the Company flag. The contact-to-account link is preserved by resolving the OplaCRM account external_id against the GoHighLevel Contact's company field at migration time. Email serves as the deduplication key. Phone, role, and custom field values migrate directly to GoHighLevel Contact properties.

OplaCRM Opportunities map to GoHighLevel Opportunities. The sale_process_stage value migrates by display label to the matching GoHighLevel pipeline stage. Close date, close reason, win/loss status, and deal value transfer to GoHighLevel's standard Opportunity fields. We pre-create the GoHighLevel pipeline and stage structure matching OplaCRM's pipeline before any Opportunity records load.

OplaCRM's sale_process_stage string enums become GoHighLevel Pipeline Stage values. We map by display label rather than internal enum to ensure CLOSE_WON and CLOSE_LOST land in the correct terminal stage bucket in GoHighLevel. Each OplaCRM pipeline becomes a separate GoHighLevel pipeline with its own stage set.

OplaCRM Products map to GoHighLevel Products. Product name, SKU, and pricing migrate directly. GoHighLevel Products are used within Opportunities as line items, and we ensure the price book is configured before line item import so that UnitPrice resolves correctly.

OplaCRM Invoices are created within the Opportunity context and carry amount, date, and status. GoHighLevel has no native Invoice object at the base tier, so we map invoice data to a GoHighLevel Opportunity custom field set (Invoice_Amount__c, Invoice_Date__c, Invoice_Status__c) and attach the invoice number as a note. The customer should review and rebuild invoice logic in GoHighLevel or a connected billing tool post-migration.

OplaCRM Custom Field values stored as key-value pairs per record migrate to GoHighLevel Custom Fields. We pre-create the custom field schema in GoHighLevel matching the source field names and data types. If a field name collides with an existing GoHighLevel property, we prefix it with 'opla_' and surface the collision in the pre-flight mapping table for the customer to rename before final import.

OplaCRM uses a UUID field (opportunities_joint_id) to link joint or co-selling opportunities. GoHighLevel has no native linked-opportunity concept, so we resolve each UUID into an explicit relationship by writing a custom field Joint_Opportunity_ID__c on both linked Opportunities and a Relationship_Type__c field set to 'Joint Deal'. We surface the full joint-relationship table in the handoff document for the customer's admin to review and potentially model using GoHighLevel Opportunities linked via a shared Tag or custom property.

OplaCRM's locked boolean flag prevents edits on the record. GoHighLevel has no native record-level lock feature. We set a custom property Opla_Locked__c with value true on affected records and flag it in the pre-flight report. The customer's GoHighLevel admin configures permission sets or page layout read-only settings to enforce the restriction after import. If the destination is an agency sub-account, permission inheritance from the parent agency may also need review.

OplaCRM Tags migrate to GoHighLevel Tags. We split any comma-delimited tag strings into individual tag entries per GoHighLevel's tag model. Tags are applied to the parent Contact or Opportunity record. Tag naming is preserved as-is unless a collision is detected, in which case we append a numeric suffix and document the change.

OplaCRM Users map to GoHighLevel Users by email address. Owner assignments on Opportunities, Contacts, and Accounts resolve via the User email match. Any OplaCRM Owner without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes. User roles migrate as GoHighLevel permission roles.