Migrate from Planfix to Twenty CRM

Planfix Contacts map directly to Twenty Person records. We preserve the contact's name, email, phone, and all custom properties as custom fields on the Person object. The email address serves as the dedupe key during import. Linked tasks and files transfer to the Person's activity timeline and attachments. Planfix contact history logs migrate as Note records attached to the Person.

Planfix Companies map directly to Twenty Company records. The company's name, domain, address, and custom fields transfer to matching Twenty Company fields. We create the Company record before any Person import so that Person-Company lookups are satisfied at the moment of Person insert. Companies without contacts in Planfix still migrate as standalone Company records.

Planfix Deals map to Twenty Opportunity records. The deal name, amount, stage, expected close date, and owner transfer to the equivalent Twenty Opportunity fields. Planfix custom deal properties become custom fields on the Opportunity. If the Planfix deal has a linked Contact, we resolve that Person record and attach it to the Opportunity's Person id during migration.

Planfix Tasks map to Twenty Task records when the task tracks an action item (assignee, due date, status). Tasks with sub-checklists migrate with checklist items preserved as custom fields or serialized into a text field. Tasks linked to a Contact or Company resolve the Person or Company id at migration time. Tasks linked to a Project may require a custom Project object in Twenty if the customer's workflow depends on project-level task grouping.

Planfix Projects group tasks and carry their own custom fields, dates, and assignees. Twenty CRM does not have a native Project object. We create a custom Project object in Twenty during schema setup, with fields for project name, dates, status, and a lookup to the responsible Company. Tasks link to their parent Project via the custom lookup. The customer chooses the exact schema during scoping based on how project data is used post-migration.

Every Planfix workspace has its own custom field definitions with different names, types, and API IDs. We query the field schema from the Planfix API before mapping any record. We then create matching custom fields in Twenty's Settings → Data Model, using the equivalent field type (text, number, date, select, multi-select, checkbox). We map Planfix field values to Twenty custom field values during the transform phase. Skipping this step means custom field values write to the wrong columns or are silently dropped.

Planfix Workgroups group users and set shared permissions. Plan X allows up to 100 workgroups. We export workgroup memberships and roles and map them to Twenty Workspace members or Role assignments. If the customer uses workgroups to segment data access, we document the access model so the customer can configure equivalent Twenty workspace permissions post-migration.

Time logged against Planfix tasks (via timers or manual entry) migrates as structured data. We carry over duration, date, and user attribution as custom fields on the migrated Task record. If the customer tracks billable hours, we create a custom hours field on the Task and a rate field on the Person or Company for time-cost calculations in reporting.

Planfix Reports are built with Planfix's report builder and exportable as CSV or XLSX. The report definitions themselves are not portable. We export the underlying data that feeds each report as a structured CSV during migration. The customer rebuilds complex reports in Twenty or an external BI tool post-migration. Saved report configurations are documented as a handoff artifact.

Planfix Document Templates use XLSX/XLSM files with template variables. The template files can be exported from Planfix. Variable mappings are workspace-specific and cannot be replayed in Twenty without manual reconfiguration. We export the template files as documentation for the customer's admin to reconfigure using Twenty's templating approach (email sequences, PDF generation via integrations).