Migrate from Sentia to HighLevel

Sentia Contacts migrate directly to GoHighLevel Contacts. The full standard field set (name, email, phone, address) maps to GoHighLevel's built-in contact fields. Custom contact-level properties in Sentia become GoHighLevel Contact custom fields created before migration. We deduplicate by email address during import, merging any duplicate Sentia Contact records. Contact-to-Company associations migrate as GoHighLevel Contact-Company links using the Company name as the lookup key.

Sentia Company records map to GoHighLevel Companies. The domain, address, phone, and website fields migrate directly. GoHighLevel supports a separate Company object distinct from Contact, which is consistent with Sentia's data model. We create Companies before Contacts so that the Contact-to-Company association is resolved at insert time. Duplicate Companies are merged by name using case-insensitive matching.

Sentia's separate Lead object has no direct GoHighLevel equivalent because GoHighLevel uses a single Contact model without a distinct Lead concept. We merge all Sentia Leads into GoHighLevel Contacts, preserving the original lead source (as a GoHighLevel Contact custom field, e.g., lead_source__c) and lead status (as a status__c custom field) as Contact-level properties. The customer confirms the tag or label taxonomy to apply during merge.

Sentia Deals map to GoHighLevel Opportunities. The deal name, monetary value, associated Contact, associated Company, and close date migrate directly. Pipeline stage from Sentia becomes a GoHighLevel Opportunity custom field (deal_stage__c) since GoHighLevel pipelines use stage names that the customer defines post-migration. We preserve the stage history as a log on each Opportunity record.

Sentia pipeline stages are organization-specific custom values. We map source stages by name proximity to the GoHighLevel pipeline stages the customer defines in their destination account. Probability percentages from Sentia custom stage properties migrate to GoHighLevel stage probability settings or an opportunity probability custom field. Customer confirmation is required on the stage mapping table before import.

Sentia custom fields are discovered during scoping via the metadata API, constrained by the customer's active tier (Basic exposes fewer field types than Ultimate). We pre-create GoHighLevel Contact custom fields and Opportunity custom fields before migration, using the same field label and nearest equivalent data type. Note that GoHighLevel does not allow switching a field between Contact and Opportunity type once created; we resolve this during scoping.

Sentia Activity records attached to Contacts or Deals migrate to GoHighLevel Activities. Call duration, disposition, and timestamps migrate to GoHighLevel Activity custom fields. Email body content migrates as a note or activity log entry. Meeting location and time stamp preserve. Activity-to-Contact associations are resolved by email match at migration time. Historical timestamps are preserved so the GoHighLevel Activity timeline reflects the original engagement dates.

Sentia Users who own records are resolved by email match against GoHighLevel Users in the destination account. Any Sentia User without a matching GoHighLevel User is placed in a reconciliation queue for the customer's admin to provision the corresponding GoHighLevel user account before record import proceeds. Inactive Sentia users map to inactive GoHighLevel users to preserve historical ownership attribution.

File attachments associated with Sentia Contacts, Companies, or Deals migrate as GoHighLevel attachments on the corresponding records. We use file reference export where available; otherwise files are re-uploaded and linked at migration time. Attachments above 25MB are flagged as oversized and escalated to the customer for alternative handling.

Sentia record tags migrate as GoHighLevel tags on the corresponding Contact or Opportunity. Tags used for segmentation are preserved as tag arrays on the destination record. Where Sentia tags represent behavioral or lifecycle data that GoHighLevel cannot natively store as tags, we map them to GoHighLevel Contact custom fields as agreed during scoping.

Sentia automations, workflow rules, and voice workflow configurations are platform-specific logic with no portable schema. Voice workflow configurations reference internal record IDs that are not transferable. We export a JSON representation of all active Sentia automation rules and voice workflow definitions for the customer's admin to rebuild in GoHighLevel's workflow builder. This document is included in the standard migration deliverable.