Migrate from Advance Practice Management Suite to Twenty CRM

Advance Practice Management Suite patient records map directly to Twenty's People object. Name, email, phone, address, and job title fields map to their Twenty equivalents. Original create timestamps are preserved as a custom field since Twenty sets CreatedDate at migration time. Owner resolution runs by email match against Twenty workspace members.

The practice or organization entity in the source becomes a Companies record in Twenty. Practice name maps to Companies.name, domain/website maps to Companies.website, industry is set to 'Healthcare' or mapped to a custom pick-list. If the source stores parent-child practice relationships, those map to Companies' built-in parent-company relation.

Twenty has no native insurance or payer object. We create a custom InsurancePayer object with fields for payer name, policy type, and coverage notes, then link it to the corresponding People record via a custom relation field. If no InsurancePayer records exist, payer information collapses into a text field on the People record.

Active cases or patient encounters map to Twenty Opportunities. The case name becomes Opportunity.name, case status maps to a custom stage pick-list, and any monetary value (billing amount, expected reimbursement) maps to Opportunity.amount. If the source uses multiple case types, those map to distinct Opportunities with type labels so filtering works in Twenty's kanban view.

Scheduled appointments from the source become Tasks in Twenty linked to the corresponding People or Companies record. Appointment date maps to Task.dueDate, appointment type maps to Task.body or a custom Task.type field, and the assigned provider resolves by email to a Twenty workspace member. Completed appointments retain their original date as a custom completion-date field.

Billing claims have no native equivalent in Twenty's standard schema. We create a BillingClaim custom object with fields for claim ID, amount, status (submitted, paid, denied), and date. The claim links to the People record of the patient and the Companies record of the practice. Claim status values require value-by-value mapping since the source billing statuses are billing-specific.

Clinical or administrative notes from the source map to Twenty's built-in Notes object. Each note is linked to the related People or Companies record. Original note timestamps and author information are preserved in note metadata fields. Rich-text formatting in source notes is maintained where the source export format supports it.

Patient documents, signed forms, and uploaded files from the source are downloaded, uploaded to Twenty's file storage, and linked to the corresponding People or Companies record. File size limits on the destination apply (Twenty's default file upload limit). Inline images in clinical notes are extracted and re-hosted as attachments.

Source provider and staff records are matched by email to existing Twenty workspace members. If a provider has no matching workspace member, they are created as a Twenty person record flagged as a provider. Provider specialties and credentials map to custom fields on that person record.

Any custom properties on patient records (e.g., referral source, preferred contact method, insurance group ID) are migrated as custom fields on the Twenty People object. Field type is inferred from the source schema: text fields map to TEXT, pick-lists map to SELECT, date fields map to DATE. Custom field creation in Twenty requires Settings > Data Model > People > Add Field before migration inserts run.

Workflows, appointment reminder sequences, and billing alert automations from the source do not migrate. They require manual rebuild in Twenty's workflow builder or in an external automation tool. FlitStack exports workflow definitions as a reference JSON document for the rebuild team. The source system remains fully operational during this phase.