CRM migration
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
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
14 of 15
objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
2–5 business days
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Best Case Bankruptcy platform overview
Scorecard, SWOT, gotchas, and pricing for Best Case Bankruptcy.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Microsoft Dynamics 365 Sales
Contact
1:1Best 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
Microsoft Dynamics 365 Sales
Lead
1:manyDebtors 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
Microsoft Dynamics 365 Sales
Account
1:1Best 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
Microsoft Dynamics 365 Sales
Opportunity
1:1Best 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Bankruptcy_Case_Number__c)
1:1Because 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Bankruptcy_Chapter__c)
1:1Best 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Petition_Filed_Date__c)
1:1The 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Discharge_Date__c)
1:1Best 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
Microsoft Dynamics 365 Sales
User (Owner)
1:1Best 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
Microsoft Dynamics 365 Sales
Contact (secondary)
1:1Best 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Assets_Schedule__c)
1:1Best 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
Microsoft Dynamics 365 Sales
Custom field on Contact (Liabilities_Schedule__c)
1:1Best 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
Microsoft Dynamics 365 Sales
Task / Event
1:1Best 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
Microsoft Dynamics 365 Sales
SharePoint / Notes Attachment
1:1Best 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
Microsoft Dynamics 365 Sales
No equivalent
1:1Best 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.
| Best Case Bankruptcy | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Debtor / Client | Contact1:1 | Fully supported | |
| Debtor / Client | Lead1:many | Fully supported | |
| Creditor | Account1:1 | Fully supported | |
| Case | Opportunity1:1 | Fully supported | |
| Case Number | Custom field on Contact (Bankruptcy_Case_Number__c)1:1 | Fully supported | |
| Chapter Type | Custom field on Contact (Bankruptcy_Chapter__c)1:1 | Fully supported | |
| Filing Date / Petition Date | Custom field on Contact (Petition_Filed_Date__c)1:1 | Fully supported | |
| Discharge Date | Custom field on Contact (Discharge_Date__c)1:1 | Fully supported | |
| Attorney / Attorney Firm | User (Owner)1:1 | Fully supported | |
| Co-Debtor | Contact (secondary)1:1 | Fully supported | |
| Scheduled Asset | Custom field on Contact (Assets_Schedule__c)1:1 | Fully supported | |
| Scheduled Liability | Custom field on Contact (Liabilities_Schedule__c)1:1 | Fully supported | |
| Activity / Court Calendar Event | Task / Event1:1 | Fully supported | |
| Document / Petition PDF | SharePoint / Notes Attachment1:1 | Fully supported | |
| Exemption Analyzer Data | No equivalent1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Software activation gate after renewal requires credit card entry
No public API — all exports are file-based or manual
Form version sensitivity means schedules filed in older editions may not re-file correctly
PACER calendar sync is a one-way pull, not a stored data object
e-filing authentication errors block court submissions without clear diagnostics
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
Best Case Bankruptcy
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .
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
All 8 core objects map 1:1 between Best Case Bankruptcy and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Best Case Bankruptcy: Not publicly documented.
Data volume sensitivity
Best Case Bankruptcy doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Best Case Bankruptcy to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Best Case Bankruptcy
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.