Migrate from Gensolve Practice Manager to Salesforce Sales Cloud

Gensolve's limited public API requires coordination with Gensolve support for data export

Gensolve Practice Manager does not expose a fully public REST API for self-service data export. Exporting clients, appointments, clinical notes, and custom fields typically requires engaging your Gensolve account manager and arranging a structured database export. This export must be delivered in a usable format (CSV, JSON, or SQL dump) before FlitStack AI can begin the migration mapping phase. Practices that have not yet arranged the export should contact Gensolve support early — export coordination can add 1–3 weeks to the project timeline. We include a Gensolve export checklist as part of the onboarding package so your team knows exactly what to request from Gensolve support.

Gensolve's clinical note structure has no Salesforce native equivalent and requires a custom object

Gensolve stores clinical notes (SOAP notes, treatment plans, clinical observations) linked to clients and practitioners in a format optimized for allied health documentation. Salesforce Sales Cloud has no native clinical note object — the standard Note and ContentNote objects are designed for general-purpose note-taking, not structured clinical data. FlitStack AI creates a Gensolve_Clinical_Note__c custom object with a Contact__c lookup, a rich-text Body__c field, a Note_Type__c pick-list, and a Practitioner__c lookup to the Salesforce User. This object is fully reportable and supports the original timestamps and note-type categorization from Gensolve, but it does not integrate with Salesforce Health Cloud or any clinical workflow automation without additional Salesforce Health Cloud licensing.

Gensolve practitioner records must resolve to Salesforce User accounts by email — unlicensed practitioners create Contact records

Gensolve practitioners are provider records with a name, email, and provider ID. In Salesforce, data record ownership is handled by User accounts. If a Gensolve practitioner will not receive a Salesforce user license (e.g., a part-time contractor or a practitioner who only needs to receive reports), their Gensolve data still migrates but they are created as Contacts with a Practitioner__c flag and the Source_System_ID__c field set to their Gensolve practitioner ID. This means their appointments in Salesforce will have an OwnerId pointing to a licensed Salesforce user rather than the practitioner themselves — a subtle but important distinction for appointment ownership reporting.

Gensolve workflows, SMS reminders, and appointment automations do not migrate to Salesforce Flow

Gensolve's appointment reminder workflows, SMS confirmation sequences, patient recall automations, and Xero sync rules are built within Gensolve's practice management logic. These do not have equivalents in Salesforce Sales Cloud — Salesforce Flow handles automation differently and requires a rebuild. We can export Gensolve workflow definitions (as documented by Gensolve support or captured from your Gensolve setup) to provide a rebuild reference for your Salesforce admin or FlitStack's automation team. The rebuild is quoted separately from the data migration.

Gensolve ACC billing and Xero accounting integration data maps to reference records only

Gensolve's ACC (Accident Compensation Corporation) claim records and Xero-linked invoice and payment data are financial and regulatory records that belong in an accounting or billing system, not a CRM. We migrate Gensolve ACC claim data and invoice history as custom objects for historical reference, but Salesforce does not natively process ACC claims or reconcile invoices. If your practice relies on Gensolve's ACC billing module, you will need to establish a separate ACC-compliant billing workflow in Salesforce or maintain the ACC system as the source of truth for claim management. We flag all ACC claim and invoice records in the migration plan and note the destination as reference-only.