Migrate from EXACT to HubSpot

HubSpot Contact maps 1:1 to Exact Contact records. Exact contact properties (name, email, phone, job title, address) transfer as HubSpot default properties. Exact's contact status flag (Customer/Lead/Inactive) routes to HubSpot lifecycle_stage as a value-mapped custom property for reporting parity. Any custom properties on Exact contacts are created as HubSpot custom properties with matching data types before migration runs.

Exact Account maps directly to HubSpot Company. Account name, website, industry, employee count, and annual revenue transfer as HubSpot Company properties. Exact's billing address fields map to HubSpot's address property set (street, city, state, postal code, country). Multi-address Exact accounts: primary billing address migrates as the Company address; additional addresses stored as a custom multi-line text property.

Exact Projects map to HubSpot Deals. The project name becomes the Deal name, project status maps to Deal stage via value mapping, and project value or budget amount maps to the Deal amount. If an Exact project contains multiple work orders or deliverables, each sub-item can become a Deal line item in HubSpot if the Products/Line Items module is available.

Exact Sales Orders map to HubSpot Deals with Line Items attached. Order number migrates as a custom property (exact_order_number__c). Each line item on the Exact order maps to a HubSpot Line Item linked to the Deal, preserving product name, quantity, and unit price.

Exact call logs, email logs, and notes transfer to HubSpot as Engagements on the Contact timeline. Original timestamps, owner (rep), and associated contact/company links are preserved. Exact notes with rich text are converted to HubSpot note format with attachments preserved.

Exact calendar entries linked to contacts or projects migrate as HubSpot Meetings with original start time, duration, attendee list, and meeting notes. If Exact uses a connected calendar integration, the HubSpot meeting link is preserved; standalone calendar entries without CRM links migrate as engagement notes.

Exact custom fields that don't map to HubSpot native properties (order numbers, invoice references, project codes, ERP-specific codes) are created as HubSpot custom properties. Custom property type is inferred from the source data type — text fields become text properties, numeric values become number properties, dates become date properties.

Exact user records are matched to HubSpot users by email address. If an Exact contact is assigned to a user who doesn't have a HubSpot account, the record lands with an unassigned OwnerId and a flag property (original_exact_owner__c) preserves the original assignment for manual re-assignment.

Exact document attachments on contact or project records are downloaded and re-uploaded to HubSpot Files. Files are associated to the corresponding HubSpot record (Contact, Company, or Deal) using HubSpot's file-to-record association API. File size limits apply (HubSpot default 25MB per file).

Exact workflow rules, approval chains, and automated assignment logic do not have a HubSpot equivalent and cannot be migrated. FlitStack exports the workflow definitions as a configuration document for your HubSpot admin to reference when rebuilding in HubSpot's Workflow tool. This export includes trigger conditions, action sequences, and conditional branch logic.

Exact's financial ledger fields (credit limit, payment terms, outstanding invoice total, tax ID) have no HubSpot native equivalent. These migrate as custom properties on the Company record (for account-level financials) or as read-only reference fields on the Deal for context. Finance teams typically recreate these as custom properties synced from an ERP integration post-migration.

Exact service tickets or support requests map to HubSpot Tickets. Ticket status, priority, subject, and description transfer. HubSpot's ticket pipeline is configured per your support workflow — Exact ticket categories map to HubSpot ticket pipelines via value mapping if multiple queues exist.