CRM migration

Migrate from Best Case Bankruptcy to Microsoft Dynamics 365 Sales

Field-level mapping, validation, and rollback between Best Case Bankruptcy and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .

Best Case Bankruptcy logo

Best Case Bankruptcy

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

93%

14 of 15

objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

2–5 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Best Case Bankruptcy stores client records as case-centric data structures — debtors, co-debtors, creditors, assets, and liabilities organized by bankruptcy chapter and filing status. Dynamics 365 Sales operates on a fundamentally different model: Accounts for organizations, Contacts for individuals, and Leads for prospective records, with Opportunities tracking revenue pipeline. There is no native bankruptcy-chapter concept in Dynamics 365 Sales, and court filing status, exemption schedules, and petition data do not have CRM equivalents. FlitStack AI migrates the contact and organization layers from Best Case (debtor names, addresses, SSN fragments, case numbers) into Dynamics 365 Sales Contact and Account records, preserving a bankruptcy_case_reference custom field on each contact so your team can cross-reference original cases. Creditor records from Best Case map to Dynamics 365 Sales Accounts with a custom creditor_type field. Workflows, document templates, exemption logic, and e-filing integrations do not transfer — those require manual reconfiguration in Dynamics 365 or separate legal-technology tooling. The migration API approach reads Best Case records through the platform's export capabilities and writes to Dynamics 365 Sales via the Dataverse Web API, with bulk operations for record counts exceeding 10,000.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Best Case Bankruptcy logo

Best Case Bankruptcy

What's pushing teams away

  • Compatibility issues between desktop and cloud versions cause lost documents and sync failures with court filing systems, leading to filing delays.
  • Support response times frustrate users trying to resolve urgent e-filing errors before court deadlines.
  • Best Case has changed ownership through successive acquisitions, raising concerns that cost-cutting will degrade the product quality long-term.
  • Newer feature add-ons — consumer loan management, legal noticing — are seen as unnecessary bloat by solo and small-firm practitioners.
  • Periodic form layout redesigns introduce confusion; the 2023 form updates introduced duplicate-question wording that Best Case did not clarify adequately.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Best Case Bankruptcy objects map to Microsoft Dynamics 365 Sales

Each row shows how a Best Case Bankruptcy object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Best Case Bankruptcy

Debtor / Client

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Best Case debtor records (individual persons who file bankruptcy) map directly to Dynamics 365 Sales Contact records. The debtor's name, address, date of birth, and SSN last-four are extracted and written to Contact fields. A custom Bankruptcy_Case_Reference__c field links the contact back to the originating Best Case case number.

Best Case Bankruptcy

Debtor / Client

maps to

Microsoft Dynamics 365 Sales

Lead

1:many
Fully supported

Debtors who are prospective clients (not yet converted to active matters) may be staged as Dynamics 365 Sales Leads before being converted to Contacts once the case is opened. The split decision is based on whether the Best Case record has an active petition filed date — records without filing dates become Leads.

Best Case Bankruptcy

Creditor

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Best Case creditor records (organizations owed money by the debtor) map to Dynamics 365 Sales Account records. The creditor name, address, and claim amount are extracted. A custom Creditor_Type__c field captures whether the claim is secured, unsecured, or priority, preserving Best Case classification data.

Best Case Bankruptcy

Case

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Best Case case records do not map to Opportunities because bankruptcy cases are not revenue-generating in the sales sense. However, case records are linked to Contacts via custom fields so that Dynamics 365 Sales reporting can show open bankruptcy matters per contact. The Opportunity object is not used in this migration path.

Best Case Bankruptcy

Case Number

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Bankruptcy_Case_Number__c)

1:1
Fully supported

Because Dynamics 365 Sales lacks a native case‑number field, FlitStack creates Bankruptcy_Case_Number__c as a custom text field on Contact. The field is limited to 50 characters, indexed for rapid lookup, and configured with field‑level security so that only authorized roles can read the docket identifiers during migration and reporting.

