Migrate from Flowlu to Twenty CRM

Flowlu Contacts map to Twenty Persons. The Flowlu contact record (name, email, phone, company association, lifecycle stage, custom properties) maps to Twenty's Person object. We use email as the dedupe key. The Flowlu company link becomes a link to the migrated Twenty Company record. Custom fields on Contacts migrate to custom fields on Person via Settings → Data Model with type matching (text, number, date, checkbox, list).

Flowlu Company records map directly to Twenty Company. We preserve company name, industry, website, address, and any custom fields. The relationship between Contact and Company in Flowlu (many-to-one) is preserved as the Person's companyLink in Twenty. Company records are imported before Person records so that the company reference is satisfied at the moment of Person insert.

Flowlu Opportunities map to Twenty Opportunities. Stage, amount, probability, expected close date, and custom fields migrate. The Flowlu pipeline assignment becomes a Twenty pipeline. Closed-Lost and Closed-Won timestamps from Flowlu are preserved in custom fields. Custom fields on Opportunities migrate with type matching against Twenty's custom field creation interface.

Flowlu Pipelines and their stages migrate to Twenty Pipelines. Stage names, display order, and probability percentages are mapped. Each Flowlu pipeline becomes a separate Twenty pipeline. We configure the pipeline in Twenty before migrating any Opportunities so that deal placement is valid at import time.

Flowlu Tasks exist inside Projects and also as standalone CRM tasks. Project-assigned tasks map to Twenty Tasks linked to the migrated project workspace (or as Notes on the relevant Company/Person if no project mapping is desired). Standalone CRM tasks map to Twenty Tasks. Task status, assignee, due date, and description migrate. Dependencies between tasks in Flowlu do not have a direct Twenty equivalent and are preserved as text descriptions in the task body for manual rebuild.

Flowlu Projects are top-level work containers with no direct Twenty CRM equivalent because Twenty does not have a native project management module. We give the customer three options during scoping: migrate Projects as Twenty Companies with a project type tag, migrate as custom fields on relevant Person or Opportunity records, or export as a written inventory of project names, deadlines, and owners for manual rebuild in a project tool. The choice depends on how the customer uses project data post-migration.

Flowlu Time Entries (hours logged against Tasks or Projects) migrate to Twenty as custom fields on the relevant Person or Opportunity, or as Activity records with the duration in the description. Billable flag and time entry descriptions are preserved. If the customer uses time tracking as a billing reference, we recommend migrating billable time as a custom number field on Opportunity.

Flowlu Invoices (line items, tax rates, payment status, totals) have no native Twenty CRM equivalent. Twenty does not include an invoicing module. We export invoice data as CSV records that the customer can re-enter manually or import into a dedicated invoicing tool. Payment status, totals, and due dates can be preserved as custom fields on the related Opportunity as a workaround.

Flowlu Knowledge Base articles (title, body content, category) cannot be mapped to a native Twenty object. We export Knowledge Base content as structured CSV (title, category, body text) and deliver it as a manual re-entry package. If the customer uses Knowledge Base articles as internal documentation attached to Projects or Companies, we recommend migrating the most critical articles as Notes attached to the relevant Company record in Twenty.

Custom Fields attach to multiple object types in Flowlu (Projects, Tasks, Opportunities, Contacts, Companies, Knowledge Base). Each Flowlu custom field has a type (text, number, date, list, checkbox). We pre-create the equivalent custom fields in Twenty's Settings → Data Model for each target object before any data import begins. Type mismatches (e.g., Flowlu list field vs. Twenty text field) are flagged for manual review during scoping. Required-field validation on Twenty custom fields must be relaxed during import or the import will fail on records with missing required values.

Flowlu Users (Admin, Manager, Member roles) map to Twenty workspace members. We resolve by email match. Owner assignment on Opportunities, Tasks, and Projects migrates by resolving the Flowlu owner email to the Twenty workspace member. Any Flowlu user without a matching Twenty account goes to a reconciliation queue for the customer to provision before record import.

Flowlu engagements (calls, emails, meetings, tasks logged against CRM records) map to Twenty Activity records linked to the relevant Person or Opportunity. Activity type, date, body text, and assignee migrate. Call duration and disposition notes from Flowlu calls migrate to Twenty Activity description. Email content migrates as Activity body text. Meeting subject, date, and attendee information migrate as Activity records.