Migrate from My Practice Now to Salesforce Sales Cloud

My Practice Now client records map 1:1 to Salesforce Contacts. The client name splits into FirstName and LastName where available; single-field names populate the LastName field with FirstName left blank. Primary location/address data migrates to Contact.MailingAddress. Unmatched clients receive a placeholder Account assignment.

When a My Practice Now client represents a business entity (rather than an individual), the client name and business details migrate to a Salesforce Account first, then a Contact is created and linked via AccountId. This two-step routing happens automatically during the import sequence.

My Practice Now appointments map to Salesforce Events with original start and end datetimes preserved on Event.StartDateTime and Event.EndDateTime. The appointment status (confirmed, cancelled, no-show) migrates as a custom picklist field (Appointment_Status__c) on the Event record. If the appointment includes a location or staff assignment, those values map to custom fields on the Event as well.

Appointments classified as tasks (follow-up items, reminders without a scheduled block) split to Salesforce Tasks with Task.ActivityDate set to the scheduled date and Task.Subject carrying the appointment title. The original appointment ID is preserved as Source_Appointment_ID__c. These Tasks also link to the Contact via WhoId to maintain the client relationship in Salesforce.

My Practice Now invoices migrate as Salesforce Orders. Invoice line items map to OrderProducts with Product2 lookup where a matching product exists; otherwise items are created as text-line OrderProducts. Invoice payment status migrates to a custom field (Invoice_Status__c) on the Order record.

Invoice line items migrate to OrderProducts with Quantity, UnitPrice, and Description preserved. Total invoice amount recalculates from the loaded OrderProducts in Salesforce — the original total is stored in Total_Invoice_Amount__c for reconciliation. If any line item references a product that does not yet exist in Salesforce, FlitStack creates a placeholder Product2 record so the OrderProduct can be linked without data loss.

My Practice Now staff/practitioner records are matched to existing Salesforce users by email address. Unmatched practitioners are flagged before migration — teams either create Salesforce users first or assign records to a fallback owner. Practitioner specialty maps to a custom text field.

Client notes migrate as Salesforce Notes attached to the corresponding Contact record. Note.Title carries the note date and category; Note.Body carries the full text. Original create timestamps are preserved in CreatedDate after migration. If a client has multiple notes, each migrates as a separate Note record linked to the same Contact, preserving chronological order.

My Practice Now custom client fields are read from the export schema, then created as Salesforce custom fields on the Contact object (or Account if the field applies to a business entity). Field type is matched — text to Text, number to Number, date to Date, picklist to Picklist. Picklist values are exported and re-created in Salesforce.

Appointment-specific custom fields from My Practice Now (e.g., room, service type, cancellation reason) are created as Salesforce custom fields on the Event object before data loads. Each field's type is mapped from the source schema definition. These fields are added to the Event layout so users can view and edit them directly in the Salesforce UI after migration.

Multi-location My Practice Now setups store location/branch as a property of client or staff records. Salesforce has no native location field — we create a Branch__c custom picklist or text field on Account (for business clients) or Contact (for individual clients) and populate it from the source location value.

My Practice Now payment transaction history (payment method, amount, date) has no direct Salesforce Sales Cloud equivalent because Sales Cloud lacks native billing. We preserve payment records as Order_Payment__c custom fields and attach a PDF summary note so finance teams have the full history on record.