Migrate from Unim to HighLevel

Unim Contact records map to GoHighLevel Contact. Every Unim deployment has a different Contact schema built from a base ModelID plus active custom fields. We discover the live Contact field set via the custom-fields API endpoint before migration, resolve DataType IDs for any custom fields via the valuelists endpoint, and map each to a GoHighLevel standard field or custom field created in the destination sub-account before import. Email address is the dedupe key for Contact inserts.

Unim Company records map to GoHighLevel Company. The Company entity follows the same discovery pattern as Contact—ModelID plus active custom fields are introspected before migration. We create matching custom fields in GoHighLevel's Company object, then import Company records before Contact import so that the Contact-to-Company linkage is satisfied at insert time. Domain or company name is the dedupe key.

Unim's Company-to-Contact linkage model varies per application. We discover whether Contacts link to Companies via a foreign-key field, a join table, or embedded object references. In GoHighLevel, Contacts optionally associate with a Company record via the company_name or company_id field. We configure this linkage during discovery and preserve the relationship during import by resolving the destination Company ID before Contact insert.

Unim Activity records carry timestamps, owner references, and optionally linked custom fields. We map call Activities to GoHighLevel Task with call-related metadata in custom fields; email Activities map to GoHighLevel Task with a body field carrying the message content; meeting Activities map to GoHighLevel Event with start/end timestamps; notes map to GoHighLevel Note. Activity-to-Contact or Activity-to-Company linkage is preserved via the destination record ID resolved at migration time.

Unim's custom-fields API exposes every custom field defined on the standard objects with a Name, ModelID, DataType, and Nullable flag. DataTypes require a separate valuelists API call to resolve the lookup ID. We create matching custom fields in GoHighLevel for each discovered custom field before importing any records. Multi-select, date, number, and text datatypes map directly to GoHighLevel equivalent field types. This step is mandatory before any record import.

Bespoke object types defined at the Unim application level are discovered via schema introspection. We evaluate each custom object independently: if it resembles a Deal or Project structure (with amount, stage, close date), we map it to GoHighLevel Opportunity within a Pipeline. If it is a distinct entity type not represented in GoHighLevel's standard model, we create a Custom Object in GoHighLevel and map its fields accordingly. Lookup relationships between custom objects and standard objects require parent-record resolution before child record insert.

Owner IDs in Unim are scoped to that specific deployment and are not portable to GoHighLevel. We extract every distinct owner referenced on Contacts, Companies, Activities, and custom objects, and match by email address against the GoHighLevel destination Users. Any owner with no matching GoHighLevel User is placed in a reconciliation queue for the customer to provision before import resumes. Unresolved owner references are set to the GoHighLevel migration service user with a note for manual reassignment.

Tag associations in Unim are stored either as linked records or as array fields depending on the specific deployment. We preserve tag-to-record linkages as a join table exported to a GoHighLevel custom field (multi-select picklist) or as Tags in GoHighLevel depending on the customer's preference. Tag strategy is confirmed during the discovery phase.