Migrate from The Practice to Microsoft Dynamics 365 Sales

The Practice Client maps to Dynamics 365 Sales Contact. Most client fields (name, email, phone) translate directly. Clients who represent an organization rather than an individual route to Account; The Practice's client_type field is used to determine the split — individual clients become Contacts, organization-named clients become Accounts with a related Contact.

When The Practice client record has a company name populated in the organization field, that record maps to Dynamics 365 Sales Account. The contact-level details (coach, primary service) are preserved as custom fields on the Account record. Account.Industry uses a value-mapped set based on the practice vertical.

The Practice Session has no direct Dynamics 365 Sales equivalent — sessions are not Leads, Opportunities, or standard activities. FlitStack creates a custom Dataverse table (new_Session) with a lookup to Contact (new_ClientId). Session status (scheduled/completed/cancelled) maps to a custom OptionSet (new_SessionStatus). Coach assignment maps to OwnerId on the custom table.

Completed and paid sessions in The Practice that represent recurring service revenue can be aggregated into a Dynamics 365 Sales Opportunity. Each session contributes to the Opportunity.Amount field; the SessionCount__c custom field on the Opportunity tracks the number of contributing sessions. This is an optional mapping for teams that want pipeline-level revenue tracking.

The Practice Invoice maps to the Dynamics 365 Sales Invoice entity only when the Dynamics tenant has Sales Professional or Enterprise licensed (Invoice requires the sales-document module). Invoice.Amount maps from The Practice invoice.total_amount. Invoice status (paid/overdue/void) maps to Invoice.StatusCode via value_mapping.

Each line item on a The Practice invoice — representing a session, package, or product — maps to a custom Dataverse table (new_InvoiceLineItem) linked to Invoice. The line item description, quantity, and unit price map to corresponding custom fields. ServiceType from The Practice maps as a lookup to a custom ServiceType table.

Every The Practice custom property on a Client record creates a new column in the target Dataverse table. The Practice stores these as string key-value pairs; they are type-inferred during discovery — date values become DateOnly columns, numeric values become Decimal, text remains Text. The SchemaName uses the new_ prefix per Dataverse convention.

Session notes written in The Practice migrate as Dataverse Annotation records linked to the new_Session custom table. The Note.Title uses the session date plus 'Session Note'; the Note.Body contains the full note text. Original timestamps are preserved in Annotation.CreatedOn. Rich-text formatting is stripped to plain text to match Dataverse Note field constraints.

The Practice users assigned as coaches map to Dynamics 365 Sales SystemUser records. Resolution is by email address — FlitStack matches The Practice user.email to the Azure Active Directory UPN of a Dynamics 365 Sales user. Unmatched coaches are flagged before migration; the account owner assigns them a fallback OwnerId or invites them to the Dynamics tenant first.

The Practice workflows — session reminders, follow-up triggers, client onboarding sequences — have no direct equivalent in Dynamics 365 Sales. These must be rebuilt in Power Automate or Dynamics 365 Sales business process flows. FlitStack exports The Practice workflow definitions as a structured JSON reference document for your admin to use as a rebuild guide.

The Practice email templates are not migrated. Dynamics 365 Sales uses Microsoft Copilot Studio or Power Automate for email automation; templates must be rebuilt using the source template text as reference. FlitStack preserves the template body text in a reference export file.

The Practice integrations — including calendar synchronization, payment processor webhooks, and Zapier automation zaps — do not have a migration path to Dynamics 365 Sales. Post-migration, these connections must be rebuilt: calendar sync uses the Dynamics 365 Sales Outlook or Teams integration natively; payment processor hooks are rebuilt as Power Automate connectors or third-party middleware; Zapier zaps are replaced with Power Automate cloud flows that trigger on Dataverse record events.

The Practice reports and dashboards do not migrate. The underlying data — session counts, billing totals, client retention — does migrate, so reports can be rebuilt in Dynamics 365 Sales native charts or Power BI. FlitStack provides a data dictionary of migrated fields to support the Power BI rebuild.

The Practice document attachments on client records migrate to SharePoint Online via the Dynamics 365 Sales SharePoint integration. File size limit is 10 MB per file via the Dataverse Attachments API. Inline images in session notes are extracted, rehosted as individual Note attachments, and linked to the session record.