Best Case Bankruptcy

Chapter Type

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Bankruptcy_Chapter__c)

1:1
Fully supported

Best Case chapter types (Chapter 7, Chapter 11, Chapter 13, Chapter 15) have no Dynamics 365 Sales native equivalent. FlitStack creates Bankruptcy_Chapter__c as a custom pick-list field on Contact, preserving the chapter value from Best Case so firms can segment contacts by filing type.

Best Case Bankruptcy

Filing Date / Petition Date

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Petition_Filed_Date__c)

1:1
Fully supported

The bankruptcy petition filed date from Best Case is stored as Petition_Filed_Date__c on the Dynamics 365 Sales Contact record, preserving the official filing timestamp for reporting and audit trails. The field is defined as a date attribute, included in contact searches, and used to drive date‑based workflow triggers such as status updates or follow‑up reminders.

Best Case Bankruptcy

Discharge Date

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Discharge_Date__c)

1:1
Fully supported

Best Case tracks the discharge date when the court releases the debtor from qualifying debts. FlitStack maps this to Discharge_Date__c on the Contact record, allowing Dynamics 365 Sales workflows to automatically update the contact’s status to "Discharged" after the date passes, and enabling compliance reporting on case closure timelines.

Best Case Bankruptcy

Attorney / Attorney Firm

maps to

Microsoft Dynamics 365 Sales

User (Owner)

1:1
Fully supported

Best Case stores the responsible attorney name per case. This maps to the Dynamics 365 Sales OwnerId field by email resolution — if the attorney has a Dynamics 365 user account, the contact is assigned to that user. Unmatched attorneys are flagged for manual assignment.

Best Case Bankruptcy

Co-Debtor

maps to

Microsoft Dynamics 365 Sales

Contact (secondary)

1:1
Fully supported

Best Case records co-debtors as separate person records within the same case. Each co-debtor becomes a separate Dynamics 365 Sales Contact, linked to the primary debtor Contact via a custom Co_Debtor_Relationship__c lookup field. Case reference and chapter fields are populated identically across co-debtor contacts.

Best Case Bankruptcy

Scheduled Asset

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Assets_Schedule__c)

1:1
Fully supported

Best Case asset schedules (real property, vehicles, bank accounts) are summarized as text blocks and stored in a custom field on the Contact. Full asset detail requires a separate custom entity or Notes attachment since Dynamics 365 Sales has no native asset schedule object.

Best Case Bankruptcy

Scheduled Liability

maps to

Microsoft Dynamics 365 Sales

Custom field on Contact (Liabilities_Schedule__c)

1:1
Fully supported

Best Case liability schedules (secured debts, unsecured claims) are summarized as text blocks and stored in a custom field on the Contact. Because Dynamics 365 Sales does not support multi‑row liability structures natively, FlitStack recommends creating a separate custom entity for detailed liability tracking if your practice requires granular, searchable debt records beyond the summary.

Best Case Bankruptcy

Activity / Court Calendar Event

maps to

Microsoft Dynamics 365 Sales

Task / Event

1:1
Fully supported

Best Case meeting‑of‑creditors dates and court deadlines are mapped to Dynamics 365 Sales Events. The original court date, time, and location are preserved in the Event description, and each Event is linked to the Contact record for the associated debtor. This allows your team to view upcoming deadlines in the Dynamics 365 calendar and trigger follow‑up tasks automatically.

Best Case Bankruptcy

Document / Petition PDF

maps to

Microsoft Dynamics 365 Sales

SharePoint / Notes Attachment

1:1
Fully supported

Best Case generates petition PDFs, schedules, and court-filed documents. These cannot be migrated to Dynamics 365 Sales as native objects. FlitStack exports the document set to a provided SharePoint location and creates a Note on the Contact record with a link. Re-filing in courts must be done through the appropriate CM/ECF system.

Best Case Bankruptcy

Exemption Analyzer Data

maps to

Microsoft Dynamics 365 Sales

