Migrate from Talisma to HubSpot

Talisma Persons map directly to HubSpot Contacts. Each Person record transfers with name, email, phone, job title, and address fields. Talisma's person-level custom fields migrate to HubSpot contact properties — created as custom properties before migration if they do not exist.

Talisma Organizations map to HubSpot Companies. Organization name, domain, industry, employee count, and annual revenue transfer as Company properties. Parent-child org hierarchies in Talisma map to HubSpot's company parent-company association using the parent_organization_id field. Industry pick-list values are mapped to HubSpot's standard industry options, with non-matching values preserved as custom properties for admin review. Annual revenue values transfer as numeric fields where possible, with any currency formatting stripped during the mapping process.

Talisma's person-organization relationship (which persons are linked to which organizations) maps to HubSpot's contact-company primary association. N:N associations in Talisma are preserved — HubSpot supports one primary company per contact with the ability to add additional associated companies via the Associations API.

Talisma Cases migrate to HubSpot Tickets. Case subject, description, priority, status, and owner transfer as Ticket properties. Talisma case types map to HubSpot ticket pipeline names, with case status values mapped to ticket status categories — Open, Pending, Closed. If Talisma contains multiple case types (e.g., Support, Billing, Technical), we create corresponding pipelines in HubSpot so each case category routes to its own workflow. Case priority values (Low, Medium, High, Critical) map to HubSpot's priority field with one-to-one correspondence, and any custom priority labels are preserved as custom properties for review.

Talisma Campaign records — including campaign name, type, start date, and status — migrate to HubSpot Campaigns. Member associations (which contacts were added to which campaigns) transfer as HubSpot Campaign Members with activity timestamps preserved. Campaign member status in Talisma maps to HubSpot campaign member status (registered, attended, cancelled). If Talisma tracks campaign utm parameters or source information, these migrate as campaign custom properties. We also preserve the original Talisma campaign ID as a custom property for cross-reference.

Talisma allows custom entities beyond Persons, Organizations, and Cases. These map to HubSpot Custom Objects — available on Enterprise plans. Non-Enterprise HubSpot portals receive these records as custom properties on the Contact or Company object, chosen based on the entity's primary association.

Talisma logs for emails, calls, meetings, and notes transfer as HubSpot Engagements with original timestamps and owners preserved. HubSpot's engagement model associates these activities with the relevant Contact, Company, Deal, or Ticket record via the engagement's associations array. Email bodies and call notes migrate as engagement content, with attachments handled via HubSpot's file storage and linked to the engagement record. Meeting records include attendee information where available, and activity type (email, call, meeting, note) maps to HubSpot's engagement_type field.

Talisma workflows, sequence rules, and automated triggers do not migrate — they are tightly coupled to Talisma's module execution context. We export workflow definitions as structured JSON documentation for your HubSpot admin to reference during rebuild in HubSpot's Workflow tool.

Talisma user records map to HubSpot Users by email address match. We flag any Talisma owner without a corresponding HubSpot user email before migration — your team either creates HubSpot users first or assigns those records to a fallback owner during the migration run.

Talisma file attachments download from the source and re-upload to HubSpot's file storage. Files are associated with the relevant Contact, Company, or Ticket record. File size limits for HubSpot imports apply — files over 25 MB are flagged for manual handling.

Talisma module-level settings such as required fields, validation rules, and display labels are configuration, not data. These do not migrate. We document Talisma's current field configuration so your HubSpot admin can replicate field-level requirements in HubSpot's property settings. The configuration document includes each field's display label, data type, whether it is required or optional, and any validation rules such as format constraints or pick-list options. This documentation serves as the reference guide for your HubSpot admin to recreate Talisma's field behaviour in HubSpot's property panel.