Migrate from Core Practice to Salesforce Sales Cloud

Core Practice patient records map directly to Salesforce Contacts. Every patient becomes one Contact. FlitStack AI maps first name, last name, email, phone, date of birth, address fields, and gender directly. The Core Practice patient ID (e.g., PAT-00421) migrates as a custom field (Core_Patient_ID__c) for traceability. Unmatched patients are flagged before migration commits.

The dental practice itself — the business entity — maps to a Salesforce Account record. Practice name, address, phone, and website fields map directly. For multi-location practices, each location is a separate Account with the corporate entity as a Parent Account via the ParentId field.

Core Practice appointments have no native Salesforce equivalent. FlitStack AI maps appointments to Salesforce Tasks with custom fields: Appointment_Type__c (pick-list: checkup, cleaning, root canal, emergency, etc.), Operator__c (lookup to Practitioner__c), Chair__c (text), Location__c (text), and Appointment_DateTime__c (datetime). Tasks link to the Contact (patient) and Account (practice).

Core Practice staff with a Salesforce license (associate dentists, office managers) resolve to Salesforce Users by email match. Staff without a Salesforce license — hygienists, assistants — map to a Practitioner__c custom object so their names can still be linked to appointments via the Operator__c custom field on Tasks.

Core Practice treatment plans include procedure code, description, status, estimated cost, and notes. FlitStack AI creates a Treatment_Plan__c custom object in Salesforce with custom fields for each element. Procedure codes map to Product2 so Salesforce Products carry the treatment catalog. Plan status uses a custom pick-list matching Core Practice values.

Core Practice procedure codes (D#### ADA codes or custom codes) and descriptions migrate to Salesforce Product2 records. The Product Name carries the procedure description, and the Product Code field carries the ADA code. UnitPrice on the Product2 represents the standard fee for the procedure.

Core Practice stores medical and dental history as structured text blocks per patient. FlitStack AI creates a Medical_History__c custom object with a lookup to Contact (patient), plus custom textarea fields for conditions, medications, allergies, and notes. Each patient gets one Medical_History__c record.

Core Practice insurance records include carrier name, policy number, group number, subscriber name, relationship, effective date, and termination date. FlitStack AI creates an Insurance_Policy__c custom object with a lookup to Contact, plus custom fields for each data element. Active vs. inactive status maps to a custom pick-list.

Core Practice invoice records — invoice number, amount, date, payment method, balance — map to a Billing_Record__c custom object with a lookup to Contact and an optional lookup to Treatment_Plan__c. Payment status uses a custom pick-list matching Core Practice values (Paid, Partial, Outstanding, Written Off).

Core Practice prescriptions include medication name, dosage, frequency, prescribing practitioner, and date. FlitStack AI creates a Prescription__c custom object with a lookup to Contact and to Practitioner__c. Dosage and frequency map to custom text fields. Prescriptions link to the relevant Treatment_Plan__c when available.

Core Practice file attachments — X-rays, consent forms, treatment images — re-upload to Salesforce Files. Files attach to the relevant Contact or custom object record via ContentDocumentLink. File size limits of 25MB per file in Salesforce apply; larger files are flagged before migration. Inline images in notes are downloaded and rehosted.

Core Practice appointment reminder sequences are platform-specific workflow configurations. Salesforce has no direct equivalent — appointment reminders require Salesforce Flow with time-based workflow actions or a third-party app from AppExchange. FlitStack AI exports the workflow definitions as a rebuild reference document for your Salesforce admin.

Core Practice prescription alert and recall workflows are platform configurations that do not exist in Salesforce. These automations must be rebuilt in Salesforce Flow. FlitStack AI provides a workflow audit export listing every configured alert, its trigger condition, and its action so your team can reproduce each sequence in Flow.

Core Practice custom properties — fields created by the practice outside the standard schema — map to Salesforce custom fields on the appropriate object. Each custom property requires a custom field created in Salesforce before migration (Label, API Name, data type, and pick-list values). FlitStack AI delivers a custom field creation plan as part of the migration package.

Core Practice staff records (practitioners, admin) resolve to Salesforce Users by email address match. Unmatched staff — those without a Salesforce User record — are flagged in the pre-migration audit. Your team decides whether to create Salesforce User accounts for each or map them to the Practitioner__c custom object.