Migrate from Nookal to Pipedrive

Nookal patients migrate directly to Pipedrive People records. Each patient's name, email address, phone number, and physical address fields transfer directly to the corresponding Pipedrive Person fields. The patient's unique Nookal identifier is preserved as a custom field called Source_System_ID__c to maintain full traceability throughout the migration and to enable reliable de-duplication against Pipedrive's auto-generated Person ID during subsequent delta runs.

Nookal practitioners resolve to Pipedrive user accounts by matching the practitioner's email address to an invited Pipedrive user. Unmatched practitioners are flagged before migration — the team either invites them to Pipedrive first or assigns their records to a designated fallback owner. Provider numbers and specialties from Nookal do not map to any Pipedrive user field and are stored as custom fields for reference.

Nookal sessions map to Pipedrive Activities. Each session's type (initial consultation, follow-up, telehealth) maps to the Pipedrive Activity type field (meeting, call, or task) by type-value mapping. The practitioner who ran the session resolves to the Pipedrive Activity owner by email match. Session duration, date, and patient association are preserved on the Activity record.

Nookal invoices map to Pipedrive Deals when they represent a billable service with commercial value. Invoice status (paid, pending, overdue) maps to the Pipedrive Deal stage by value mapping. The invoice amount maps to Deal value. For purely clinical billing that will remain in practice-management software, invoices are documented as a custom field rather than a Deal to avoid dual tracking of the same revenue.

Nookal patients can be associated with an organisation (employer, insurance group, or referring clinic). Where present, the organisation name migrates as a Pipedrive Organization. The Nookal organisation record's address and domain fields map to the Organisation's address and website fields in Pipedrive.

Nookal clinical notes attached to a patient session migrate as Pipedrive Notes linked to the relevant Person record. Notes preserve the original creation timestamp and practitioner as owner. Because Pipedrive Notes are free-text and not field-structured, clinical note metadata (type, session date, practitioner) is embedded in the note body during migration.

Nookal's Medicare/DVA claiming status is a healthcare billing construct with no Pipedrive equivalent. We preserve it as a read-only custom field on the Person record for audit reference, but the actual Medicare claiming workflow must continue in practice-management software. This field is informational only — Pipedrive cannot process Medicare claims.

Nookal tracks how patients were referred (GP referral, Google search, practitioner recommendation, etc.). This pick-list migrates as a custom pick-list field (Referral_Source__c) on the Pipedrive Person record. The Nookal referral-source values are mapped one-by-one to the Pipedrive pick-list; unmapped values are stored as free text in the same field.

Nookal appointment reminder settings (SMS reminders, reminder timing, confirmation rules) are a platform-specific notification configuration with no Pipedrive equivalent. Pipedrive has its own activity-reminder settings per user and per deal. We do not migrate reminder configuration; it must be reconfigured in Pipedrive's notification settings.

Nookal allows per-patient and per-practitioner custom properties. Each custom property is evaluated: if it describes a patient attribute it becomes a custom field on the Pipedrive Person; if it describes a practitioner attribute it becomes a custom field on the User record. Field type (text, number, date, pick-list) is preserved. Pipedrive's custom field hash-key system means each field receives a unique API key post-migration.

Nookal payment records (partial payments, payment method, receipt numbers) attached to an invoice are merged into the corresponding Pipedrive Deal as a custom multi-line text field or as a closed Activity note. Because Pipedrive has no native accounting module, detailed payment history is preserved as structured text rather than as a native object.

Nookal multi-location setups (clinic branches, satellite sites) map to Pipedrive Organisations named per location. For single-location practices, the location is stored as a custom field on the relevant Person and Deal records rather than as a separate Organisation. We surface this decision in the migration plan before the full run.