Migrate from OrangeCRM to HighLevel

OrangeCRM Customers map to GoHighLevel Company records. The customer_name field becomes Company Name, and any customer-specific custom fields (billing address, customer type, account status) migrate as GoHighLevel custom fields on Company. Company is created before Contact import so that the Company lookup is satisfied at Contact insert. We validate that every OrangeCRM Customer record maps to exactly one GoHighLevel Company and flag any orphaned Customer records where the OrangeCRM export produced incomplete address data.

OrangeCRM Contacts map directly to GoHighLevel Contacts with standard fields (first name, last name, email, phone, address). Multi-value phone and email fields are split into GoHighLevel's primary and additional contact fields. The Contact's parent Customer record resolves to the GoHighLevel Company lookup via domain-based or name-matched lookup during import. Any OrangeCRM custom fields on Contact become GoHighLevel Contact custom fields created before import.

Fulfillment records are a proprietary OrangeCRM concept tracking subscription or order fulfillment status tied to a Customer. Since GoHighLevel has no standard equivalent, we create a Fulfillment Custom Object in GoHighLevel's Object Settings with fields matching the OrangeCRM export schema (fulfillment_id, status, fulfillment_date, customer_reference, tracking_number). We preserve the parent Customer reference as a Lookup to the GoHighLevel Company and note that the customer must validate business logic interpretation during the mapping review phase before cutover.

OrangeCRM Help Desk tickets map to GoHighLevel Tasks using the Inbox-style task model. Ticket status, priority, assignee, and conversation history migrate as Task status, priority, assigned User, and a Notes field containing the threaded conversation. We extract the conversation thread from OrangeCRM's export and flatten it into a single text block with sender and timestamp annotations to preserve context without requiring GoHighLevel's conversation threading model.

OrangeCRM email campaign records and subscriber lists map to GoHighLevel Contacts with subscriber opt-in dates and campaign engagement metrics stored as custom Contact fields. Active subscriber list membership in OrangeCRM translates to Tags on GoHighLevel Contacts (e.g., tag_name: 'newsletter_q1_2025'). Email opt-in and opt-out status maps to GoHighLevel's dnd and email opt-out flags per contact.

OrangeCRM Storefront orders map to GoHighLevel Opportunities representing the revenue transaction, with line items and product references stored in a custom Order Custom Object linked to the Opportunity. Order totals, fulfillment status, and OrangeCRM product IDs migrate as custom fields; the customer must validate that OrangeCRM product pricing is correctly interpreted against any new price lists configured in GoHighLevel Payments.

OrangeCRM Banking module records (payment tracking or ledger entries) map to a GoHighLevel Invoice custom object with fields for amount, currency, payment date, and reference. We flag any multi-currency handling requirements from the OrangeCRM export and note that GoHighLevel Payments supports Stripe integration for payment recording; the customer's admin validates whether the existing Banking logic maps to Stripe payment records or remains as a custom Invoice object.

OrangeCRM event registrations and attendee records map to a GoHighLevel Event Registration Custom Object linked to the associated Contact, with attendee status, session selections, and custom event fields preserved as custom fields. We also tag the related GoHighLevel Contact with the event name for segmentation. If OrangeCRM event data is large or complex, we recommend the customer validate field mapping during the sandbox pass before production migration.

OrangeCRM user accounts and record owners map to GoHighLevel Users by email match. We extract every distinct owner referenced on Contact, Customer, Fulfillment, Ticket, and Order records and match against the GoHighLevel destination location's User list. Any OrangeCRM Owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required for task assignment and contact ownership in GoHighLevel.

OrangeCRM custom fields per module are extracted from the export schema and pre-created in GoHighLevel as custom fields on the corresponding object (Contact, Company, Opportunity, or the relevant Custom Object). Field types are mapped from OrangeCRM's export types to GoHighLevel field types: text to text, date to date, number to number, picklist to dropdown. Multi-select fields in OrangeCRM map to GoHighLevel multi-select or tag-based fields depending on the use case, chosen during scoping.