Migrate from Advance Practice Management Suite to Pipedrive

Advance Practice Management Suite patient records map directly to Pipedrive Person objects. Fields including name, email, phone, address, and custom patient properties migrate as Pipedrive Person fields. Pipedrive requires an Organization to be present before linking a Person — the org must land first in the migration sequence.

Advance Practice Management Suite practice and organization records map to Pipedrive Organization objects. Fields including practice name, address, phone, website, and specialty map to Organization fields. Pipedrive uses a single org_id on Person records as the primary link — multi-location practices require one Organization per location.

Advance Practice Management Suite appointments and patient cases map to Pipedrive Deals. Pipedrive Deal fields (title, value, stage, close date) receive mapped values from appointment properties. Pipedrive's Deal object does not natively support appointment scheduling — appointment times and visit types migrate as custom fields on the linked Deal, or as linked Activities.

Advance Practice Management Suite appointment lifecycle stages (scheduled, confirmed, in-progress, completed, cancelled) map to Pipedrive Pipeline stage values. Each AdvancedPM pipeline becomes one Pipedrive Pipeline object with stage names remapped via value mapping. Stage probabilities and forecast categories are applied per Pipedrive stage configuration.

Advance Practice Management Suite appointment records migrate as Pipedrive Activity objects with type='appointment' or type='task'. The original appointment datetime, duration, provider, and status map to Pipedrive Activity subject, due date, and done flag. Pipedrive Activities link to Person and Organization records via the activity's person_id and org_id foreign keys.

Advance Practice Management Suite call logs and clinical notes map to Pipedrive Activities with type='call' or type='note'. The original timestamp, provider, and content migrate as Pipedrive Activity subject, due date, and body text. Pipedrive's Activity body field stores the note content with original create dates preserved in FlitStack's audit log.

Advance Practice Management Suite staff and provider records map to Pipedrive Users. Matching is performed by email address — if a Pipedrive User exists with the same email as an AdvancedPM staff record, the owner field on migrated records is assigned to that user. Unmatched staff records are flagged before migration so the team can invite them to Pipedrive first.

AdvancedPM custom fields on patient records (insurance carrier, referral source, patient type, chart number) require Pipedrive custom fields. FlitStack creates the custom fields in the target Pipedrive account using the account-specific field keys, then populates them during migration. Pipedrive custom field keys are 40-character hashes unique to each account — they cannot be pre-defined globally.

AdvancedPM custom fields on appointments (visit type, referring physician, authorization number, room number) map to Pipedrive Deal custom fields. These are created on the Deal object using the target account's field keys. Fields on appointments that had no Pipedrive equivalent are preserved as custom fields for reference rather than discarded.

AdvancedPM billing and claim records do not have a native Pipedrive equivalent. FlitStack migrates outstanding claim amounts as Pipedrive Deal value and claim status as a custom field (Claim_Status__c) on the linked Deal. Paid or settled claims are migrated as Deal notes or closed Deals with a paid custom field rather than as separate objects.

Advance Practice Management Suite multi-location setups store each location as a separate entity. Each location becomes its own Pipedrive Organization. Contacts associated with a specific location link via the Organization's org_id on the Person record. FlitStack splits the multi-location schema into individual Organizations, preserving the location name and address on each.

Advance Practice Management Suite referral source tracking (referring physician, referring organization, marketing channel) has no Pipedrive native field. FlitStack preserves referral source as a custom field on both the Person and the linked Organization — your team chooses the canonical location during migration planning.