Migrate from Vortex Field Software to Twenty CRM

Twenty CSV import caps at 20,000 records per file — large Vortex datasets require chunking

Twenty's CSV import interface limits each upload to 20,000 records. Vortex FSM deployments with large work-order histories, asset registries, or multi-year service records will exceed this threshold. FlitStack AI splits large Vortex extracts into 20,000-record chunks matched to Twenty's import order requirements. For datasets approaching API rate-limit thresholds, we recommend using Twenty's Organization-tier API endpoint (200 requests/minute) instead of CSV upload to handle volume without chunking overhead. We surface the record-count estimate and recommended import method in the pre-migration plan.

Workspace Members must exist before records referencing them can be imported

Twenty's import system enforces referential integrity — a record with an assigneeId, creatorId, or companyId cannot import successfully if that referenced user or company does not exist. Vortex technician and dispatcher IDs on work orders must resolve to Twenty Workspace Members by email. FlitStack AI runs a pre-import user resolution step: every Vortex user with an email gets matched to a Twenty workspace member; unmatched users are flagged so your team can invite them before the migration run. This is a hard failure condition in Twenty — records with unresolved references are skipped and reported in the import summary.

Vortex workflows, dispatch rules, and SLA triggers do not migrate — must be rebuilt in Twenty

Vortex FSM workflows including dispatch assignment rules, SLA escalation timers, automated routing logic, and notification triggers are configuration-layer constructs with no equivalent in Twenty's data model or workflow builder. Twenty's Settings → Workflows supports basic trigger-action automations but lacks native SLA countdown fields, dispatch-routing logic, or sequence-based follow-up cadences. FlitStack AI provides a structured export of your Vortex workflow definitions — each rule's trigger conditions, time delays, and actions — in a format your Twenty admin can use as a rebuild reference. Plan 1–3 weeks of Twenty admin time for workflow reconstruction depending on Vortex rule complexity.

Custom fields must exist in Twenty before import — importing before creation silently drops columns

Twenty's CSV import creates records but not fields. If a column in your import CSV has no matching Twenty field — whether standard or custom — the import engine silently skips that column. The records land without the data. This affects every Vortex custom property that has no standard Twenty equivalent: SLA terms, priority tiers, contract types, asset serial numbers, service categories. FlitStack AI runs a field-existence pre-flight check against your Twenty workspace before every import run. The pre-flight report lists every custom field that must be created in Settings → Data Model before the migration run, with field type recommendations (select, text, date, number) based on Vortex's source data types.

Multi-technician work orders require flattening logic for Twenty's single-assignee model

Vortex work orders can carry multiple technician assignments and multiple dispatcher sign-offs — a single job may have three field technicians listed. Twenty Tasks and Opportunities each support a single primary assignee. We map the primary technician (by most-recent modification or by designated lead flag) to Twenty's Task assignee. Secondary technicians are mapped to additional Task records linked to the same Opportunity, with a custom field (Secondary_Technician__c) preserving the full team roster. This preserves the complete service-team context while satisfying Twenty's single-assignee schema. The mapping rule (primary = most-recent modification) is configurable in the migration plan.