Migrate from Centrium CRM to HighLevel

Standard Centrium contacts without the organization flag migrate to GoHighLevel Contact records. We preserve first name, last name, email, phone, address fields, and any custom field values extracted from the CSV export. The contact's email address serves as the dedupe key during import. Owner assignment maps to the GoHighLevel user record by email match, with orphaned assignments flagged for admin resolution.

Centrium stores organizations as contact records with an organization flag rather than as a distinct object. During preprocessing, we identify all contacts with the organization flag set, deduplicate by organization name, create GoHighLevel Location records for each unique organization, then re-link the remaining individual contact records to the corresponding Location. This N:1 merge step adds a preprocessing phase that can extend the timeline for accounts with large organization lists.

Centrium Deals map to GoHighLevel Opportunities. Centrium's dealstage property (won/open/lost) maps to the nearest GoHighLevel pipeline stage — open maps to a configurable default pipeline stage, won maps to the final closed-won stage, and lost maps to the closed-lost stage. The deal amount, name, and associated contact and organization links migrate directly. Any deal notes migrate as Opportunity notes in GoHighLevel.

Centrium's flat three-state model (won/open/lost) does not carry intermediate stage progression history. We map each Centrium status to the closest GoHighLevel pipeline stage. If the destination GoHighLevel account uses a multi-stage pipeline, the customer specifies the stage mapping during scoping. Historical stage transitions are not available in the export and are disclosed as a data completeness gap in the validation report.

Centrium Tasks migrate to GoHighLevel Tasks with due date, title, description, and completion status preserved. Assignee mapping resolves the Centrium owner email to the corresponding GoHighLevel user by email match. Open and completed tasks migrate; the customer specifies whether archived or completed tasks older than a configurable age threshold are included.

Centrium Projects are lightweight containers linking tasks and contacts. GoHighLevel does not have a native Project object. We extract the project name, linked tasks, and associated contacts during extract, then create a GoHighLevel Tag or custom field on the migrated tasks to preserve the project grouping. The customer specifies the grouping strategy during scoping. Complex project metadata beyond name and membership requires a manual review of GoHighLevel's Opportunities-as-projects workaround if applicable.

Centrium Notes are flat text records attached to contacts, deals, or projects. We migrate the full note body and preserve the parent-object association by linking the note to the corresponding GoHighLevel Contact or Opportunity record. Notes are not threaded — multi-message conversations map as individual note records in GoHighLevel. Notes without a valid parent record are attached to the nearest related contact or flagged for admin assignment.

Centrium custom fields are stored in a simplified schema. We extract the field definition and all per-record values during the extract phase and recreate the equivalent custom field in GoHighLevel using its custom field configuration. Field type mapping follows Centrium's type annotations — text fields map to GoHighLevel text fields, date fields map to date fields, and multi-select values map to multi-select picklists where the destination supports that type.

Centrium user records include name, email, and role permissions. We map source users to GoHighLevel users by email address. Any Centrium user without a matching GoHighLevel user account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Role permissions do not transfer — see the gotchas section for the permissions gap disclosure.