Migrate from Field Nexus to Twenty CRM

Field Nexus Contact maps directly to Twenty CRM People. The contact's name, email, phone, and job title translate to People fields. The contact's associated company in Field Nexus becomes the companyId lookup in Twenty CRM — the Company must be imported first.

Field Nexus Company maps to Twenty CRM Companies. Company name, domain/website, industry, employee count, and annual revenue are direct field maps. Companies must be loaded first because People records reference them via companyId foreign key, and FlitStack validates this sequencing before initiating the People import phase.

Field Nexus work orders are transformed into Twenty CRM Opportunities using a configurable status-to-stage value map. Work-order status (Scheduled, In Progress, Completed) maps to Twenty's Stage field (Proposal, Negotiation, Closed Won, Closed Lost). Service-address fields map to Twenty's address compound fields on the linked Company record for location context.

Twenty CRM has no native invoicing object, so a custom Invoices object must be created in Settings → Data Model before migration begins. Field Nexus invoices migrate to this custom object, carrying fields for invoice number, amount, status, due date, and a lookup to the linked Opportunity or Contact for relationship traceability.

Field Nexus timesheet entries and activity logs are mapped to Twenty CRM Tasks. Each task preserves the original timestamp, assigned user (resolved via email match to Twenty CRM Workspace Members), activity type, description, and a lookup link back to the related Contact or Work Order record for full auditability.

Field Nexus notes attached to contacts or work orders map to Twenty CRM Notes. The note body, author (resolved as owner via email match), and creation timestamp are all preserved during migration. Notes are linked to the target People or Companies record by ID lookup once those records have been imported into Twenty CRM.

Field Nexus custom properties on contacts (beyond standard fields like name, email, phone) are migrated as custom fields on the People object in Twenty CRM. These fields must be pre-created in Settings → Data Model with appropriate data types before the CSV import runs to prevent import errors.

Field Nexus company-level custom properties migrate as custom fields on Twenty CRM Companies object. Like People custom fields, these must be defined in Twenty's schema before data load occurs, ensuring field existence for all imported company records to reference correctly during migration.

Field Nexus users and work-order owners are resolved by email match against Twenty CRM Workspace Members. Users without a matching Twenty account are flagged for admin review before migration — their records can be assigned to a fallback owner or the Twenty account can be provisioned first to enable proper owner assignment.

Field Nexus file attachments are preserved as URL references in Twenty CRM Notes where the file remains accessible. If the source URL is not accessible post-migration, the file is downloaded and re-uploaded to Twenty's storage with the URL updated in the note body.

Field Nexus workflow rules, sequence automations, and dispatch logic do not have an equivalent in Twenty CRM's data model. FlitStack exports workflow definitions as a JSON specification for rebuilding in Twenty's Settings → Workflows section. This is a manual step that requires a Twenty admin.

Field Nexus invoice templates, numbering sequences, and payment automation rules are not migratable to Twenty CRM's custom object structure. These must be manually recreated in Twenty's invoicing workflow or connected to a separate billing tool. FlitStack provides a structured export of template names, field mappings, and sequence rules as a reference guide for rebuilding.