No equivalent

1:1
Fully supported

Best Case includes an exemption analyzer that helps attorneys determine which assets are exempt under federal and state law. This tool has no Dynamics 365 Sales equivalent. The analysis output can be exported as a PDF and attached to the Contact record, but the logic cannot be transferred.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Best Case Bankruptcy logo

Best Case Bankruptcy gotchas

High

Software activation gate after renewal requires credit card entry

High

No public API — all exports are file-based or manual

Medium

Form version sensitivity means schedules filed in older editions may not re-file correctly

Medium

PACER calendar sync is a one-way pull, not a stored data object

Medium

e-filing authentication errors block court submissions without clear diagnostics

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Bankruptcy case data has no native CRM entity in Dynamics 365 Sales

    Dynamics 365 Sales is built around the Account-Contact-Lead-Opportunity sales cycle. Bankruptcy cases — with their chapter type, filing dates, trustee assignments, and discharge status — exist only as custom fields on Contact and Account records. This means every case attribute requires a custom field, and there is no built-in way to model case-to-contact relationships as a separate entity. FlitStack creates the custom fields and populates them from Best Case exports, but the Dynamics 365 data model will look different from Best Case's case-centric layout. Firms should plan for a 2–3 week configuration period to finalize custom field layout, pick-list values, and form design before migration data lands.

  • PII handling in Dynamics 365 Sales requires field-level security planning

    Best Case stores debtor SSN (full or last-four), date of birth, and financial account numbers. Dynamics 365 Sales field-level security (FLS) must be configured for these fields before migration data arrives — by default, all users with Contact read access see all fields. FlitStack creates SSN-related fields with FLS restricted to System Administrator and a designated compliance role, but your Dynamics 365 admin must confirm the security role assignments match your firm's data handling policies. Mismanaged FLS on SSN fields creates a compliance risk if the system is audited.

  • Best Case document exports require separate SharePoint re-filing

    Best Case generates petition PDFs, exemption schedules, and court-filed documents as structured outputs tied to each case. Dynamics 365 Sales stores documents in SharePoint-backed Notes and Attachments, but there is no automated path to re-create the document tree from Best Case exports. FlitStack exports all available documents to a provided SharePoint library and creates Note records with download links on the corresponding Contact records. Re-filing in court CM/ECF systems must be done manually or through separate e-filing software — the Dynamics 365 Sales migration does not automate court submissions.

  • Dynamics 365 Sales Professional caps custom tables at 5 in standard licensing

    Dynamics 365 Sales Professional licensing limits custom tables (entities) to 5. Firms with complex creditor schedules, asset tracking, or multi-case debtor structures may exceed this limit on Professional licensing. The Enterprise license removes the custom table cap and allows unlimited custom tables and more complex Power Platform integrations. FlitStack's migration plan specifies which custom fields are required per table and flags whether the firm's target Dynamics 365 license tier can accommodate the schema without requiring an upgrade to Enterprise.

  • Co-debtor relationships require junction object or manual linking

    Best Case supports multiple co-debtors per case with each co-debtor as a separate record linked to the same case number. Dynamics 365 Sales does not have a native co-debtor relationship model between Contact records. FlitStack creates a custom Co_Debtor_Link__c lookup field on the Contact object that points from co-debtor Contacts to the primary debtor Contact. This requires confirming that the custom lookup relationship is supported under the firm's Dynamics 365 license tier and that the Contact form layout includes the co-debtor link field for cases where it is needed.

Migration approach

