Migrate from CentraHub CRM to HighLevel

CentraHub Leads map directly to GoHighLevel Contacts with no conversion step required since GoHighLevel does not maintain a separate Lead object outside of its native pipeline. We preserve lead source, status, owner assignment, and creation date. The CentraHub lead status picklist maps to a GoHighLevel contact tag or custom field to retain source attribution for reporting.

CentraHub Accounts map to GoHighLevel Locations, which represent company-level records. The Account name becomes the Location name, and the Account website becomes the Location website. Address fields map to GoHighLevel's address compound field. Location is created first so that the parent reference is available when Contact records are imported and linked.

CentraHub Contacts map to GoHighLevel Contacts with the Account-Contact relationship resolved by matching the CentraHub account_id against the Location ID we assigned during the Location import phase. Phone, email, title, and address fields migrate directly. We flag any Contact records that reference a CentraHub Account ID with no corresponding Location and hold them in a reconciliation queue.

CentraHub Deals map to GoHighLevel Opportunities. The deal stage name maps to a GoHighLevel pipeline stage, and deal amount maps to Opportunity value. We configure the GoHighLevel pipeline and stage values before migration to match the CentraHub stage names and preserve the probability mapping where CentraHub exposes it. Owner assignment resolves by email match to a GoHighLevel user.

CentraHub Tasks map to GoHighLevel Tasks. Due date, priority, status, and assigned owner migrate directly. We resolve the owner by email against GoHighLevel user records and link the task to the matching Contact or Opportunity by looking up the migrated record ID. Custom task types require a value-mapping step during transformation.

CentraHub Appointments map to GoHighLevel Calendar events. Start time, end time, title, location, and description migrate directly. We normalize date and time values to UTC before writing to GoHighLevel. Appointments linked to Contacts or Deals resolve the parent reference via the migration ID map we built during the Contact and Opportunity import phases.

CentraHub activity logs for calls, emails, and notes migrate to GoHighLevel Notes or Activity records. Call duration and disposition migrate as custom note attributes. Email body content migrates as note body text linked to the Contact. We reconstruct the activity timeline ordering by setting the GoHighLevel created date to match the CentraHub activity timestamp so that the sequence of interactions is preserved in the Contact record.

CentraHub per-module custom fields map to GoHighLevel custom fields of equivalent data type. We extract the full custom field schema per module from CentraHub, validate data types against CentraHub's loose enforcement (flagging records where text was stored in a number field), and create matching custom fields in GoHighLevel before data import. Picklist values map explicitly; any picklist value with no GoHighLevel equivalent is flagged for the admin to resolve.

CentraHub tags applied across Contacts, Accounts, and Deals map to GoHighLevel Tags. Tags stored as multi-checkbox properties on Contacts map to GoHighLevel tag assignments on the Contact record. We preserve the full tag taxonomy and flag any tag value that contains characters unsupported by GoHighLevel's tag naming convention.

CentraHub file attachments are stored via Dropbox and Box integration rather than as native CRM files. We download each attached file to temporary storage during the extraction phase, then re-attach files to the matching GoHighLevel Contact, Location, or Opportunity record post-import using GoHighLevel's file upload API. File names and original upload timestamps are preserved in the GoHighLevel attachment metadata.

CentraHub Workflows automate field updates, email sends, and task creation based on field conditions. Workflow definitions store field references by internal ID rather than field names, meaning any field renamed during migration silently breaks the workflow. We extract all workflow definitions as structured JSON, cross-reference field IDs against the migration field map, and deliver a written inventory of every active workflow with its trigger, conditions, actions, and the recommended GoHighLevel Automation equivalent for the customer admin to rebuild.

Reporting configurations including chart types, filters, date ranges, and dashboard layouts are platform-specific and cannot be reproduced in GoHighLevel. We do not migrate dashboards or report definitions. Historical data that informed existing reports is preserved in the migrated records. We deliver a written summary of the CentraHub report structure to assist the admin in recreating equivalent reports in GoHighLevel's reporting module.