Migrate from Unim to HubSpot

Unim custom field definitions require a separate datatype lookup before value reads

Unim's custom-fields API follows a two-step pattern: field definitions (including datatype UUIDs) are fetched from a valuelist endpoint, then field values are read using those definitions. FlitStack AI handles this by fetching all custom field definitions upfront during the schema audit phase and caching datatype mappings. If a datatype is not recognized, the field is migrated as a text property and flagged for post-migration review. This two-step pattern can extend the schema audit phase by 1–3 hours for accounts with more than 20 custom fields, which is why we include a dedicated schema-discovery step before field mapping begins.

HubSpot lifecyclestage requires a canonical value; Unim custom stage values need triage

HubSpot's lifecyclestage property enforces a specific pick-list: subscriber, lead, MQL, SQL, opportunity, customer, evangelist. If Unim uses a custom lead-status or lifecycle field with values that don't match HubSpot's canonical set, FlitStack maps the most common values directly (e.g., Unim 'prospect' → HubSpot 'lead') and preserves the original value as a custom property called Original_Lifecycle__c. Your marketing team reviews the triage report within 48 hours of the sample migration run and confirms the value-mapping decisions before the full run commits. This prevents contacts from landing with blank lifecycle stages, which would break HubSpot's list segmentation and automation enrollment.

Contact deduplication across Unim and HubSpot requires email-based merge rules

If Unim contacts share email addresses with existing HubSpot contacts (e.g., from a prior trial or a parallel instance), the migration needs a deduplication rule. FlitStack AI uses email as the primary dedupe key for contacts. If a HubSpot contact with the same email already exists, the Unim record's properties are merged into the existing HubSpot contact, with Unim values taking precedence for fields that are blank in HubSpot. You specify the merge policy in the pre-migration audit form — options include 'Unim wins', 'HubSpot wins', and 'Flag for review'. Circular references in company hierarchies are also flagged before migration to prevent orphaning contacts.

Unim workflows and automation rules do not transfer and must be rebuilt

Unim workflows store trigger-action definitions that are not accessible via the standard API export in a format compatible with HubSpot's workflow editor. FlitStack AI exports Unim workflow definitions as a JSON reference document listing each workflow's trigger object, trigger condition, and action steps. Your HubSpot admin uses this document to rebuild workflows in HubSpot's Automation > Workflows editor. Because Unim's trigger model differs from HubSpot's enrollment-criteria model, some workflows may need redesign rather than direct translation. We recommend scheduling the workflow rebuild as a parallel workstream starting during the migration's planning phase so workflows are ready at HubSpot go-live.

Delta-pickup window captures in-flight changes but has a 48-hour ceiling

During the cutover window, your team continues working in Unim. FlitStack AI captures records created or modified in Unim after the main migration run and syncs them to HubSpot within the delta-pickup window, typically 24–48 hours. If your team continues working in Unim beyond 48 hours (e.g., a weekend cutover), records modified after the delta window closes will not be in HubSpot at go-live and must be manually identified. We recommend scheduling the cutover during a low-activity period and having your team complete their Unim work by end-of-day before the delta window opens.