Microsoft Dynamics 365 to Smokeball migration. Let agents do the data entry.
The import moves the easy records. The rest is your team copying accounts, notes and documents from Microsoft Dynamics 365 into Smokeball by hand. Caddi AI Agents do that part, then check both sides record by record.
- Built on your field map
- Every mismatch listed
- Keeps working after cutover
Microsoft Dynamics 365 to Smokeball: the short answers
For a clean mid-size move. Years of history in Microsoft Dynamics 365 add weeks of cleanup first.
For audit, cleanup and execution, on published 2026 ranges. Not counted: licenses and your own staff's time.
In Microsoft Dynamics 365 the primary record is account and contact; in Smokeball it is the matter.
No dedicated administrator needed.
The export is the easy part. The hours are in what the import skips.
Loading Smokeball is the part any vendor can do. What takes the time is every record that lands wrong or not at all: remapped fields, activity history, documents, and proving the result matches Microsoft Dynamics 365.
What carries over, and what your firm has to decide
Six things decide how clean this move is. Four need a decision from your firm before any data moves. Write down who made each one.
What no export carries across
- 01
Rules built into Microsoft Dynamics 365 as plugins and Power Automate flows. No export contains them, so document them before you switch it off.
- 02
Automations, reports, dashboards and permissions. They are rebuilt in Smokeball, not moved, so budget them as build work.
- 03
Connections to other tools. The DMS, billing, e-signature and the shared inbox each have to be reconnected to Smokeball and retested.
You make the decisions. Caddi AI Agents do the data entry.
Show an agent the task on a screenshare or describe it in chat, and change it in plain English as the mapping changes. AI builds it, verified code runs it, and every run is logged and reviewable.
Move the records
Agents read Microsoft Dynamics 365, apply your field map and load Smokeball. The mapping decisions stay yours. The typing does not.
File the documents
Agents file each document to the right Smokeball record with the right metadata, instead of a folder dump someone sorts later.
Cover the overlap
While both systems are live, agents copy new accounts and updates from Microsoft Dynamics 365 into Smokeball, so nobody enters everything twice.
Prove it matches
Agents compare Smokeball to Microsoft Dynamics 365 record by record and list everything that does not match, so you fix the gaps before anyone trips over them.
Then the agents stay
A migration tool leaves on cutover day. The work it ignored does not: intake email, signed documents and billing still have to reach Smokeball. The same agents keep doing that data entry across your tools, so the clean matters you just paid for stay clean.
How much hand entry is in your move?
Nobody quotes you for staff time. Put in your own numbers and see what the import leaves on your team.
Five phases, and who does each one
Spend your first two weeks on Microsoft Dynamics 365 and your last two checking the result. Migrations that go wrong almost always shortened one of the two ends.
- 1You decide
Audit Microsoft Dynamics 365
Count what is in there, find duplicates and records attached to nothing, and decide what stays behind. Get that signed off before mapping.
- 2You decide
Map against real records
Start from the field map above, then walk fifty live records field by field, including the messy ones.
- 3Caddi runs it
Dry run the full load
Load everything into a test copy of Smokeball, not a sample. Samples hide the failures that only show up at volume.
- 4Together
Cut over on a quiet window
Freeze Microsoft Dynamics 365, load Smokeball, reconnect every tool that talked to Microsoft Dynamics 365, then go live. Keep Microsoft Dynamics 365 read-only for at least a quarter.
- 5Caddi runs it
Reconcile
Compare Smokeball to Microsoft Dynamics 365 record by record and list everything that does not match. Keep that list with your records.
The longer version, with the evidence behind it, is in the CRM migration playbook.
The cost breakdown and the known quirks
Cost breakdown
- Data audit and cleanup
- $3,000 to $25,000
- Migration execution
- $5,000 to $50,000
- Target configuration
- Two to six weeks
- Ongoing administration
- Absorbed by existing operations staff
Published 2026 ranges. Smokeball pricing: From about $49 per user per month; four plan tiers.
Microsoft Dynamics 365 needs a named administrator and Smokeball does not, so the running cost drops with the license. The trade: any workflow built into Microsoft Dynamics 365 has to be rebuilt or given up.
Microsoft Dynamics 365 quirks to plan for
- Option sets and lookups need translating rather than copying.
- SharePoint-linked documents are references, not files, so document migration is a separate project.
- Plugins and Power Automate flows hold logic no export represents.
Getting data out: Dataverse export tooling and the Web API.
Smokeball quirks to plan for
- Automatically captured time records are a large dataset with no obvious home in most targets.
- Matter-type-specific field sets mean the same concept appears under several names.
- Document automation templates are Smokeball-specific and get rebuilt, not moved.
Who runs it: No dedicated administrator needed.
Microsoft Dynamics 365 to Smokeball migration questions
How do you migrate from Microsoft Dynamics 365 to Smokeball?
Five steps. Audit the Microsoft Dynamics 365 data, map fields against fifty real records, dry run the full set into a test copy of Smokeball, cut over on a quiet window with Microsoft Dynamics 365 frozen, then compare the two systems record by record. Getting data out of Microsoft Dynamics 365: Dataverse export tooling and the Web API. Documents move as a separate pass.
What does not transfer from Microsoft Dynamics 365 to Smokeball?
In Microsoft Dynamics 365 the primary record is account and contact; in Smokeball it is the matter. Activity history carries only in part: dates, authors and types usually survive, threads and structure often do not. And no export carries rules built into Microsoft Dynamics 365 as plugins and Power Automate flows; automations, reports, dashboards and permissions; connections to other tools.
How long does a Microsoft Dynamics 365 to Smokeball migration take?
Six to twelve weeks for a clean mid-size move. Firms with years of history in Microsoft Dynamics 365 should add several weeks of cleanup before any data moves.
Will Smokeball migrate my data from Microsoft Dynamics 365 for me?
Ask Smokeball's onboarding team exactly what their import covers, and get it in writing. Vendor imports usually handle the standard records. The usual gaps are activity history, documents, custom fields, anything connected to Microsoft Dynamics 365, and the reconciliation that proves the result matches. Those gaps are where the hand entry comes from.
Can Caddi do the Microsoft Dynamics 365 to Smokeball migration work?
Caddi AI Agents do the mechanical work of the move: they read Microsoft Dynamics 365, apply your field map, load Smokeball, file documents to the right record, and compare both sides record by record so you get a list of everything that does not match. Someone at your firm still makes the mapping decisions and signs them off. After cutover the same agents keep doing the data entry between Smokeball and the tools around it.
Who administers Smokeball afterwards?
No dedicated administrator needed. That is one of the reasons this move is lighter than a platform migration.
What are the compliance implications for law firms?
State retention rules and duties over the client file survive the migration. A gap in matter history is a finding, not a cosmetic issue, so keep the field map, the list of mismatches and the sign-offs with the records.
Let Caddi AI Agents do the data entry across Microsoft Dynamics 365, Smokeball and the tools around them.
Thirty minutes. Bring your field map or nothing at all, and leave with a plan for the records, the documents, the overlap and the reconciliation.
