CRM migration
Field-level mapping, validation, and rollback between Gensolve Practice Manager and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Gensolve Practice Manager
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
12 of 12
objects map 1:1 between Gensolve Practice Manager and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Gensolve Practice Manager organizes healthcare practices around clients, appointments, practitioners, clinical notes, referrers, and integrated accounting—stored in a single-tenant Oracle database with per-practitioner FTE licensing. Dynamics 365 Sales (built on Dataverse) structures the world as Accounts, Contacts, Leads, Opportunities, Activities, and Products—using security roles, business units, and a unified API. The migration carries everything Gensolve stores natively (clients, appointments, practitioners, clinical note metadata, referrer relationships, custom fields) into Dynamics 365 Sales entities. The harder problems are mapping Gensolve's client and appointment model to Dynamics 365's Contact and Activity model, preserving practitioner-to-client relationships in Dynamics' Owner/User hierarchy, handling Gensolve's custom form fields in Dynamics' custom column system, and reconciling Gensolve's ACC billing data with Dynamics 365's invoice and order entities. We extract Gensolve data via their Public API and direct database export, transform records using field-level mapping, and load via the Dynamics 365 Web API with duplicate detection against Source_System_ID__c. Workflows, automations, and template logic in Gensolve have no Dynamics equivalent and must be rebuilt using Power Automate.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Gensolve Practice Manager platform overview
Scorecard, SWOT, gotchas, and pricing for Gensolve Practice Manager.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Gensolve Practice Manager object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Gensolve Practice Manager
Client
Microsoft Dynamics 365 Sales
Contact
1:1Gensolve clients (patients) map directly to Dynamics 365 Contacts. The primary contact address, phone, email, and emergency contact fields translate to Contact columns. Practitioners assigned as primary caregivers to a client become the Contact Owner in Dynamics, establishing the practitioner-client relationship within the standard Dynamics security model.
Gensolve Practice Manager
Client Organisation
Microsoft Dynamics 365 Sales
Account
1:1Where Gensolve stores referring organizations or corporate health clients, those map to Dynamics 365 Accounts. This includes medical clinics, allied health referral networks, and corporate wellness programs that generate client referrals. Personal patients who have no organization affiliation become Contacts without a parent Account, which is valid and common in Dynamics 365 Sales.
Gensolve Practice Manager
Appointment
Microsoft Dynamics 365 Sales
Appointment (Activity)
1:1Gensolve appointments map to Dynamics 365 Appointments with the practitioner as the Owner, client (Contact) as the regarding record, original start/end times preserved, and appointment status (scheduled, attended, cancelled) translated to Dynamics status values. All appointment details including duration, type, and practitioner notes are preserved in custom columns for complete historical continuity.
Gensolve Practice Manager
Appointment
Microsoft Dynamics 365 Sales
Task (Activity)
1:1Gensolve appointments with no specific time (e.g., follow-up items, session notes) can alternatively map to Tasks attached to the Contact record. These task-based activities preserve the client relationship context while accommodating the undated nature of follow-up items. The original appointment duration is stored in a custom field for reporting continuity across both appointment and task activity types.
Gensolve Practice Manager
Practitioner / Staff
Microsoft Dynamics 365 Sales
System User
1:1Gensolve practitioners and staff map to Dynamics 365 System Users. Email addresses serve as the matching key between Gensolve practitioner records and Dynamics user accounts. Unmatched practitioners are flagged before migration and assigned to a fallback owner while the Dynamics admin provisions their user accounts. Practitioner specialty and provider numbers are preserved as custom columns on the System User record.
Gensolve Practice Manager
Referrer
Microsoft Dynamics 365 Sales
Contact
1:1Medical referrers (other practitioners or clinics that refer patients) migrate as Contacts in Dynamics 365. A custom pick-list field Referral_Type__c distinguishes referrers from regular patient contacts and is created as a custom column in Dynamics. Referrer-specific information including provider numbers and referral source tracking is preserved in custom columns for reporting on referral source effectiveness.
Gensolve Practice Manager
Clinical Note
Microsoft Dynamics 365 Sales
Annotation (Note)
1:1Gensolve clinical notes and letters become Dynamics 365 Annotations attached to the patient Contact record. Original note timestamps, note type (subject), and practitioner author are preserved in the annotation metadata. Rich-text formatting is retained where Gensolve supports it, and attachments embedded in clinical notes are migrated as related file attachments to maintain document integrity.
Gensolve Practice Manager
Invoice
Microsoft Dynamics 365 Sales
Invoice
1:1Gensolve invoices map to Dynamics 365 Invoices where Dynamics 365 Sales or Business Central is available. Invoice line items translate to Invoice Details. Standalone Dynamics 365 Sales without Business Central stores invoice references as custom fields on the Contact for financial reconciliation.
Gensolve Practice Manager
Custom Form Field
Microsoft Dynamics 365 Sales
Custom Column (Column)
1:1Gensolve custom fields on any entity become Dynamics 365 custom columns with schema names prefixed by new_ (default publisher). Field data type is matched (text, number, picklist, date) to the appropriate Dataverse column type. Sales Professional limits custom tables to 15, so Enterprise licensing is recommended for heavy custom-field usage.
Gensolve Practice Manager
Site / Location
Microsoft Dynamics 365 Sales
Business Unit
1:1Gensolve multi-site configurations map to Dynamics 365 Business Units in Enterprise licensing. Each Gensolve site becomes a Business Unit with its own practitioners and records. Single-site Gensolve customers use a single Business Unit with Location stored as a custom column.
Gensolve Practice Manager
Document / Attachment
Microsoft Dynamics 365 Sales
Attachment (ActivityMimeAttachment)
1:1Files attached to Gensolve appointments, clinical notes, or client records are re-uploaded to Dynamics 365 as email attachments or notes with document bodies. The file naming convention preserves the original Gensolve file name for traceability. File size limits of Dynamics 365 apply (25 MB per file by default), and files exceeding this limit are chunked or linked via SharePoint document management integration.
Gensolve Practice Manager
SMS / Email Log
Microsoft Dynamics 365 Sales
Email (Activity)
1:1Gensolve SMS and email communications linked to clients are logged as Dynamics 365 Email activities on the Contact record. The original send timestamp, direction (inbound/outbound), and message content are preserved as activity columns. Communication threads are linked to the client Contact for complete conversation history visibility within the Dynamics 365 timeline view.
| Gensolve Practice Manager | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Client | Contact1:1 | Fully supported | |
| Client Organisation | Account1:1 | Fully supported | |
| Appointment | Appointment (Activity)1:1 | Fully supported | |
| Appointment | Task (Activity)1:1 | Fully supported | |
| Practitioner / Staff | System User1:1 | Fully supported | |
| Referrer | Contact1:1 | Fully supported | |
| Clinical Note | Annotation (Note)1:1 | Fully supported | |
| Invoice | Invoice1:1 | Fully supported | |
| Custom Form Field | Custom Column (Column)1:1 | Fully supported | |
| Site / Location | Business Unit1:1 | Fully supported | |
| Document / Attachment | Attachment (ActivityMimeAttachment)1:1 | Fully supported | |
| SMS / Email Log | Email (Activity)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Gensolve Practice Manager gotchas
Gensolve requires direct support coordination for data exports
Xero-linked invoices risk duplication without deduplication flags
Custom field registry is per-practice and requires enumeration before mapping
SMS and email template content is not stored as standalone records
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Coordinate Gensolve data export and validate export file structure
FlitStack initiates contact with the Gensolve account manager to request a full database export covering clients, appointments, practitioners, referrers, invoices, and custom form field definitions. Upon receipt, we validate record counts, date ranges, and column completeness against the Gensolve data model. Any gaps in the export are flagged immediately so additional data pulls can be requested before mapping design begins. This step typically takes 3–7 business days depending on account manager availability.
Design Dynamics 365 schema: custom columns, tables, and Business Units
Based on the Gensolve data export analysis, FlitStack produces a Dynamics 365 schema plan covering custom column creation (new_customfield naming), custom table creation for junction entities (e.g., ClientPractitioner), and Business Unit setup if Enterprise licensing is in scope. The schema plan is delivered as a numbered checklist so the Dynamics admin can pre-create all required objects before the migration validation run. Custom column data types are matched to source field types (text, integer, datetime, picklist) to prevent truncation or type errors during data load.
Resolve practitioners to Dynamics 365 System Users by email match
Gensolve practitioners are matched to existing or provisioned Dynamics 365 System Users using email address as the primary key. Unmatched practitioners are listed in a pre-migration owner resolution report, requiring the client to either provision corresponding Dynamics user accounts or assign those records to a designated fallback owner before the migration run. No record lands in Dynamics without a resolved OwnerId. Practitioner-specialty and practitioner-type metadata is preserved as custom columns on the System User record.
Run sample migration with field-level diff on 100–500 records
A representative sample spanning clients across appointment types, referrer relationships, and practitioners is migrated to a Dynamics 365 sandbox environment. FlitStack generates a field-level diff report comparing Gensolve source values against Dynamics target values for every mapped column. The client reviews the diff to verify appointment timing, practitioner ownership, referrer classification, and custom field population. Any mapping corrections are applied to the migration configuration before the full run is scheduled.
Execute full migration with delta-pickup window and audit log
The full migration loads all Gensolve records into Dynamics 365 Sales. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in Gensolve during the cutover period. Every migration operation is written to an audit log including source record ID, target record ID, operation timestamp, and operator. If reconciliation against the Gensolve export file reveals gaps, one-click rollback reverts all Dynamics records and the migration is re-run with corrected mapping.
Platform deep dives
Gensolve Practice Manager
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Gensolve Practice Manager and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Gensolve Practice Manager: Not publicly documented.
Data volume sensitivity
Gensolve Practice Manager doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Gensolve Practice Manager to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Gensolve Practice Manager to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Gensolve Practice Manager
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.