Migrate from Gensolve Practice Manager to Freshsales

Gensolve Client records (patients) map to Freshsales Contacts. Client name splits into first_name and last_name; mobile and home phone map to Freshsales phone fields; address fields map directly. Gensolve ACC status and patient type become custom fields on the Contact record.

Gensolve Practitioner records do not have a direct CRM equivalent. FlitStack matches each practitioner by email address against Freshsales Users. Unmatched practitioners are flagged before migration — your team either provisions Freshsales user accounts in advance or practitioners land as Contacts with a practitioner flag for reference.

Gensolve appointments become Freshsales Events. Appointment type maps to Event subject, start and end times map to Freshsales event start/end, appointment status (attended, cancelled, no-show) maps to a custom Event Status field. The related Gensolve Client ID is preserved in a custom field for linking back to the Freshsales Contact.

Gensolve custom forms store clinical assessment data (objective/subjective forms, injury rehabilitation types, functional limitation scores) as form entries attached to a client. FlitStack extracts each custom form field and creates a corresponding Freshsales custom field on Contact, then populates the values. Form-level groupings are preserved as a custom field label prefix.

Gensolve Referrer records (doctors, specialists, gyms who refer patients) map to Freshsales Accounts. Referrer name becomes Account name, contact details map to the Account's address and phone fields. A custom Referrer Type pick-list (medical, allied health, fitness) is created in Freshsales and populated from Gensolve's referrer category.

Gensolve Clinic or Site records (physical locations where practitioners operate) merge into Freshsales Accounts. Multi-site practices may have several Gensolve Sites that each become a separate Freshsales Account with the site's address and a custom Site Code field. A top-level 'Head Office' Account can optionally be created to link child site accounts.

Gensolve tracks ACC claim numbers, ACC status (approved, pending, closed), and ACC injury type on the Client record. These become three separate custom fields on the Freshsales Contact (ACC_Claim_Number__c, ACC_Status__c, ACC_Injury_Type__c) so the ACC history is visible without leaving the contact record.

Gensolve recall reminders (follow-up appointments triggered by clinical protocol) convert to Freshsales Tasks on the Contact record with a due date matching the recall schedule. Task subject reflects the recall reason so sales or admin staff can action it. The original Gensolve recall type (e.g., post-treatment review, injury milestone check) maps to the Task subject, and the Gensolve recall interval (number of weeks or months) becomes the Freshsales Task due date calculated from the original appointment date. Each recall Task links back to the originating Contact so staff have full context when working through their task queue.

Gensolve inventory items (supplements, braces, medical supplies tracked for re-sale or clinical use) map to Freshsales Products. Product name, SKU, and unit price transfer directly. Stock quantity is stored as a custom field since Freshsales Products track price and description rather than live inventory counts.

Gensolve staff records (non-practitioner admin users) map to Freshsales Users by email match. Admin users who should not be CRM users are mapped to a Contact record with an Admin_Staff__c flag so the record is preserved but does not consume a Freshsales seat.

Gensolve invoices and billing transactions have no native Freshsales equivalent — Freshsales does not include an accounting module. FlitStack creates a Freshsales Deal record per client representing outstanding or historical billing, with invoice number, total amount, and payment status stored as custom fields. Full accounting history should be migrated to Xero or QuickBooks separately.

Gensolve clinical notes and letter templates contain structured clinical content that does not map cleanly to a standard CRM object. FlitStack exports these as Notes attached to the Contact record, preserving the note text and creation date. Clinical content should be reviewed for PHI before migration to ensure compliance with your data handling obligations.