Migrate from OptifiNow to Twenty CRM

OptifiNow's Lead Management module maps to Twenty's Person object. We extract lead source, assignment rules, and any custom status fields from OptifiNow's lead routing configuration during discovery. Custom lead status values migrate as a multi-select picklist field on the Person record. The original OptifiNow lead creation date migrates to Person.createdAt for historical sequencing.

OptifiNow Contact records map directly to Twenty Person. Standard fields (name, email, phone) migrate 1:1. Activity history linked to the Contact in OptifiNow migrates as Tasks and Notes on the corresponding Person in Twenty. Tag associations and custom contact-level fields discovered during the schema walkthrough migrate as custom fields on Person.

OptifiNow Account records map to Twenty Company. The account hierarchy (parent-child company relationships) migrates as a Company self-lookup relationship if present. All Contacts linked to the Account in OptifiNow are linked to the migrated Company in Twenty via the Person.companyId field.

OptifiNow Opportunities map to Twenty Opportunity with deal value, probability, and expected close date preserved. Pipeline stage names from OptifiNow's tenant-specific configuration migrate to Twenty's Opportunity.stage field with a stage mapping table defined during discovery. Closed-Won and Closed-Lost reasons become custom select fields on Opportunity.

OptifiNow's configurable pipeline stages migrate to Twenty's Opportunity stage values via a stage mapping table created during the discovery phase. Stage probability percentages transfer as Opportunity probability values. If OptifiNow uses multiple pipelines, we create multiple sets of stage values in Twenty and assign them per Opportunity record during import.

OptifiNow stores email sequences, triggers, and delays as internal workflow definitions that cannot be extracted as runnable automation packages. We export sequence templates as plain-text documentation listing trigger conditions, step order, delay durations, and CRM action types. The customer's admin rebuilds these as Twenty Workflows or as a sequence management tool of their choosing post-migration.

OptifiNow custom objects migrate to Twenty custom objects created via the /metadata API before data import. The discovery phase enumerates OptifiNow custom object types and field definitions; we then create matching Twenty custom objects with equivalent field types (text, number, select, date, relation). Custom object records import after all standard object parent records are present to satisfy lookup dependencies.

OptifiNow activity logs (calls, emails, meetings, social interactions) linked to Contacts and Accounts migrate as Twenty Task, Note, or Event records based on activity type. Call duration and disposition migrate to custom Task fields. Email content migrates as Note or Task body. Activity timestamps are preserved as Task.createdAt for chronological ordering. Parent record lookups resolve via email-to-Person matching or explicit OptifiNow contact ID tracking.

OptifiNow's content management module stores marketing collateral, images, and social media materials. Binary file assets migrate as file blobs attached to relevant Opportunity or Person records. Approval workflow associations and scheduling metadata cannot be preserved in Twenty's file model; we document the content library structure so the customer's admin can re-establish any approval routing in Twenty Workflows post-migration.

OptifiNow User records with role and territory assignments map to Twenty Member records. We extract OptifiNow owner IDs from Contact, Account, and Opportunity records and match by email against the Twenty workspace Members list. Any OptifiNow owner without a matching Twenty Member goes to a reconciliation queue for manual provisioning before record import proceeds.

OptifiNow benchmark sales processes and workflow rules are opaque and tenant-specific. We document the workflow map during discovery, listing each rule's trigger condition, conditions, and CRM actions. Twenty's workflow builder recreates these as Twenty Workflows. The handoff includes a workflow inventory document with trigger types, conditions, and action sequences that the customer's admin uses to rebuild inside Twenty.