Migrate from Efficy CRM to HighLevel

Efficy Company records map to GoHighLevel Locations. The company name becomes the Location name, and Efficy's companydomain property maps to the Website field. Location is created before any Contact import so that the Location-Custom Field relationship is satisfied at Contact insert. We extract Companies from Efficy's JSON-RPC API searcha endpoint and write to GoHighLevel's Locations API using the location name as the dedupe key.

Efficy Contact records map directly to GoHighLevel Contacts. Standard properties (firstName, lastName, email, phone, address) transfer cleanly. The Efficy Company linkage migrates as a GoHighLevel Location lookup on the Contact record, resolving the Efficy KCOMAPNY foreign key to the GoHighLevel Location ID at migration time. Multi-address contacts require flattening to a single primary address in GoHighLevel.

Efficy Deal records map to GoHighLevel Opportunities within a configured Pipeline. Deal stage maps to a GoHighLevel Pipeline stage; deal value and expected close date migrate as monetary amount and close date. The pipeline stage names are re-created in GoHighLevel before migration so that stage IDs are available for assignment during import. Owner mapping resolves Efficy KUSER references to GoHighLevel user IDs by email match.

Efficy Activities linked to Contacts or Deals migrate as GoHighLevel Activities with the original timestamp preserved. Call duration and disposition notes map to GoHighLevel Activity custom fields. Email body and subject transfer as Activity notes. Meeting details map to the GoHighLevel Activity meeting type with attendee lists preserved. Activity linkage to Contact is resolved by matching the Efficy KCONTACT foreign key to the migrated GoHighLevel Contact ID.

Efficy custom fields on Companies, Contacts, and Deals transfer to GoHighLevel Custom Fields of equivalent type. Picklist values from Efficy become GoHighLevel option-set values; date fields map to GoHighLevel date fields; numeric fields map to number fields. We pre-create the full custom field schema in GoHighLevel during the schema-design phase before any records are migrated. Custom field type compatibility is verified during scoping because some Efficy field types (e.g., complex multi-relation fields) require flattening or omission.

Efficy object-level tags flatten to GoHighLevel Tags on Contacts and Opportunities. Multi-tag properties from Efficy are stored as comma-separated values in GoHighLevel's tag field. Tag strategy is confirmed during scoping because GoHighLevel tags function as quick filters rather than segmentation lists; if the customer requires list-based segmentation, we map Efficy tags to GoHighLevel Campaigns or Smart Lists instead.

GoHighLevel does not have a native ticketing module. Efficy Ticket records are migrated into a GoHighLevel Custom Object named Ticket with fields for status, priority, agent assignment, and conversation history. Ticket conversations are stored as threaded notes or as a text-area field on the Custom Object record. The Custom Object is provisioned in GoHighLevel before migration begins, and workflows on the Ticket Custom Object are documented in the automation rebuild specification for manual reconstruction.

Efficy Project records with milestones and tasks can migrate to GoHighLevel as a Custom Object (Project) or as Opportunities in a dedicated pipeline tagged as Project records. Full project management structure including milestones, resource assignments, and dependencies does not map directly to GoHighLevel and requires a configuration decision during scoping. Most Efficy-to-GoHighLevel migrations use a pipeline with a project-type tag to keep the structure simple; complex project data maps to a Custom Object with a one-to-many task sub-object.

Efficy documents attached to Companies, Contacts, or Opportunities are migrated as GoHighLevel Media Library entries via URL reference or as binary uploads where GoHighLevel's media API supports it. Documents without a downloadable URL (stored internally in Efficy without a public link) are flagged in the pre-migration audit and listed as a separate remediation task for the customer to handle outside the migration scope.

Efficy Users are mapped to GoHighLevel Users by email address match. Inactive Efficy users are excluded from the user migration but their historical assignments on Contacts, Deals, and Activities are remapped to the active GoHighLevel user who takes over the account. GoHighLevel's unlimited-user model means there is no per-user licensing constraint on how many users are provisioned, but the customer's admin must create GoHighLevel User accounts and assign roles before records with owner assignments can be imported.

Efficy automation rules, follow-up sequences, and workflow triggers do not export via the Efficy API or the Import Wizard. These do not migrate. We document every active Efficy automation during discovery — capturing the trigger type, conditions, actions, and delay logic — and deliver a rebuild specification written for GoHighLevel's workflow builder. Revenue-critical automations are prioritised first and assigned an estimated rebuild effort of one to two hours per complex workflow.