Migrate from OpenCRM to HighLevel

OpenCRM Companies map to GoHighLevel Locations attached to Contact records. Each OpenCRM Company generates one Location record linked to the corresponding Contact. The Company Name becomes Location Name; the Company Address maps to Location address fields. We extract Companies first from OpenCRM's CSV export and stage them so that every Contact can be assigned a parent Location ID during the Contact import phase. Orphaned Companies (with no linked Contacts) create stand-alone Contact records with Location data attached directly.

OpenCRM Contact records map to GoHighLevel Contact records with direct field-to-field mapping for first name, last name, email, phone, and address fields. The Contact's parent Company becomes the Location lookup. Custom fields from OpenCRM map to GoHighLevel Contact Custom Fields, which we create during the schema setup phase. Tags from OpenCRM's label system map to GoHighLevel tags on the Contact record. Owner assignment maps by email match to GoHighLevel user accounts.

OpenCRM Deals map to GoHighLevel Opportunities. Each Deal is linked to a Contact and optionally to a Company; we resolve the Contact ID (and Location ID from the Company) before inserting the Opportunity. Deal value maps to Opportunity Value; expected close date maps to Close Date; owner maps by email match. Pipeline stage name mapping is required (see stage mapping below) and confirmed with the customer before the Deal import phase runs.

OpenCRM's tenant-defined pipeline stages require a manual mapping table since no two CRM tenants define the same stage names. We produce a stage-mapping table during scoping, present it to the customer for confirmation, and apply it during the Deal import so each Opportunity lands in the correct GoHighLevel pipeline stage. If the customer uses multiple OpenCRM pipelines, each maps to a separate GoHighLevel pipeline.

OpenCRM Activity records (calls, meetings, tasks) map to GoHighLevel Activities of the corresponding type. Activity date and time normalize to UTC before insert. Owner assignment resolves via email-to-user lookup. Disposition and duration fields on calls map to custom GoHighLevel Activity fields. We sequence Activity import after Contacts and Opportunities are fully loaded so the parent Contact and Opportunity IDs are available for the activity-to-record linkage.

OpenCRM Notes attached to Contacts, Companies, or Deals map to GoHighLevel Notes linked to the corresponding Contact or Opportunity record via the GoHighLevel Notes API. Note body content migrates as plain text. We run a post-import audit comparing note counts per parent record between OpenCRM and GoHighLevel to verify linkage integrity.

File attachments stored against OpenCRM records are extracted from the UI export and staged to a cloud file store (S3-compatible). We generate reference links embedded in the corresponding GoHighLevel Contact or Opportunity record. Full ContentDocument migration into GoHighLevel's native file management requires a separate file upload step using the GoHighLevel attachments API; the record-to-attachment linkage is preserved through URL mapping.

OpenCRM custom fields discovered during scoping migrate to GoHighLevel Contact Custom Fields or Opportunity Custom Fields depending on which object they were attached to in OpenCRM. Data types are mapped: OpenCRM text fields map to GoHighLevel Text, date fields to Date, numeric fields to Number, and dropdown fields to Dropdown with the same option values. We create the custom field schema in GoHighLevel before any data inserts begin.