Migrate from CaseManager to Microsoft Dynamics 365 Sales

CaseManager custom fields require D365 custom columns — Sales Professional caps at 15 tables

D365 Sales Professional enforces a 15-table limit for custom tables (including your custom case table). If CaseManager has more than 15 distinct custom fields spread across multiple case types, or if those fields belong to additional related objects, you may need to upgrade to Sales Enterprise before migration to avoid hitting the cap. We audit every CaseManager custom property pre-migration and flag whether your target license supports the resulting D365 schema. Custom columns on standard tables (Contact, Account) do not count against this limit — only custom tables.

Case-to-Opportunity routing requires a business decision before migration

If CaseManager cases represent in-flight sales rather than customer service requests, your team may want cases to map to D365 Opportunities instead of a custom case table. Routing to Opportunity gives you pipeline stages, probability, and forecast data — but D365 Opportunity records have a different field model than cases. We support either path (custom case table or Opportunity) but the decision changes every downstream field mapping. Resolving this before migration prevents rework that would trigger additional migration passes.

API rate limiting during export can extend migration timelines for large case volumes

CaseManager's REST API enforces per-endpoint rate limits that vary by subscription tier. Large case volumes (100,000+ records) risk hitting throttling errors if extraction runs during business hours. We schedule exports during off-peak windows and implement exponential backoff retry logic. For extremely large datasets, we split extraction into chunks per date range or case status and run nightly batches. This extends wall-clock time but prevents API errors that would require restarting incomplete migration runs.

Workflows, automations, and assignment rules do not transfer — must be rebuilt in Power Automate or D365 workflow designer

CaseManager workflows that auto-assign cases, trigger notifications, or enforce case-routing rules have no equivalent in D365 Sales. Microsoft Power Automate handles cloud workflow automation, and the native D365 workflow designer covers record-level processes. We export your CaseManager workflow definitions as a structured JSON blueprint your admin can use to rebuild equivalent logic. The rebuild is a separate workstream — plan 2–4 weeks for complex workflows.

SharePoint document library setup must precede attachment migration

D365 stores file attachments via SharePoint document libraries linked to records. Before we can re-upload CaseManager attachments, a SharePoint library must exist and be connected to the target case table via the D365 document management settings. We coordinate with your SharePoint admin to provision the library and configure the connection. If this setup is not complete before the migration window, attachments are deferred to a secondary pass after go-live.