Migrate from OPEX 365 CRM to HighLevel

OPEX 365 CRM Contact records map to GoHighLevel Contact. Standard fields including firstname, lastname, emailaddress1, telephone1, address1_line1, address1_city, address1_stateprovince, and address1_postalcode migrate directly. The Dataverse ownerid resolves to a GoHighLevel user by email match. Contact status (statecode) maps to GoHighLevel Contact active/inactive status.

OPEX 365 CRM Account records map to GoHighLevel Company. Account name becomes company name, website maps to website, industry maps to industry dropdown, and annual revenue maps to a numeric custom field if GoHighLevel's default fields do not cover it. Parent-child account hierarchies are preserved as Company hierarchy relationships in GoHighLevel where supported.

OPEX 365 CRM Opportunities map to GoHighLevel Deals. The opportunity name becomes Deal name, estimatedclosekby becomes close date, and amount becomes monetary value. Pipeline and stage assignments from the source map to GoHighLevel pipeline stages configured in the destination before migration. Closed-won and closed-lost status from OPEX 365 CRM map to corresponding GoHighLevel Deal status values.

OPEX 365 CRM Lead records may be imported as GoHighLevel Contacts with a lead_status tag or as GoHighLevel Lead objects depending on the customer's GoHighLevel configuration preference. We document both options during scoping. The source lead score (hs_lead_score or custom field) migrates as a GoHighLevel tag or custom number field. If the destination GoHighLevel sub-account uses Leads, we import unqualified prospects as Leads and qualified ones as Contacts.

OPEX 365 CRM email activities (activitypointer with activitytypecode = email) map to GoHighLevel Contact activity records. The polymorphic activityparty entity requires resolution: each email's from and to parties are resolved to GoHighLevel Contact IDs or email addresses. Email subject, body (plain text or HTML), and timestamp migrate. GoHighLevel does not have a native EmailMessage equivalent, so email content attaches as Contact activity notes.

OPEX 365 CRM phone call activities map to GoHighLevel Contact call activities. Call duration, direction (inbound/outbound), subject, and disposition migrate as typed fields. The activityparty from field resolves to the calling Contact. Activity timestamp preserves the original call date.

OPEX 365 CRM appointment activities map to GoHighLevel Calendar Events linked to the relevant Contact or Deal. Start time, end time, location, and subject migrate. Attendees are resolved via activityparty and linked as GoHighLevel Contact associations where supported.

OPEX 365 CRM task activities map to GoHighLevel tasks attached to Contact records. Task subject, description, priority, due date, and status migrate. The activityparty assigned party resolves to a GoHighLevel user by email. Completed-on date maps to GoHighLevel task completion timestamp.

OPEX 365 CRM Notes stored as Dataverse annotation entities with base64-encoded body content require extraction via the Dataverse RetrieveContentStream API. We extract note text content and binary attachments into staging blob storage, then import them as GoHighLevel Contact notes or file attachments linked to the correct Contact, Company, or Deal record. Annotation createdon and modifiedon timestamps preserve note chronology.

Custom entities created in the OPEX 365 CRM Dataverse environment are enumerated via the EntityDefinitions API during discovery. Each custom entity's attributes are mapped to GoHighLevel Custom Object fields with type conversion (Dataverse string to text, integer to number, datetime to date, option set to dropdown). Custom entity relationships to Contact, Account, or Opportunity become Custom Object lookup fields. GoHighLevel Custom Objects are available on all plans without additional cost.

OPEX 365 CRM User records map to GoHighLevel users by email address match. The customer's GoHighLevel admin provisions the destination users before migration. Owner assignments on Contact, Account, Opportunity, and Activity records resolve via the email-to-user lookup. Any OPEX 365 CRM owner without a matching GoHighLevel user goes to a reconciliation queue for admin action before record import.