Migrate from The Practice to Twenty CRM

The Practice client records map directly to Twenty's People object. We use the client's primary email as the unique identifier, which Twenty requires for Person record uniqueness checks. Phone, address, and job title fields transfer as direct text fields. If The Practice stores organization name as a field on the client record, we parse it to a separate Companies record and link via companyId.

The Practice embeds organization or company names within client records rather than as a separate entity. We extract unique organization values and create a Companies record in Twenty first (since the import order requires Companies before People). Multi-location clients with one organization name create a single Company record linked to each Person record via companyId.

Each appointment in The Practice becomes a Task in Twenty, linked to the corresponding People record. Original appointment date and time map to Task dueDate and startDate fields. Appointment type or session type maps to a custom pick-list field on the Task since Twenty Tasks do not have a native type attribute. We preserve the appointment status (completed, cancelled, no-show) as a custom status field.

The Practice defines service types (e.g., initial consultation, follow-up, therapy session) as appointment categories. We create a custom select field called Service_Type__c on the Task object and populate it via value mapping from The Practice's service type values. If The Practice uses a freeform service type field, we store the raw value as a text field and flag it for deduplication review.

Twenty has no native invoice object. We create a custom Invoice object with fields for invoice number, amount, date, client link (relation to People), and status. Invoice line items map to a custom Invoice_Line_Item child object linked via a one-to-many relationship. Your Twenty admin defines the fiscal field names during schema setup.

Any custom fields defined in The Practice on the client record (e.g., referral source, insurance carrier, billing tier) become custom fields on Twenty's People object. Field types map as follows: text to TEXT, number to NUMBER, date to DATE, pick-list to SELECT, and boolean to CHECKBOX. Multi-select pick-lists in The Practice map to Twenty's multi-select field type.

Free-form notes attached to client records in The Practice migrate as Twenty Notes, linked to the corresponding People record. Rich-text formatting in The Practice notes is preserved as plain text where possible; complex HTML-formatted notes are cleaned to text to avoid rendering issues in Twenty's Note body field.

File attachments on client records (e.g., intake forms, signed documents, session recordings) are re-uploaded to Twenty via the file upload API endpoint. We preserve the original filename and file type. If The Practice stores files in a cloud bucket with a download URL, we fetch and re-upload to Twenty's storage. Inline images in notes are extracted and re-hosted as separate file attachments.

The Practice practitioner and staff records map to Twenty Workspace Members. We resolve each practitioner by email to match against existing Twenty users. If a practitioner record in The Practice has a name but no email, we flag it for manual assignment in Twenty's user management. Practitioner-client assignment history (which staff member saw which client) is preserved as a custom field on the People record.

If The Practice manages multiple locations or branches, we create a custom location field on People and Tasks to preserve which location a client is associated with or where an appointment took place. We use a custom SELECT field with value mapping from The Practice's location names. Multi-location practices should confirm all unique location values before migration to ensure the pick-list is complete.

The Practice workflows (appointment reminders, client onboarding sequences, follow-up triggers) do not migrate to Twenty. They must be rebuilt in Twenty's workflow builder. We export the workflow definitions from The Practice — trigger type, conditions, and action steps — as a structured reference document your Twenty admin uses to recreate each automation.

Calendar integrations, telehealth connections, billing gateway links, and any third-party tools connected to The Practice do not migrate. They must be reconnected in Twenty using Twenty's REST/GraphQL API, webhooks, or Zapier integration. We document each active connection during the audit phase so your team knows what to rebuild.