Migrate from Ivinex to HubSpot Service Hub

Ivinex Contact Tab records map to HubSpot Contact. Standard fields (name, email, phone) transfer directly. We retrieve field definitions via GetFields before pulling records to capture any custom contact fields added by the administrator. Custom Ivinex fields of type text, number, or date map to HubSpot custom contact properties. Checkbox fields map to HubSpot single-checkbox properties. User-link fields (pointing to Ivinex Users) map to HubSpot contact owner or association properties. HubSpot's per-tier property limit (100 on Starter, 1,000 on Professional, 2,000 on Enterprise) requires prioritization during scoping if the Ivinex Contact Tab exceeds that threshold.

Ivinex Organization records map to HubSpot Company. The Organization name becomes the Company name, domain and address fields map to standard HubSpot Company properties. LinkRecords in Ivinex that associate Organizations to Contacts resolve to HubSpot Company-to-Contact associations during import. We extract Organization records before Contact records so that the Company lookup is satisfied at the moment of Contact insert.

Ivinex Ticket Tab records map to HubSpot Ticket. Ivinex ticket status, priority, assignee, and description fields map to HubSpot Ticket properties. Custom fields on the Ivinex Ticket Tab become HubSpot custom ticket properties. Ivinex pipeline stages from the Ticket Tab map to HubSpot Ticket pipeline stages. If Ivinex uses multiple Tabs to represent different work item types, we consolidate these into a single HubSpot Ticket pipeline with multiple stage values, or multiple HubSpot Ticket pipelines if the customer requires separate queues per work type.

Ivinex Task records map to HubSpot Task. Due date, assignee, completion status, and description transfer directly. Task assignment in Ivinex resolves to HubSpot Ticket owner or Task assignee via the User mapping. Ivinex Task records optionally linked to Tickets map to HubSpot Task records associated with the migrated Ticket via the ticket_id property.

Ivinex activity records exported via GetAllRelatedItems map to HubSpot Ticket conversation entries (emails and call logs as Ticket conversation messages), HubSpot Task (for generic tasks and notes), and HubSpot Event (for meeting records). The association chain in Ivinex determines which HubSpot Ticket or Contact record the activity attaches to. Activity timestamps preserve for timeline ordering. Ivinex call duration and disposition fields map to custom properties on the HubSpot Ticket conversation or Task record.

Ivinex User records (name, email, role, active/inactive status) are exported so that owner assignments on Tickets, Tasks, and Contacts can be remapped to HubSpot Users. We match Ivinex User email to HubSpot User email as the lookup key. Ivinex Users without a matching HubSpot User go to a reconciliation queue for the customer's admin to provision. Role and group membership from Ivinex map to HubSpot Roles and Teams post-migration, documented in the handoff package.

Ivinex custom fields exist on every Tab and are unlimited per account. Each Ivinex custom field (text, number, date, dropdown, checkbox, user-link) maps to a typed HubSpot custom property on the corresponding object (Contact, Company, or Ticket). We call GetFields for each Tab before data extraction to capture the complete live schema. HubSpot's property limits per tier require prioritization during scoping: Starter is capped at 100 custom properties per object, Professional at 1,000, Enterprise at 2,000. If the Ivinex schema exceeds Starter limits, we work with the customer to consolidate low-priority custom fields into structured text fields before migration.

Ivinex GetRecords returns attachment metadata including download URLs but not binary content inline. We extract all attachment URLs during the data pull, then execute parallel downloads in a second pass and re-upload to HubSpot's file management. Attachment URL validity may expire after extraction; we log any failed downloads for manual retrieval. Large files over HubSpot's attachment size limits require a separate file transfer step.

Ivinex process automation module defines workflow rules with triggers, conditions, and actions. HubSpot Service Hub Workflows use a different trigger and action model. We export Ivinex workflow configuration as structured JSON documenting the trigger, conditions, actions, and expected behavior. The customer's admin rebuilds these in HubSpot Service Hub using the workflow inventory as a specification. We do not migrate Ivinex Workflows as code.

Ivinex saved Views define field visibility and filter criteria per Tab. These are user preferences, not data records. We export view names, selected fields, and filter criteria as a structured document so they can be rebuilt as HubSpot saved views and filters. Direct import of saved Views is not supported by HubSpot's API.

Ivinex Groups control API permissions and record-level access. HubSpot manages access through Roles, Permissions Sets, and Teams. We export group membership (which Ivinex Users belong to which Groups and what permissions each Group has) as a structured document. The customer's admin uses this to configure equivalent HubSpot Roles and Teams post-migration. Groups do not migrate as access control records.

Ivinex Change History tracks field-level edits per record. Full history can be large. We scope audit migration to records being migrated and offer a date-range filter. The audit log migrates as a custom activity record or note attached to the relevant HubSpot record, preserving the original timestamp, changed field, old value, and new value. HubSpot's native audit log captures changes made within HubSpot but does not import external history.