Migrate from Denticon to Nutshell

Denticon patient records map directly to Nutshell People. The patient's name, contact information, date of birth, address, and insurance carrier all transfer as native Nutshell Person fields or custom fields. Original patient IDs are stored as a custom field for traceability and delta-run de-duplication.

Denticon providers (dentists, hygienists, specialists) can map to Nutshell People records for provider associations on patient records, or to Nutshell Users if the provider is also a CRM user. Most migrations preserve provider names as a custom picklist field on Person records and as a 'referred by' attribute on referrals.

Each Denticon Office ID (OID) within a PGID maps to a Nutshell Company record. The office name, address, and phone become the Company fields. Multi-office Denticon accounts create multiple Company records in Nutshell. The OID number is preserved as a custom field (Office_ID__c) for reconciliation.

Denticon appointments map to Nutshell Activities (tasks or events). The appointment date/time, provider, type, production code, and status transfer as activity fields. Completed appointments map as logged Activities with the original timestamp preserved; upcoming appointments can be modeled as future tasks linked to the Person.

Denticon referral tracking (referring provider, referral source, referral cost) has no direct Nutshell equivalent. We map referring providers to Nutshell Person records with a 'Referral Source' custom field, and referral cost to a currency custom field on the associated Person or Company. External referral form links are documented for manual re-establishment post-migration. FlitStack also provides a referral configuration document listing active referral links for re-setup in Nutshell.

Denticon insurance carrier records map to Nutshell Company records with 'Insurance Carrier' stored as a custom field on each. This allows reporting on patient insurance breakdowns without creating a separate insurance module.

Denticon treatment plans and clinical procedures have no equivalent in Nutshell's sales CRM. We extract treatment plan summaries and key procedure codes as text custom fields on the Patient Person record, and document the full treatment plan as a Note attachment for manual reference. This preserves the data without forcing dental clinical data into a sales object.

Denticon accounts receivable and ledger entries cannot map into Nutshell's CRM schema. We extract ledger balance summaries as a custom currency field (AR_Balance__c) and document billing history in a Note attached to the Person record. The full billing and RCM data should be maintained in Denticon or a dedicated RCM system.

Claim adjudication status, filing dates, and payment records have no CRM equivalent in Nutshell. These are captured as read-only custom field values (e.g., Claim_Status__c, Last_Filed__c) on the Person record for reference, but the full claims workflow must remain in Denticon's RCM module or a separate billing system.

Denticon allows two custom fields per entity (up to 25 alphanumeric characters each) in Office, Provider, Referral, and Account setup screens. These map to Nutshell's custom field system, which supports text, number, date, currency, and picklist types. Because Denticon's custom fields are entity-scoped and short (25 chars), we recommend expanding them to descriptive Nutshell custom fields with appropriate types and longer labels.

For multi-office Denticon accounts using a single PGID, the PGID is preserved as a custom field (Practice_Group_ID__c) on each migrated Company and Person record. This maintains the organizational hierarchy from Denticon within Nutshell's flat account structure, allowing teams to filter and report across all offices using the Practice_Group_ID__c field and Nutshell tags.

Denticon's automated patient communication campaigns (with quiet-hours settings from 9 PM to 7 AM) do not have an equivalent in Nutshell's CRM model. These must be rebuilt in Nutshell using its personal email sequences feature (Pro and Business plans) or a separate marketing automation tool. FlitStack exports the campaign configuration as a reference document for rebuild.