CRM migration

Migrate from Smokeball to Microsoft Dynamics 365 Sales

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 logo

Smokeball

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

12 of 12

objects map 1:1 between Smokeball and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Smokeball logo

Smokeball

What's pushing teams away

  • Billing issues appear in 22+ G2 reviews, with users reporting disorganization in invoicing, problems with payment routing, and hard/soft cost misalignments between Smokeball and integrated accounting software like Xero or MYOB.
  • Missing features frustrate users, particularly poor search functionality across documents and the absence of auto-save, which leads to lost work and wasted time re-entering data.
  • Software bugs cause real operational pain—duplicate documents appearing in containers, slow performance under load, and files failing to load after upload, each cited 14+ times on review platforms.
  • Collaboration limitations and cumbersome document import processes are cited as missing features, making it difficult for multi-attorney firms to share and organize files efficiently.
  • Integration issues with third-party software, particularly after major updates, cause connectivity failures with Outlook, LawPay, and accounting tools that disrupt billing workflows.

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 Smokeball objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

SystemUser / User

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Custom Field (Matter_Type__c) on Opportunity

1:1
Fully supported

Smokeball 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)

maps to

Microsoft Dynamics 365 Sales

Task / Email / PhoneCall

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Custom Field or Opportunity Product Line Item

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Custom Fields (No_Equivalent)

1:1
Fully supported

Smokeball'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

maps to

Microsoft Dynamics 365 Sales

No Equivalent in Dynamics 365 Sales

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

SharePoint Document Location + Note / Attachment

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Contact with Custom Role Field

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Custom Field (Tags__c) on Contact / Opportunity

1:1
Fully supported

Smokeball 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

maps to

Microsoft Dynamics 365 Sales

Contact with Billing Role Flag

1:1
Fully supported

Smokeball 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.

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.

Smokeball logo

Smokeball gotchas

High

Document upload may not finish before Go Live

High

Data entry must halt during final LIVE migration cutover

Medium

Duplicate contacts are not detected during import

Medium

Closed and archived matters migrate after Go Live

Medium

Lower pricing tiers strip PDF functionality and auto time

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

  • Matter-to-Opportunity mapping creates a schema gap for legal billing

    Smokeball Matters carry billing constructs — open debtors balance, hard costs, soft costs, trust accounting — that have no native mapping to Dynamics 365 Sales Opportunity. Dynamics 365 Sales has no trust accounting model. We preserve financial fields as custom fields on the Opportunity or in a custom Dataverse table, but trust disbursements, client retainers, and billing configuration must be handled separately in your practice management or accounting software post-migration. Firms relying on Smokeball's billing engine should not expect Dynamics to replicate that workflow without significant custom development or integration with an external accounting tool.

  • Document re-upload requires SharePoint integration pre-configuration

    Smokeball documents are stored in Smokeball's document container system linked to matters. Dynamics 365 Sales stores documents via SharePoint integration or as record-level attachments. If the SharePoint integration is not configured before migration, documents land as Notes or Attachments on the Opportunity, which can hit the 25MB-per-file limit and degrade record performance. We require a confirmed SharePoint site structure and Dynamics document location configuration before we begin document migration. Firms that rely heavily on document retrieval should prioritize SharePoint setup during the pre-migration phase.

  • Smokeball staff-inactivity flags invert in Dynamics user model

    Smokeball marks staff as active or inactive within the firm record. Dynamics 365 Sales uses the IsDisabled flag on SystemUser, where disabled equals inactive. The mapping is a logical inversion: Smokeball active = Dynamics IsDisabled false; Smokeball inactive = Dynamics IsDisabled true. If this inversion is missed during mapping, inactive staff in Smokeball get active Dynamics user accounts, potentially exposing data to former employees. We apply the inversion explicitly and flag any staff without email addresses for manual resolution.

  • Activity-type taxonomy divergence causes partial mapping

    Smokeball activity types include document work, tasks, emails, and time entries — a legal productivity model. Dynamics 365 Sales uses ActivityPointer with subtypes Task, Email, PhoneCall, Appointment. Document work in Smokeball maps to Task in Dynamics with a note indicating document context. Time entries that are billable hours do not map to any native Dynamics entity — they require the custom Time_Entry__c table. Firms that rely on Smokeball's AutoTime feature for automatic time capture will lose that automation in Dynamics and need to rebuild it in Power Automate or the Dynamics timeline.

  • Opposing party and other-side attorney lack a native relationship model

    Smokeball captures the other side (opposing party, opposing counsel, other side attorney) directly on the Matter record with embedded contact fields. Dynamics 365 Sales Opportunities have a single primary contact via the CustomerId field plus Opportunity Contact Roles for additional contacts. We create opposing counsel and opposing party as separate Contacts with a custom Party_Role__c pick-list value and link them to the Opportunity via Opportunity Contact Roles or a custom junction table. This requires Dynamics admin sign-off on the relationship model before migration commits.

Migration approach

Six steps for a successful Smokeball to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Smokeball logo

Smokeball

Source

Strengths

  • Automatic time tracking via AutoTime captures billable activity without manual entry, directly improving firm collection rates.
  • Comprehensive document automation with Smokeball Toolbar in Microsoft Word enables rapid generation of standardized legal precedents and letters.
  • Built-in trust accounting and reporting satisfy law firm regulatory requirements out of the box.
  • Exceptional customer support with dedicated Client Success Managers and UK-based telephone support keeps small firms operational.
  • AI assistant Archie and Outlook integration reduce context switching for attorneys managing client communications.

Weaknesses

  • Billing issues appear frequently in reviews, with payment routing and cost allocation problems requiring manual intervention.
  • Search functionality across documents and matters is a known pain point, making it difficult to locate historical files efficiently.
  • Auto-save is not available, risking data loss if attorneys forget to save manually during document work.
  • Collaboration features are limited, making Smokeball less suitable for large multi-office or multi-attorney firms requiring real-time co-authoring.
  • Price increases have been reported by existing customers, and lower tiers strip critical features like PDF functionality and automatic time tracking.
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. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Smokeball: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Smokeball 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 Smokeball to Microsoft Dynamics 365 Sales data migrations

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

Can't find your answer?

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 consultation

Most Smokeball-to-Dynamics 365 Sales migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 200,000+ records or complex matter-to-opportunity mapping extend to 7–10 days. The longest planning step is configuring the Dynamics custom fields for practice-area pick-lists, party roles, and time-entry tables before data validation runs. Pre-configuration of SharePoint document locations also adds preparation time for document-heavy migrations.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Smokeball.
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