Migrate from Optimiser CRM to HighLevel

Optimiser CRM's Customer record (the unified contact entity) maps directly to GoHighLevel Contact. Standard fields (name, email, phone, address) migrate as-is. Instance-specific custom fields on Customer require pre-migration enumeration from a trial export; we create matching custom fields in GoHighLevel and map values during the CSV-to-API transform. The email field serves as the dedupe key on import.

Optimiser Company records map to the Company Info section on GoHighLevel Contact. If the customer uses separate Company and Contact objects in Optimiser, we create GoHighLevel Contacts for companies (using the Company Name as Contact name) and associate related person Contacts via a custom field or tag. The decision between flat Contact model versus separate Company object is made during scoping based on the customer's data volume and reporting needs.

Optimiser Deals map to GoHighLevel Opportunities. Each Deal's stage, value, expected close date, and owner assignment migrate. Optimiser allows configurable pipeline stages per deal type, so we extract the full stage list during scoping and create matching GoHighLevel pipeline stages before migration. Stage names are mapped via a stage-mapping table rather than assumed to match across instances.

If Optimiser CRM is used in Lead-mode (separate Lead object from Customer), Leads migrate to GoHighLevel Contacts. Lead status and source fields map to GoHighLevel Contact custom fields. Score fields migrate as custom numeric fields. GoHighLevel does not have a separate Lead object by default; Leads and Customers coexist as Contacts with different tags or status values.

Activity records logged against Contacts or Deals in Optimiser migrate as GoHighLevel Activity records. Calls, emails, meetings, and tasks each map to the corresponding GoHighLevel activity type. We associate each activity to the correct parent Contact and Opportunity by resolving the Optimiser record IDs to GoHighLevel Contact IDs at migration time. Timestamps preserve original activity dates for timeline ordering.

Tags applied to Contacts or Deals in Optimiser migrate as GoHighLevel Tags. We extract all distinct tag values from the source export, create matching tags in GoHighLevel, and apply them to the corresponding Contact or Opportunity records during import. Tags used for segmentation or lead scoring are preserved as-is; if the customer uses a large tag vocabulary (over 200 distinct tags), we recommend a tag consolidation step during scoping.

Every active custom field in Optimiser CRM must be reviewed individually during migration scoping because Optimiser's custom field schema varies by instance. We request a trial export to enumerate all fields, exclude fields with zero data, create equivalent custom fields in GoHighLevel with matching data types, and map values during the transform phase. Field types are matched: text to text, number to number, date to date, dropdown to dropdown or multi-select as appropriate.

Document attachments referenced in Optimiser are downloaded locally, then uploaded to the corresponding GoHighLevel Contact or Opportunity record. Optimiser stores attachments as URLs or in its file store; we resolve each attachment, download the file, and attach it to the correct parent record in GoHighLevel. File size limits in GoHighLevel are enforced during upload. Note that GoHighLevel's custom objects have known file upload field limitations that may require workaround via private integration.