Migrate from Visual Practice to Salesforce Sales Cloud

Patient records map to Salesforce Contact. Visual Practice stores first name, last name, date of birth, contact details, and address directly on the patient record. FlitStack AI resolves the mapping to Contact fields and creates a custom MRN__c field for the medical record number, which has no native Salesforce equivalent. A Contact's primary practice association maps to AccountId.

Visual Practice stores the affiliated practice or referring physician as a separate entity linked to the patient. This maps to Salesforce Account. The practice specialty or service type maps to Account.Industry via a value-mapping table. Parent-child practice hierarchies (if any) map to Account.ParentId. FlitStack AI creates a default 'Unassigned Account' placeholder for any patient whose practice link cannot be resolved.

Appointment records in Visual Practice carry appointment date, duration, type, status, and assigned provider. These map to Salesforce Events with Subject = appointment type, StartDateTime and EndDateTime from the date and duration fields, and Status mapped via a value-mapping table. Owner assignment resolves the Visual Practice provider to a Salesforce User by email match. Cancelled appointments migrate with IsChild = false and a custom Cancelled__c flag.

Visual Practice billing records — invoice number, payment amount, status, procedure code, and provider — map to Salesforce Opportunity. Amount = payment amount, StageName mapped from status (e.g., Paid maps to 'Closed Won'), CloseDate = payment date. Custom fields capture Invoice_Number__c, Payment_Status__c, and Procedure_Code__c. Note: detailed invoice line items map only if a Pricebook is configured; otherwise they surface as custom fields on the Opportunity.

Visual Practice insurance records link a patient to an insurance provider with policy number and group number. Salesforce has no native insurance carrier object. FlitStack AI creates an Insurance_Carrier__c custom field on Account for the carrier name and Policy_Number__c, Group_Number__c, and Subscriber_ID__c as custom fields on Contact. If multiple insurance plans per patient exist, an Insurance_Plan__c custom object with a lookup to Contact handles the N:1 relationship.

Visual Practice specialty-specific intake fields and compliance notes (e.g., consent forms, allergy flags, referral source) are stored as structured custom fields alongside patient records. FlitStack AI creates corresponding custom fields on Contact using the __c suffix (e.g., Referral_Source__c, Allergy_Flag__c, Consent_Status__c) before migration. Form structure metadata — field names, types, validation rules — is exported as a reference document for Salesforce admin rebuild.

Visual Practice staff, providers, and administrators map to Salesforce Users by email resolution. FlitStack AI matches Visual Practice owner/provider IDs to Salesforce User records by email. Any Visual Practice user without a Salesforce counterpart is flagged before migration — the team either creates the Salesforce User first or assigns those records to a designated fallback User to avoid orphaning appointment and billing records.

Visual Practice file attachments on patient records — such as scanned consent forms,lab results, or imaging links — re-upload to Salesforce Files (ContentDocument) or the Attachment object depending on file size and org configuration. FlitStack AI preserves the file name, content type, and linked-to record ID during re-upload. Inline images in notes are downloaded and rehosted in Salesforce.

Visual Practice insurance carrier entities do not map cleanly to a single Salesforce standard object. FlitStack AI migrates carrier name as Account.Name with a custom Insurance_Carrier__c checkbox to distinguish them from patient-practice Accounts. This allows reporting on insurance relationships without creating false Account records in the sales pipeline.

Lab results and imaging records in Visual Practice have no direct Salesforce equivalent. FlitStack AI migrates these as a Lab_Result__c or Imaging_Record__c custom object with a lookup to the parent Contact, preserving result date, test type, status, and a link to the original file. This keeps clinical data associated with the patient Contact record without cluttering standard Salesforce objects.