Migrate from Unanet CRM by Cosential to HighLevel

Unanet's contact record maps to HighLevel's contact record. The contact's first name, last name, email, phone, address, and title transfer directly. Unanet's firm/person split (contacts within firms) collapses into a single HighLevel contact with a link to the primary company record.

Unanet's company record maps to HighLevel's company record with name, domain/website, industry, employee count, and revenue fields transferred. Parent/child company hierarchies require flattening — the top-level parent maps as the company record and child companies are created as separate company records linked by a custom Parent_Company__c field or a note.

Unanet allows a single contact to associate with multiple companies simultaneously. HighLevel contacts have one primary company. The migration maps the most recently updated or most-used company association as primary; secondary associations are preserved as tags or custom text fields listing the other associated company names.

Unanet's opportunity (pursuit) record with pursuit code, pursuit name, stage, amount, probability, close date, and owner maps to a HighLevel opportunity. The pursuit's configurable process gates (Go/No-Go, RFP tracking) do not have a native HighLevel equivalent and are preserved as custom fields and notes rather than workflow triggers.

Unanet's pursuit stages translate directly into HighLevel pipeline stages on a one‑to‑one basis. Each stage name—such as Identified, Qualified, Pursuing, Submitted, Won, and Lost—receives a matching HighLevel stage label, preserving the original progression logic. Where Unanet includes probability weights for stages, those percentages are imported as stage‑level probability fields in HighLevel, ensuring forecast calculations remain consistent after migration.

Unanet projects that are linked to pursuits map to a custom object in HighLevel since HighLevel has no native project entity. The project record stores project name, start date, project manager, and the related opportunity lookup. AEC-specific project fields like contract type and project code are stored as custom fields.

Unanet personnel records map to HighLevel users. The owner on an opportunity is resolved by matching the personnel's email address against HighLevel user emails. Unmatched owners are flagged before migration — your team creates HighLevel accounts first or assigns a fallback owner so no opportunity lands without an owner.

Unanet's activity log entries (logged calls, emails, meeting notes) map to HighLevel tasks and notes. Each activity inherits the original timestamp, owner, and a reference back to the related contact or opportunity. Activity type (call, email, meeting, note) is preserved as a tag or task category field.

Unanet documents and attachments linked to contacts, companies, or pursuits are exported, preserving file names, creation dates, and owner details. They are then re‑uploaded into HighLevel's attachment model, where each record can store multiple files under the related contact, company, or opportunity. HighLevel's per‑record attachment size limits are respected during upload, and any file exceeding the limit is flagged for manual handling or compression.

Unanet's custom fields on contacts, companies, and opportunities map to HighLevel custom fields created in the destination. Field type is preserved where possible (text stays text, pick-list stays pick-list). AEC-specific custom fields (firm qualifications, proposal data, resume database fields) are created as custom fields in HighLevel.

Unanet's Financial Data Connector syncs project financial performance from the ERP into the CRM. HighLevel has no equivalent ERP connector. The data is not migratable — firms must rebuild financial visibility in HighLevel through manual updates, third-party integrations, or custom API work.

Unanet workflow configurations and automation rules do not transfer directly to HighLevel because each platform uses a distinct automation engine. FlitStack AI exports Unanet workflows—including lead‑routing, stage‑gating, and task‑generation rules—as a reference document listing triggers, conditions, and actions. Your HighLevel admin can use that document to rebuild equivalent logic in HighLevel’s workflow builder, mapping triggers to actions while preserving the original automation intent.

Unanet proposal automation templates and the associated resume database do not migrate to HighLevel because each platform stores template logic differently. The proposal content—including client‑specific sections, pricing tables, and layout designs—is exported from Unanet as separate documents that can be used as reference material. Your HighLevel admin can then rebuild proposals using HighLevel’s document builder, incorporating the exported text and layouts to recreate the original proposal structure more quickly.