Migrate from Case.one to Microsoft Dynamics 365 Sales

Case status to statecode/statuscode value mapping requires pre-configuration in Dynamics 365

Case.one stores case status as a free-form custom field with values like Open, Pending Review, and Closed. Dynamics 365 Cases use a mandatory statecode/statuscode pair — every status value from Case.one must be defined as a valid statuscode under the correct statecode (Active or Inactive) before records land. If the statuscode combination is not pre-configured in Dynamics 365, the record will fail to import with a schema validation error. We deliver a status-mapping configuration plan before migration runs and can script the statuscode setup in the target Dynamics 365 environment.

Time entries and billing records have no native Dynamics 365 Sales equivalent — custom table creation required

Case.one time entries and billing invoices have no equivalent construct in standard Dynamics 365 Sales — there is no native time-tracking module, billing module, or invoice table in the Sales app. We create custom Dataverse tables (Time_Entry__c and Billing_Invoice__c) to hold this data, but these tables are separate from the core CRM workflow and do not trigger out-of-the-box Dynamics 365 processes. Teams relying on Case.one billing automation will need to rebuild invoice generation in Dynamics 365 Business Central or a third-party accounting tool as a post-migration step.

Power Platform API request quotas cap bulk migration throughput

Dynamics 365 Sales uses the Dataverse Web API which enforces per-user request quotas (5,000 to 100,000 requests per 24 hours depending on licensing tier). Large migrations with hundreds of thousands of records can exhaust daily quotas, requiring migration runs to span multiple days. We implement batch operations and request pacing to stay within allocated limits, but teams with Enterprise-tier Dynamics 365 (100,000 request/day limit) will experience faster migration throughput than Professional-tier environments (5,000 request/day limit).

Custom fields in Case.one require Dataverse custom column creation before migration validation

Every custom field in Case.one — practice area, billing rate, jurisdiction, opposing counsel, and any custom properties your firm has defined — requires a corresponding custom column to be created in the appropriate Dataverse table before field-level mapping validation can complete. Dynamics 365 Sales Professional enforces a 15-table custom-table limit while Enterprise allows unlimited custom tables. We audit Case.one custom field inventory during discovery and deliver a schema setup plan specifying the exact column names, data types, and pick-list values to pre-create in Dynamics 365.

Case-party relationships collapse to a single primary contact lookup plus connection roles

Case.one allows a case to have multiple contacts and companies as parties — opposing counsel, expert witnesses, co-counsel, and plaintiff/defendant organizations all associated with a single case. Dynamics 365 Cases support only one primary customer (Contact) lookup directly. We handle this by migrating the primary party as the Contact lookup and creating Dynamics 365 Connections on the Case record for secondary parties with role labels matching the Case.one relationship type. Connection roles must be pre-created in Dynamics 365 for every unique party-role label in your Case.one data.