Migrate from NextChapter to Microsoft Dynamics 365 Sales

Workflows and automations do not transfer — must rebuild in Power Automate

NextChapter workflows for court deadline reminders, Pacer notice alerts, debtor intake follow-ups, and case status triggers are proprietary automation logic. Dynamics 365 has no equivalent workflow import — these must be rebuilt from scratch using Power Automate cloud flows or the Dynamics 365 workflow designer. We export your NextChapter workflow definitions as a reference document so your admin can rebuild them in the correct sequence on the destination platform. To preserve your automation logic.

Sales Professional caps custom tables at 15 — Enterprise licensing required for large SALI field sets

In addition to the 15-table limit, the Professional tier caps the number of rows per custom table at 30,000 and restricts access to advanced features such as duplicate detection rules and AI-driven insights. Firms with large debtor bases often need to split SALI fields across multiple tables, which increases mapping complexity and may require additional data‑validation steps. Our planning audit documents each custom table and field relationship so you can decide whether the Enterprise tier’s unlimited capacity and enhanced security roles justify the licensing upgrade.

Pacer notice integration is platform-specific — must re-establish access in Dynamics

Pacer notice integration is platform-specific and does not migrate to Dynamics 365. Court docket access must be re-established by re-registering for PACER and configuring a separate integration or manual workflow. We preserve all case numbers, court jurisdictions, and docket identifiers in custom fields on each Opportunity so your team can re-link PACER access without re-entering case metadata. Additionally, PACER account fees and usage reporting are handled on PACER.gov and are independent of Dynamics 365; setting up a new PACER integration involves creating a Power Automate flow that polls the PACER API or uses an existing connector, and you will need to configure any required API keys or OAuth tokens.

Documents exceed Dynamics 365 attachment limits — require SharePoint Online

Dynamics 365 native notes/attachments cap at 131,072 characters per record. Bankruptcy filings with petitions, schedules, and court orders routinely exceed this. We export documents to SharePoint Online organized by case number, then store the SharePoint URL in a custom field on the Opportunity so attorneys access files inline from Dynamics 365 without leaving the CRM. The SharePoint library maintains each file’s original metadata, including creation date, author, and content type, and can be displayed within the Opportunity’s timeline using the document viewer. Power Automate can be configured to automatically update Dynamics 365 when new documents are added to the library, ensuring attorneys always see the latest filings without manual refresh.

Billing records have no CRM equivalent — must export separately

NextChapter billing records (attorney fee schedules, court cost trackers, payment plan installments) do not map to any Dynamics 365 CRM object. We export these as a dated financial report in CSV format for import into Dynamics 365 Finance, Business Central, or your preferred accounting tool post-migration. The financial report preserves original amounts, payment dates, and remaining balances. The export includes a header row with column names such as Invoice ID, Client Name, Service Date, Fee Amount, and Balance Due, allowing mapping to your accounting software’s chart of accounts. For multi-currency practices, FlitStack can add a currency field to the CSV and apply the exchange rate at the time of export.