Migrate from Flexie to Twenty CRM

Flexie Workers map directly to Twenty People records. We extract name, contact details, availability windows, employment status, and any custom properties per worker. The Flexie worker email becomes the People email field and serves as the dedupe key during import. Employment status (active, inactive, on-leave) migrates to a Twenty custom select field for status tracking. Availability windows are not a native Twenty field and require a custom availability object or multi-select field designed during schema scoping.

Flexie Venues map to Twenty Company records. Venue name becomes Company name, and venue address fields map to the Company address fields. Venue-level custom fields (capacity, operating hours, region, venue type) become Twenty Company custom fields created before import. Companies must be imported before any People records that reference them so that the People.companyId lookup resolves at insert time.

Flexie Shifts map to Twenty Task records. Shift start time and end time map to Task dueDate and startDate. Shift status (open, filled, cancelled) migrates to a custom Task status field. The venue where a shift occurs becomes the Task WhatId referencing the Company record. We preserve the original shift duration as a custom field because Twenty Tasks track dates rather than explicit duration.

Flexie Shift Assignments are the junction between Workers and Shifts. We resolve each assignment by linking the Task (migrated from the Shift) to the assigned Worker (People record) via the Task.name field or a custom task-participant lookup. If Flexie tracks assignment notes, status, or acceptance timestamp, these become custom fields on the Task. Unfilled (open) shifts are imported as Tasks without a worker link and flagged for review.

Flexie Entity Forms serve as data entry points and workflow triggers with submission records attached. Form submission data has no direct Twenty equivalent and requires a custom object design during scoping. We create a Custom Object matching the form schema (form fields become custom fields on the object), and form submission records are imported as Custom Object records with a reference to the related Worker or Venue if applicable. Form definitions themselves are documented for manual recreation in Twenty.

Flexie documents attached to Workers, Shifts, or Venues migrate as Twenty Files. Document metadata (name, upload date, attached record type) is preserved, and the file itself is uploaded to Twenty and linked via ContentDocumentLink to the parent People, Company, or Task record. We do not migrate the actual file hosting separately; documents are transferred as part of the migration payload and uploaded via Twenty's file upload API.

Flexie custom properties per Worker are extracted during discovery via API. Each custom property is mapped to a typed Twenty People custom field (text, number, select, multi-select, date, or boolean). Picklist-type custom properties require value review for length limits and special characters before creating the corresponding select field in Twenty. All custom fields must exist in Twenty before any People import begins.

Flexie custom properties per Venue are mapped to Company custom fields in Twenty. Venue-specific attributes like service category, capacity limits, shift minimums, or regional flags become Company custom fields. We extract the live schema from Flexie during discovery to capture every active custom property, including those not visible in the default UI.

Custom properties on Flexie Shifts (pay rate, shift type, dress code, equipment requirements) map to Task custom fields in Twenty. We flag any shift properties that reference other Flexie objects (such as pay rates tied to worker tiers) as requiring manual review because cross-object references in Flexie do not automatically translate to Twenty relationships.

Flexie Workflows are automation sequences built on Entity Form triggers and scheduling actions. They are platform-native and cannot be exported as reusable definitions. We do not migrate workflows. During scoping, we run a discovery pass that documents every active Flexie workflow with its trigger conditions, actions, and dependencies. This inventory is delivered as a written handoff document for the customer's admin to rebuild in Twenty or integrate via an external automation tool such as n8n.