Migrate from Unanet CRM by Cosential to HubSpot

Unanet Contact maps directly to HubSpot Contact. Most fields — FirstName, LastName, BusinessEmailAddress — map 1:1. Contacts without a firm association land as HubSpot contacts with no primary company; those with a firm association link to the mapped HubSpot company via the hubspot_company_id property.

Unanet's Firm (the organization record) maps to HubSpot Company using FirmName as the Company Name. HubSpot stores the website in the domain property; Unanet's firm-level address fields map to HubSpot's address compound properties. Parent-child firm hierarchies in Unanet map via HubSpot's parent company association.

Unanet pursuits are the AEC equivalent of HubSpot deals — project-based sales opportunities tied to a firm and contact. The pursuit name maps to deal name, pursuit amount maps to deal amount, and the pursuit stage maps to the HubSpot deal pipeline stage value. Each Unanet pursuit pipeline requires a corresponding HubSpot deal pipeline.

Unanet stage values are mapped one-by-one to HubSpot deal stage values within the target pipeline. Stage probability and forecast category re-applied based on HubSpot's stage configuration. If Unanet has multiple pursuit pipelines (e.g., Design Build vs. Public Works), each requires its own HubSpot deal pipeline.

Unanet's parent-child firm relationship maps to HubSpot's parent company association on the Company object. The parent firm must be migrated first so child firms can reference the correct HubSpot parent company ID. Circular firm hierarchies are flagged and resolved before migration runs.

Unanet allows a contact to be associated with multiple firms (N:1). HubSpot contacts have one primary company plus secondary associations. FlitStack maps the primary firm association as the HubSpot primary company link and surfaces additional firm links as secondary company associations or as a custom property for reference.

Unanet engagement records — calls, emails, meetings, and notes — map to HubSpot's engagement timeline. Call activities become HubSpot call engagements with the original timestamp and owner preserved. Emails become email engagements. Meetings become meeting engagements. Notes map to HubSpot notes on the associated contact or company record.

Unanet proposals are tightly coupled to pursuits and contain template-generated output history. HubSpot has no native proposal object. FlitStack creates a Proposal custom object (HubSpot Enterprise) or imports key proposal metadata — proposal name, creation date, status — as custom properties on the associated deal. The proposal document files are re-uploaded to HubSpot Files and linked to the deal record.

Unanet users are matched to HubSpot users by email address. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback HubSpot user. No record lands without an owner.

Unanet's custom fields map to HubSpot custom properties. Each custom field requires creation in HubSpot's portal settings before migration, with matching type selection (text, number, date, dropdown, checkbox). FlitStack delivers a custom field creation plan based on the exported field list. Fields with no HubSpot equivalent are preserved as custom properties with a source_system flag.

Unanet file attachments — proposal documents, contact files, firm logos — are downloaded and re-uploaded to HubSpot Files. Files are associated with the appropriate HubSpot record (contact, company, or deal) via the file upload API. File size limits per HubSpot plan apply; files over the limit are flagged for splitting or alternative storage.

Unanet tracks project history tied to a firm and pursuit — past project performance data used in proposals. HubSpot has no native project object. Key project metadata (project name, year completed, project type, revenue) migrates as a custom object (HubSpot Enterprise) or as deal-level custom properties. Project documents are attached to the custom object or deal.