Migrate from StrategicERP to Microsoft Dynamics 365 Sales

StrategicERP projects have no native CRM equivalent — custom fields on Opportunity are a functional workaround, not a full project management system

Dynamics 365 Sales is a CRM, not a project management or job-costing platform. StrategicERP Project records (with cost codes, work breakdown structures, budget vs. actuals, and change orders) cannot map to a single CRM entity. FlitStack's approach maps Projects to Opportunities with custom fields for project number, status, contract value, and manager name, plus a separate Work_Order__c custom table for field tasks. Finance teams expecting ERP-level project costing must continue using StrategicERP or migrate to Dynamics 365 Project Operations — the CRM layer provides sales visibility into the project pipeline but does not replace job-costing logic. This distinction between CRM opportunity tracking and ERP project costing must be communicated to stakeholders before go-live to prevent false expectations.

Invoice and Purchase Order records cannot live inside Dynamics 365 CRM tables — they become read-only reference data on the Account

StrategicERP Invoices and Purchase Orders are financial records tied to the accounts-payable and accounts-receivable modules. Dynamics 365 Sales has Quote, Order, and Invoice entities scoped to the sales cycle (proposal → order → invoice), not the procurement cycle. FlitStack stores original invoice and PO numbers as custom text fields on the Account record and keeps the actual invoice PDFs in SharePoint linked to the Account. This means the invoice aging report, payment status, and PO approval workflow remain in StrategicERP — the CRM Account shows a reference to the original document but does not own the financial lifecycle. Finance teams should be briefed on this separation before migration so they do not attempt to use Dynamics for AP/AR management.

Dataverse API rate limits require batched migration with 6,000-request-per-user-per-5-minute windows — large ERP datasets need orchestration

Microsoft Dataverse enforces a request quota of 6,000 API requests per user per 5-minute window for standard Web API calls. StrategicERP exports that include 50,000+ records across Contacts, Accounts, Projects, Work Orders, and Activities will exhaust this limit during a naive single-threaded migration. FlitStack uses batched API requests with exponential back-off, distributes load across multiple service-principal accounts, and leverages Dataverse Bulk API (available via Azure integration) for high-volume record inserts. The migration plan includes a rate-limit impact assessment during discovery so no records are silently dropped due to throttling. This is particularly relevant for migrations running against a Sales Professional tenant with the 15-custom-table limit, where additional tables must be created before the migration begins.

StrategicERP N:N contact-to-company associations with role labels collapse to one primary AccountId plus Account Contact Relationships

StrategicERP allows a single contact to be associated with multiple companies, each with a role label (e.g., Contractor at Customer A, Project Manager at Vendor B). Dynamics 365 Contact has a single primary AccountId field as its main company association. Additional company associations use the Account Contact Relationship entity, which supports a role name field but does not natively display a role label on every record view without custom form configuration. FlitStack migrates the primary company association as Contact.AccountId and creates Account Contact Relationship records for all secondary associations with the role name preserved. Teams that rely on seeing all company-role associations at a glance on the Contact form will need a sub-grid or Power Apps canvas component added to the Contact form post-migration.

StrategicERP automation logic, approval workflows, and custom business rules do not migrate — Power Automate is the rebuild target

StrategicERP workflows governing project status transitions, PO approval chains, work-order dispatch rules, and field-service escalation logic are ERP-layer automation that has no equivalent in Dynamics 365 Sales. FlitStack AI migrates data and schema only. Every StrategicERP workflow, sequence, approval routing rule, alert, and custom business rule must be rebuilt in Dynamics 365 using Power Automate, Dynamics workflows, or Power Apps. FlitStack delivers an Automation Audit Export that lists every active workflow in StrategicERP with its trigger conditions and actions so the Dynamics administrator has a rebuild reference. This is a key scope conversation to hold with the project sponsor early — automation rebuild effort is a significant post-migration task that is not included in the standard migration price.