Migrate from NeoDeck Holdings to Pipedrive

NeoDeck Holdings patient records map to Pipedrive Persons. Name, email, phone, address, and demographic fields translate directly. The patient's primary facility assignment maps to a Person's primary OrganizationId — the facility must migrate as an Organization first so the foreign-key reference resolves correctly in Pipedrive.

NeoDeck Holdings facilities and provider groups map to Pipedrive Organizations. Organization name, address, phone, and industry fields translate directly. Multi-location setups where a single provider operates across several NeoDeck facilities generate multiple Organization records in Pipedrive — one per facility name and address combination.

NeoDeck Holdings appointment and encounter records map to Pipedrive Activities. The appointment type (initial consultation, follow-up, telehealth) becomes the Activity subject line. Start and end datetimes map to Pipedrive's due_date and due_time fields. A custom Activity type field preserves whether the source was an in-person visit or telemedicine session since Pipedrive's native activity type enumeration does not capture this distinction.

NeoDeck Holdings insurance profile records (carrier name, group number, subscriber ID, coverage type) have no Pipedrive native equivalent. These map to Pipedrive custom fields on the Person object — Insurance_Carrier__c, Insurance_Group_Number__c, and Insurance_Subscriber_ID__c. FlitStack creates these fields before the migration run so they are available during data loading.

NeoDeck Holdings clinical note content migrates as Pipedrive Activity records with the type set to 'note' and the note body populated with the original clinical content. Original create timestamps are preserved in a custom datetime field so the chronological history of notes is available in Pipedrive reporting.

NeoDeck Holdings user and provider accounts resolve to Pipedrive Users by email match. Unmatched providers are flagged before migration — the team either creates a corresponding Pipedrive user account or assigns records to a designated fallback owner. This step is required before any record with an owner assignment can land in Pipedrive.

Referral source data stored in NeoDeck Holdings (referring provider name, referral date, referral type) has no native Pipedrive field. These map to custom fields on the Person object. The referral source string migrates as a text field; referral date maps to a custom date field if the team wants to preserve temporal referral history.

If NeoDeck Holdings tracks service lines or product offerings (e.g., telehealth subscription tiers, billing service packages), those map to Pipedrive Products. Product name, code, and unit price translate directly. Pipedrive Products can be linked to Deals via the Product_ids array on the Deal object.

NeoDeck Holdings billing claim records (claim ID, billed amount, payer, status) can map to Pipedrive Deals if the team uses Pipedrive to track revenue-cycle milestones. The claim status (submitted, pending, paid, denied) maps to a custom Deal field rather than Pipedrive's native stage field, since the clinical billing lifecycle does not align with a standard sales pipeline stage sequence.

NeoDeck Holdings e-prescription records (medication name, dosage, prescriber, date) do not have a meaningful CRM equivalent in Pipedrive. These records migrate as Activity notes with a structured note body so the information is preserved for reference, but no attempt is made to map them into a Pipedrive native object — doing so would create orphaned records with no actionable CRM context.

File attachments stored in NeoDeck Holdings (patient documents, signed forms, imaging references) re-upload as file attachments on the corresponding Pipedrive Person or Organization record. Pipedrive's file size limit (25MB per file) applies — files exceeding this limit are flagged and the team decides whether to split or exclude.

NeoDeck Holdings custom objects related to patient clinical data (allergy list, diagnosis codes, provider specialty) map to custom fields on the Pipedrive Person record. Multi-select fields (e.g., a list of allergies) use Pipedrive's multi-select custom field type. Each unique diagnosis code set is mapped to a separate custom field keyed by the code system (ICD-10, CPT).