Six steps for a successful Best Case Bankruptcy to Microsoft Dynamics 365 Sales data migration

  1. Export Best Case data and profile record structure

    FlitStack extracts data from Best Case using the platform's export capabilities — typically CSV or structured report exports of debtor contacts, creditor records, and case metadata. We profile the export to identify record counts, field completeness, and any non-standard data patterns (multiple co-debtors, missing case numbers, inconsistent chapter-type values). This profiling step produces a data quality report before field mapping begins, so your team knows what needs cleansing or normalization before migration.

  2. Design Dynamics 365 Sales custom field schema

    Based on the Best Case data profile, FlitStack creates the custom fields on Contact and Account required to store bankruptcy-specific attributes: Bankruptcy_Case_Number__c, Bankruptcy_Chapter__c, Petition_Filed_Date__c, Discharge_Date__c, and others. We deliver a schema design document listing each custom field, its type, pick-list values, and field-level security designation. Your Dynamics 365 admin creates the fields in the target environment before the migration run.

  3. Map debtor and creditor records to Contact and Account

    FlitStack maps Best Case debtor records to Dynamics 365 Sales Contacts, applying the custom field schema for bankruptcy attributes. Co-debtor records become separate Contact entries linked via the Co_Debtor_Link__c lookup. Creditor records map to Account entries with claim_amount and claim_type custom fields. Owner resolution by email ensures each record is assigned to the correct Dynamics 365 user — unmatched owners are flagged for manual assignment before the full run.

  4. Run sample migration with field-level diff

    A representative slice — typically 200–500 records spanning debtors, co-debtors, and creditors — migrates to a Dynamics 365 Sales sandbox first. FlitStack generates a field-level diff comparing source values against destination values so you can verify chapter-type pick-list mapping, date field translation, and PII field population. This validation step catches mapping errors before the full production run commits data. During this phase, we also verify that pick‑list values match the defined taxonomy, confirm that date fields preserve timezone information, and ensure that PII fields are populated according to security roles.

  5. Execute full migration with delta-pickup window

    The full record set migrates to Dynamics 365 Sales production using the Dataverse Web API, with bulk operations for record sets exceeding 5,000. A 24–48 hour delta-pickup window captures any Best Case records modified during the cutover. FlitStack generates an audit log of every record written, and one-click rollback reverts the migration if reconciliation against Best Case export totals fails. Post-migration, the SharePoint document export is delivered alongside a mapping reference for your admin to finalize form layouts and security roles.

Platform deep dives

Context on both ends of the pair

Best Case Bankruptcy logo

Best Case Bankruptcy

Source

Strengths

  • OneTouch™ e-filing has survived every court ECF transition since 2005 without a single manual re-entry requirement.
  • Built-in Means Test Calculator and Exemption Analyzer handle the most calculation-heavy portions of case prep automatically.
  • Due Diligence Reports import credit bureau data directly into forms, averaging 60 minutes of saved data entry per case.
  • PACER free-look integration and automatic court calendar sync replace a separate docket-monitoring subscription.
  • Client intake questionnaire enables fully remote initial consultations through a secure online portal.

Weaknesses

  • No publicly documented API means all data exports require file extraction, screen-scrape, or manual CSV pulls.
  • Compatibility issues between desktop and cloud versions cause document loss and court-sync failures.
  • Customer support quality is inconsistent; users report slow response times on urgent e-filing issues.
  • Frequent screen layout and form redesigns introduce friction for established users who have muscle-memory workflows.
  • Newer add-on modules (consumer loan management, legal noticing) are seen as unnecessary complexity by solo practitioners.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Best Case Bankruptcy and Microsoft Dynamics 365 Sales .

  • Object compatibility

    A

    All 8 core objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Best Case Bankruptcy: Not publicly documented.

  • Data volume sensitivity

    B

    Best Case Bankruptcy doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Best Case Bankruptcy to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Best Case Bankruptcy to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Best Case Bankruptcy to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Best Case Bankruptcy to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Best Case to Dynamics 365 Sales migrations complete in 2–5 business days for record sets under 25,000. Larger practices with 25,000+ debtor and creditor records, extensive co-debtor structures, or multi-case files extend to 5–10 business days. The custom field schema design and Dynamics 365 environment setup add 1–2 weeks of lead time before the migration run begins. The longest single step is typically the field-level diff validation in the sandbox environment, which your team reviews before production cutover.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Best Case Bankruptcy.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day