CRM migration
Field-level mapping, validation, and rollback between Smokeball and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Smokeball
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
12 of 12
objects map 1:1 between Smokeball and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Smokeball organizes law firm data around Matters, Activities, Time Entries, and Trust Accounting — a schema designed for legal practice management rather than sales pipeline tracking. Dynamics 365 Sales structures data around Accounts, Contacts, Leads, and Opportunities using the Dataverse underlying model with table (entity) names and column names in Title Case or snake_case depending on the interface. The migration carries Smokeball contacts, companies, staff records, matter headers, and activity history into Dynamics 365 Sales tables. The harder problems are translating Smokeball Matters into either Dynamics Opportunities with custom fields or a custom Matter table, preserving billable time entries as Opportunity Product lines or custom currency fields, and handling Smokeball's trust accounting and billing constructs which have no native equivalent in Dynamics 365 Sales. We run a sample migration first with field-level diff, then a full cutover with delta-pickup for records modified during the switchover window. Workflows, document automation rules, and billing configuration do not migrate — we export Smokeball workflow definitions for your Dynamics admin to rebuild in Power Automate and the Dynamics configuration layer.
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
Smokeball platform overview
Scorecard, SWOT, gotchas, and pricing for Smokeball.
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 Smokeball 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.
Smokeball
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Smokeball contacts (clients, opposing counsel, witnesses) map directly to Dynamics 365 Contact. Address fields, phone numbers, email addresses, and salutation translate directly. Primary Matter association becomes a custom lookup field on Contact. Duplicate detection runs on email address to prevent redundant contact creation during migration.
Smokeball
Staff
Microsoft Dynamics 365 Sales
SystemUser / User
1:1Smokeball staff records (attorneys, paralegals, admin) map to Dynamics 365 Users. Email address is used for matching. Inactive staff in Smokeball become inactive users in Dynamics unless you specify otherwise. Staff without email addresses are flagged for manual resolution before migration commits.
Smokeball
Matter
Microsoft Dynamics 365 Sales
Opportunity
1:1Smokeball Matters are the core legal entity and map to Dynamics Opportunities as the closest pipeline analog. Matter number becomes Opportunity name prefix. Matter type (practice area) maps to a custom Opportunity field or category pick-list. Open balance from Smokeball becomes a custom currency field on the Opportunity.
Smokeball
Matter Type / Practice Area
Microsoft Dynamics 365 Sales
Custom Field (Matter_Type__c) on Opportunity
1:1Smokeball practice areas such as Family Law, Personal Injury, Real Estate, Criminal Defense, and Estate Planning have no direct Dynamics 365 equivalent. We create a custom pick-list field on Opportunity and map each practice area value one-to-one to ensure consistent categorization in your new CRM system.
Smokeball
Activity (Task, Document Work, Email)
Microsoft Dynamics 365 Sales
Task / Email / PhoneCall
1:1Smokeball activities tracked per matter map to Dynamics Activities. Document work, tasks, and emails map to Task and Email entities respectively. Original timestamps and owning staff are preserved during migration. Matter association links to the Opportunity via the regardingobjectid field to maintain context.
Smokeball
Time Entry
Microsoft Dynamics 365 Sales
Custom Field or Opportunity Product Line Item
1:1Smokeball time entries (hours, rate, description) do not map to a native Dynamics object. We can create a custom Time_Entry__c table in Dataverse linked to the Opportunity, or add time-entry fields directly on the Opportunity record for summary billing data. The custom table approach preserves full time-entry detail.
Smokeball
Hard Cost / Soft Cost
Microsoft Dynamics 365 Sales
Custom Fields (No_Equivalent)
1:1Smokeball's hard costs (court filing fees, expert fees) and soft costs (photocopying, postage) are legal billing constructs. Dynamics 365 Sales has no trust accounting model. We preserve cost records as custom fields for reference but they require manual reconciliation with your accounting software post-migration.
Smokeball
Trust Accounting / Client Retainer
Microsoft Dynamics 365 Sales
No Equivalent in Dynamics 365 Sales
1:1Smokeball trust accounting handles client retainers, escrow balances, and trust disbursements as a law-firm-specific financial model. Dynamics 365 Sales does not include a trust accounting module or any equivalent financial construct. These records must be handled separately in your practice management or ERP system post-migration.
Smokeball
Document / File Attachment
Microsoft Dynamics 365 Sales
SharePoint Document Location + Note / Attachment
1:1Smokeball documents linked to matters re-upload to SharePoint via Dynamics SharePoint integration. If the SharePoint integration is not configured, documents attach as Notes or Attachments on the Opportunity record. File size limits and SharePoint site structure are configured before migration.
Smokeball
Opposing Counsel / Other Side Attorney
Microsoft Dynamics 365 Sales
Contact with Custom Role Field
1:1Smokeball captures the other side attorney and opposing parties directly in the Matter record. These contacts migrate as Dynamics Contacts with a custom Party_Role__c pick-list field indicating whether the contact is opposing counsel, opposing party, or witness role. Opportunity Contact Roles link these to the matter.
Smokeball
Tags / Labels
Microsoft Dynamics 365 Sales
Custom Field (Tags__c) on Contact / Opportunity
1:1Smokeball tags applied to contacts or matters do not map to native Dynamics fields. We create a text field on both Contact and Opportunity capturing comma-separated tag values. Dynamics admins can later convert these to a proper multi-select pick-list or categories for improved filtering and reporting.
Smokeball
Debtor / Billing Contact
Microsoft Dynamics 365 Sales
Contact with Billing Role Flag
1:1Smokeball records a debtor on each matter for billing purposes. This contact receives a custom Billing_Debtor__c boolean flag migrated to Dynamics Contact. Invoice routing and payment terms need to be reconfigured in Dynamics billing settings post-migration to ensure proper AR management.
| Smokeball | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Staff | SystemUser / User1:1 | Fully supported | |
| Matter | Opportunity1:1 | Fully supported | |
| Matter Type / Practice Area | Custom Field (Matter_Type__c) on Opportunity1:1 | Fully supported | |
| Activity (Task, Document Work, Email) | Task / Email / PhoneCall1:1 | Fully supported | |
| Time Entry | Custom Field or Opportunity Product Line Item1:1 | Fully supported | |
| Hard Cost / Soft Cost | Custom Fields (No_Equivalent)1:1 | Fully supported | |
| Trust Accounting / Client Retainer | No Equivalent in Dynamics 365 Sales1:1 | Fully supported | |
| Document / File Attachment | SharePoint Document Location + Note / Attachment1:1 | Fully supported | |
| Opposing Counsel / Other Side Attorney | Contact with Custom Role Field1:1 | Fully supported | |
| Tags / Labels | Custom Field (Tags__c) on Contact / Opportunity1:1 | Fully supported | |
| Debtor / Billing Contact | Contact with Billing Role Flag1: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.
Smokeball gotchas
Document upload may not finish before Go Live
Data entry must halt during final LIVE migration cutover
Duplicate contacts are not detected during import
Closed and archived matters migrate after Go Live
Lower pricing tiers strip PDF functionality and auto time
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 Smokeball data via API and review schema
FlitStack AI pulls Smokeball data using the Smokeball REST API — contacts, staff, matters, activities, time entries, documents, and notes. We review the extracted schema against the Smokeball data model documentation and flag any custom properties or user-defined fields that require a Dynamics custom field. We also identify matter types, billing structures, and tags that need value-mapping or custom field creation in Dynamics before the migration runs.
Configure Dynamics 365 Sales schema and custom fields
Before data moves, your Dynamics admin (or our team) creates the custom tables, columns, and pick-list values needed for the migration. This includes the Matter_Type__c pick-list, Party_Role__c on Contact, Time_Entry__c custom table, and Open_Balance__c currency field on Opportunity. We deliver a Dynamics schema setup plan specifying exact display name, API name, data type, and pick-list values so the admin can pre-configure before validation runs.
Resolve Smokeball staff to Dynamics users by email
Smokeball staff records are matched to Dynamics 365 Users by email address. Staff without email addresses are flagged before migration — your team either creates a Dynamics user account for them or assigns their records to a fallback user. No matter record lands without an OwnerId in Dynamics. Closed or inactive Smokeball staff are mapped to disabled Dynamics users for audit continuity.
Run a sample migration with field-level diff
A representative slice migrates first — typically 50–200 matters spanning multiple practice areas, a sample of contacts, activities, and time entries. We generate a field-level diff between the Smokeball source and the Dynamics destination so you can verify matter-type pick-list mapping, time-entry placement, document re-upload status, and owner resolution before the full run commits. Any mapping adjustments are made before the production migration window.
Cut over with delta-pickup for in-flight records
Full migration runs against Dynamics 365 Sales. A delta-pickup window (typically 24–48 hours) captures any matters, contacts, or activities modified in Smokeball during the cutover. Documents are uploaded to SharePoint via the configured document location. Audit log captures every operation, and one-click rollback is available if reconciliation fails. Post-migration, your team rebuilds Smokeball workflows and document automation in Power Automate using the exported workflow definitions we provide.
Platform deep dives
Smokeball
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Smokeball and Microsoft Dynamics 365 Sales .
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
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
Smokeball: Not publicly documented.
Data volume sensitivity
Smokeball 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 Smokeball to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Smokeball 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 Smokeball
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.