Migrate from My Practice Now to Microsoft Dynamics 365 Sales

Dynamics 365 Sales has no native invoicing module — invoice data requires custom field provisioning

My Practice Now treats invoices as core data objects with line items, amounts, and payment status. Dynamics 365 Sales does not include a native invoice entity — it handles quotes and orders but not billing records unless your organization also licenses Dynamics 365 Business Central. FlitStack AI preserves invoice data as custom fields on the Account record (Total_Invoice_Amount__c, Invoice_Status__c, Balance_Due__c) and creates a reference Opportunity where a 1:1 relationship exists. Full invoice history with line items requires Business Central as a post-migration step, which we flag explicitly in the migration plan before any data moves.

Appointment-to-Activity conversion loses My Practice Now's native scheduling board

My Practice Now's scheduling interface is purpose-built for appointment management — staff calendars, appointment status workflows, and service-type routing are native features. When appointments migrate to Dynamics 365 Activities (Appointment and Task records), the scheduling context is preserved as field data but the native scheduling board does not exist in Dynamics 365 Sales. Teams that rely heavily on My Practice Now's visual scheduling calendar should plan to configure a scheduling solution using Dynamics 365's Calendar Control, Power Apps, or a third-party scheduling add-on post-migration. We flag appointment fields in the migration plan so your admin can map them to the chosen scheduling configuration.

My Practice Now's single-client model splits into Account and Contact, creating a mandatory population sequence

My Practice Now stores client data in one record. Dynamics 365 Sales separates business information (stored on Account) from individual contact information (stored on Contact). This split means every client record generates two rows in Dynamics 365 and requires the Account to exist before the Contact can be linked via the Primary Contact ID lookup field. FlitStack AI sequences the migration to create all Accounts first, then all Contacts with AccountId populated, ensuring referential integrity. If your My Practice Now data has clients without an email address, we surface those records for manual resolution before the migration runs.

Power Platform API request limits apply during bulk migration writes

Dynamics 365 Sales and the underlying Dataverse API impose request limits — the default allocation is 100,000 API requests per 24 hours per user. A large migration with hundreds of thousands of records (clients, appointments, invoices, notes) can exhaust the API quota during the migration run, causing HTTP 429 throttling responses. FlitStack AI implements exponential backoff on 429 responses and distributes writes across off-peak hours to stay within the Dataverse request allocation. For migrations exceeding 200,000 records, we coordinate a dedicated migration user with elevated API limits in partnership with your Dynamics 365 admin.

Dynamics 365 Sales Professional caps custom tables at 15 — Enterprise removes this limit

If your My Practice Now setup uses more than 15 custom fields across objects or stores data in custom practice-specific objects, the Dynamics 365 Sales Professional license enforces a 15-table ceiling that your migration will exceed. We audit your My Practice Now custom field count during discovery and confirm your Dynamics 365 license tier before migration planning. Upgrading to Sales Enterprise unlocks unlimited custom tables and removes this constraint — we include the license tier check as a pre-flight item in every My Practice Now migration plan.