Migrate from Pulse Digital Clinic to Nutshell

Pulse Digital Clinic has no public API — data export relies on built-in tools

Pulse Digital Clinic explicitly states no APIs are available, which means migration depends entirely on the platform's built-in data import/export functionality. If the export tool omits historical billing records, encounter notes, or prescription histories, those objects require manual extraction or re-entry. We validate every export against a pre-migration data audit to surface gaps before the migration runs — any omitted data objects are flagged with estimated re-entry time so your team can decide whether to include them manually or defer to post-migration entry.

Appointment history exceeds standard CRM activity tracking scope

Pulse appointment records represent the core clinical encounter log — timestamps, physician assignments, encounter types, and clinical notes all live in one object. Nutshell Tasks and Activities are designed for sales follow-ups, not medical encounters. We map appointments to Nutshell Tasks to preserve the timestamp and physician link, but encounter-specific clinical context (chief complaint, diagnosis codes, treatment notes) must live in Nutshell Notes or custom fields. Your team should test whether Note-based clinical context meets compliance and accessibility requirements in Nutshell before committing the full migration.

Billing and payment records require a custom object design in Nutshell

Pulse's patient billing module tracks invoices, payments, outstanding balances, and payment plans — none of which have a native Nutshell equivalent. Standard Nutshell Deals model sales opportunities, not billing receivables. We can map outstanding balances to custom fields on Deal records or create a separate custom object for billing summary, but the right approach depends on whether your team uses Nutshell Deals to track service agreements. We surface this decision point during the mapping planning phase and document the chosen design before data lands.

Multi-physician setups require owner resolution by email match

Pulse supports multi-physician and multi-clinic configurations, but Nutshell's owner model is user-account-based. Physicians in Pulse who do not have active Nutshell user accounts cannot be resolved automatically — their records land under a fallback owner or with physician name in a custom field. We flag unmatched physicians before migration so your team can either create Nutshell accounts for them or confirm the fallback rule. If physician-level visibility and reporting is required in Nutshell, account creation must precede the migration run.

Healthcare data compliance responsibilities do not transfer with data

Patient records in Pulse Digital Clinic are subject to healthcare data handling requirements. Migrating those records to Nutshell — a general-purpose CRM not designed as a HIPAA-covered entity by default — shifts the compliance posture to your organization. We document which fields contain protected health information (PHI) during the data audit so your team can assess whether Nutshell's data handling meets your compliance requirements or whether a separate healthcare-compliant storage layer is needed for clinical data.