Migrate from Gensolve Practice Manager to Pipedrive

Gensolve client records map directly to Pipedrive People. Name splits into first_name and last_name. Email, phone, and address fields map to their Pipedrive equivalents. Client ID stored as Source_ID__c for traceability. Practices with multiple contact points per client (e.g., emergency contact) store the secondary as a custom field.

Gensolve practitioners are staff members, not patients. When a practitioner has a unique email address, FlitStack resolves it to a Pipedrive User by email match. Practitioners without email addresses (rare) must be created as Pipedrive users manually before migration, or their appointment records are re-assigned to a default user and flagged in the audit log.

Gensolve practitioners and clinic locations are stored as named entities with addresses. Both map to Pipedrive Organizations. The location address maps to org_address fields; practitioner name becomes the organization name. If the same person operates across multiple locations, each location becomes a separate Organization.

Gensolve appointments carry status (Booked, Confirmed, Cancelled, Completed), date/time, duration, practitioner, and location. Each appointment becomes a Pipedrive Activity: completed or confirmed appointments map to Meetings, cancelled appointments map to Tasks for follow-up review. Original start/end timestamps, practitioner assignment, and location are preserved as custom fields on the activity.

Gensolve referrers (external practitioners or clinics sending patients) become Pipedrive Organizations tagged with a custom field is_referrer set to true. The referral relationship between patient and referrer is stored as a custom organization field on the Person record. Referral-specific contact details (referrer phone, provider number) migrate as custom fields on the Organization.

Gensolve invoice and account data has no native Pipedrive equivalent — Pipedrive is a CRM, not an accounting system. Invoice totals, outstanding balances, and payment status migrate as custom fields on the related Deal for audit reference. Actual financial reconciliation must occur in Xero, QuickBooks, or a dedicated accounting platform post-migration.

Gensolve custom forms (assessment templates, intake questionnaires, injury-specific forms) define fields unique to each practice. These require pre-creation as Pipedrive custom fields on Person or Deal before migration. FlitStack extracts form field names and types from the Gensolve export and generates a Pipedrive field-creation plan. Field values from completed forms attach to the relevant Person record.

Gensolve clinical notes are text-rich records attached to a client and an appointment. They migrate as Pipedrive Notes attached to the Person record, with the original note date preserved. The associated practitioner name and appointment date are stored in the Note body for audit continuity. Attached documents (images, PDFs) are downloaded and re-uploaded to Pipedrive Files linked to the Note.

Gensolve treatment plans detail structured intervention goals and progress markers. These migrate as Pipedrive Notes with a treatment_plan flag in the Note title. If the treatment plan relates to a specific revenue-generating deal, it is attached to both the Person and the relevant Deal for cross-referencing.

Gensolve inventory items (supplements, consumables) can map to Pipedrive Products when the clinic uses Pipedrive Deals to track product-based revenue. Stock quantities and minimum-stock thresholds from Gensolve migrate as custom fields on the Product record. Inventory tracking with reorder logic does not have a Pipedrive equivalent and must remain in Gensolve or move to a dedicated inventory tool.

Gensolve SMS and email communication logs attached to client records migrate as Pipedrive email Activities on the Person record. Original send date, sender (practitioner), and message content are preserved. Two-way SMS threads that Gensolve logged as individual entries become a sequence of email Activities in chronological order.

Gensolve recall lists and birthday/follow-up outreach campaigns are healthcare-specific marketing automation with no Pipedrive equivalent. These lists export from Gensolve as Person records tagged with recall_date and recall_type. Pipedrive has no native recall or re-engagement campaign engine — this workflow must be rebuilt using Pipedrive's Automations or an external marketing tool post-migration.