Migrate from My Practice Now to Twenty CRM

My Practice Now's Client record maps directly to Twenty's People object. The Client's primary contact fields (name, email, phone, address) transfer as corresponding People fields. Primary company association becomes the companyId relation in Twenty. All contact details retain their original formatting and timezone information to preserve communication history.

When a My Practice Now client includes organizational affiliation data, that organization record creates a Twenty Companies entry. The company record holds industry, size, and location data that Twenty's Companies object supports natively. Industry classification uses standard codes, while size categories map to Twenty's built-in employee range options.

My Practice Now appointments become Twenty Tasks with the original appointment date preserved as the due date, appointment duration stored in a custom number field, and the client name linked via the Tasks' relation field. Status maps from scheduled/completed/cancelled to the corresponding Task status values.

Invoice records from My Practice Now translate to Twenty Opportunities. The invoice amount becomes the Opportunity amount, invoice date becomes the expected close date, and invoice status (paid/pending/overdue) maps to custom picklist values on the Opportunity record. The mapping preserves original invoice identifiers for audit trails.

Notes attached to My Practice Now client records migrate as Twenty Notes linked to the corresponding People record. Original note timestamps and author information preserve for audit continuity. Rich-text formatting in My Practice Now notes converts to plain text in Twenty.

Custom fields defined on My Practice Now client records require pre-creation in Twenty via the Metadata API before migration. Field types map to Twenty equivalents: text fields become STRING, pick-lists become SELECT, dates become DATE. The Metadata API endpoint POST /rest/metadata/objects/{objectName}/fields creates each field.

Appointment-specific custom fields such as appointment type, location, or practitioner notes migrate as custom fields on Twenty Tasks. These require provisioning via the Metadata API using POST /rest/metadata/objects/tasks/fields before the appointment-to-task translation runs. Field definitions include type, label, and optional picklist values for consistent data capture.

If My Practice Now tracks services or products separately, these map to a Twenty custom object (e.g., Services). The custom object definition is created via POST /rest/metadata/objects with the appropriate field schema before records load. Each field is defined with type, required flag, and display label for user-friendly UI rendering.

My Practice Now user assignments on client records resolve by email match against Twenty WorkspaceMembers. Unmatched owners flag for admin review before migration — records can assign to a fallback WorkspaceMember or the owner can be invited to Twenty first.

My Practice Now file attachments on client records do not transfer as native files. We preserve attachment URLs and file names in a custom text field on the People record so your team can re-upload files to Twenty's storage or an external system post-migration.