CRM migration
Field-level mapping, validation, and rollback between D-Tools and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
D-Tools
Source
Nutshell
Destination
Compatibility
12 of 14
objects map 1:1 between D-Tools and Nutshell.
Complexity
CModerate
Timeline
3–5 days
Overview
D-Tools (System Integrator and Cloud) is purpose-built for AV and low-voltage system integrators — its data model centers on Clients, Contacts, Projects, Proposals with line items, Locations, Service Plans, and Item Custom Fields. Nutshell is an SMB CRM built around People, Companies, Leads, and Deals with a flat schema; custom fields are supported on People, Companies, and Leads only. These models diverge significantly: D-Tools' hierarchical proposal structure, location assignments, and service-plan billing records have no direct Nutshell equivalents and require structural flattening. We extract from D-Tools via its REST API (subject to a 120 calls/min and 10,000 calls/day ceiling, GetClients capped at 500 records per page) or via CSV export for larger datasets. We import into Nutshell via its JSON-RPC API using the account's API key. Workflows, automations, report definitions, integrations, and D-Tools product catalog links do not migrate — we document them as rebuild artifacts. Activities (tasks, notes) migrate with original timestamps. Owner resolution uses email matching against Nutshell users. A delta-pickup window captures any D-Tools records modified during cutover before you deactivate the source account.
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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a D-Tools object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
D-Tools
Client
Nutshell
Company
1:1D-Tools Client maps to Nutshell Company. Address, phone, website, and industry fields migrate directly. Multi-contact clients in D-Tools collapse to one Nutshell Company record; each named contact becomes a Nutshell Person linked to that Company. The mapping preserves all company-level information while consolidating multiple contact associations into the single company profile.
D-Tools
Contact
Nutshell
Person
1:1D-Tools Contact maps to Nutshell Person. First name, last name, email, phone, title, and address fields migrate directly. Owner resolved by email match against Nutshell users. Unmatched owners flagged for manual assignment before migration. This direct field mapping ensures all contact details transfer cleanly without transformation logic.
D-Tools
Contact
Nutshell
Lead
1:manyD-Tools Contacts flagged as prospective clients (no closed-won project) can route to Nutshell Lead instead of Person. We apply a status-based split: contacts with no project in D-Tools migrate as Nutshell Leads; contacts with active or past projects migrate as Nutshell People.
D-Tools
Proposal
Nutshell
Deal
1:1D-Tools Proposal (the estimate or quote document) has no direct Nutshell equivalent. Nutshell Deals store a name, amount, stage, and close date. We map the proposal name to Deal name, total value to Deal amount, and proposal status to a custom stage field. Itemized line items are preserved in a multi-line custom text field on the Deal for reference.
D-Tools
Proposal Line Item
Nutshell
Deal (custom field)
many:1D-Tools proposal line items (manufacturer, part number, quantity, unit price, extended price) are merged into a structured custom field on the Nutshell Deal — one concatenated block per proposal so the full itemized pricing survives in the record. Product catalog references that cannot be resolved are stored as plain text.
D-Tools
Project
Nutshell
Deal
1:1D-Tools Project represents an in-flight or completed installation. We map Project name and status to Deal name and stage; the winning proposal value maps to Deal amount. Projects without a proposal are migrated as Deals with a nominal $1 amount and a custom Project_Status__c field.
D-Tools
Service Plan
Nutshell
Deal (custom fields)
1:1D-Tools Service Plans track billing frequency, plan lengths, and features for recurring revenue clients. Nutshell has no recurring-billing object. We preserve service plan details as custom fields on the associated Nutshell Company or Deal — plan name, billing frequency, monthly/annual price, and feature list stored as text fields for reference.
D-Tools
Location
Nutshell
Company (custom field)
1:1D-Tools Locations organize items by installation site (building, room, zone). Nutshell has no native location concept. We map the primary project location to a custom text field on the Nutshell Deal; additional locations are appended as comma-separated values or as multi-value custom fields.
D-Tools
Item Custom Field
Nutshell
Custom field on Company/Lead
1:1D-Tools Item Custom Fields are free-form per-item data defined in the Control Panel. Nutshell supports custom fields on People, Companies, and Leads with structured types (text, date, number, picklist). We inspect each Item Custom Field, infer its data type, and create a matching Nutshell custom field on the appropriate object — unstructured text fields become Nutshell long-text fields.
D-Tools
Task / Activity
Nutshell
Task
1:1D-Tools tasks, milestones, and time logs map to Nutshell Tasks. Original create dates, due dates, assigned users, and completion status are preserved. Time logs are stored as a custom number field on the Nutshell Task. All task metadata including original timestamps and assignment information transfers directly without transformation.
D-Tools
Note / Attachment
Nutshell
Note
1:1D-Tools notes and file attachments on projects and clients migrate as Nutshell Notes attached to the corresponding Company or Person record. File attachments are re-hosted in Nutshell's attachment storage. Inline images from D-Tools notes are downloaded and re-uploaded to preserve visual content within the migrated records.
D-Tools
Workflow Rules
Nutshell
Not migrated
1:1D-Tools workflow rules trigger notifications and actions based on SI entity criteria. Nutshell automations cover email sequences and lead routing differently. Workflows are exported as D-Tools configuration JSON for a rebuild reference in Nutshell's automation builder — they must be manually reconstructed.
D-Tools
Report Definition
Nutshell
Not migrated
1:1D-Tools Report Definitions group and parameterize reports by category, location, or system. Nutshell's reporting is built-in and simpler. Report definitions are exported as D-Tools Report Explorer XML and provided as a reference document; Nutshell reporting is rebuilt based on exported data.
D-Tools
Owner / User
Nutshell
Owner (Person field)
1:1D-Tools users and owners are matched to Nutshell users by email address. If a D-Tools owner has no corresponding Nutshell user, their records are assigned to a fallback Nutshell user specified by your admin before migration. The original D-Tools owner ID is stored in a custom Source_System_Owner_ID__c field for traceability.
| D-Tools | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Contact | Lead1:many | Fully supported | |
| Proposal | Deal1:1 | Fully supported | |
| Proposal Line Item | Deal (custom field)many:1 | Fully supported | |
| Project | Deal1:1 | Fully supported | |
| Service Plan | Deal (custom fields)1:1 | Fully supported | |
| Location | Company (custom field)1:1 | Fully supported | |
| Item Custom Field | Custom field on Company/Lead1:1 | Fully supported | |
| Task / Activity | Task1:1 | Fully supported | |
| Note / Attachment | Note1:1 | Fully supported | |
| Workflow Rules | Not migrated1:1 | Fully supported | |
| Report Definition | Not migrated1:1 | Fully supported | |
| Owner / User | Owner (Person field)1: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.
D-Tools gotchas
Dual product API split (Cloud vs. SI) requires product identification first
i3 Product Library is a platform resource, not user data
GetClients API caps at 500 records per request with pagination required
Service plan dynamic pricing rules must be manually reconstructed
Custom report definitions do not transfer between D-Tools instances
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Audit D-Tools data via API and CSV export
We connect to D-Tools using your API key and extract all object types: Clients, Contacts, Proposals, Projects, Line Items, Locations, Service Plans, Tasks, and Notes. Because D-Tools enforces 120 calls/min and 10,000 calls/day limits, we run extraction in scheduled batches with backoff. For large datasets we supplement with CSV export via D-Tools' Project Item and Project List export features. We catalog every Item Custom Field and Service Plan field, noting their data types and value distributions. The audit output is a data inventory report shared with your team before mapping begins.
Build the D-Tools-to-Nutshell mapping specification
We produce a mapping specification document: each D-Tools object and field maps to a Nutshell object and field, with mapping type (direct, transformed, value-mapped, custom-field-required) annotated. For proposals we document the itemized line-item serialization strategy. For Item Custom Fields we specify the Nutshell field name, type, and target object. Service Plan fields are mapped to Company custom fields. We surface the Location flattening approach and the Owner email-matching rule. Your team reviews and approves the specification before any migration runs.
Resolve owners and prepare Nutshell custom fields
We cross-reference D-Tools owner email addresses against Nutshell user accounts. Unmatched owners are flagged with their D-Tools record count so your team can either create corresponding Nutshell users or designate a fallback owner. In parallel, we create all required Nutshell custom fields — Proposal_Line_Items__c, Service_Plan_Name__c, Project_Location__c, and any inferred Item Custom Field mappings — with the correct field types and field-level visibility settings.
Run sample migration and generate field-level diff
A representative slice of 50–100 records migrates first — covering a mix of Clients, Contacts, Proposals, Projects, and a Service Plan. We generate a field-level diff showing every source value and its destination counterpart, including the serialized proposal line-item block and custom field populated values. Your team verifies owner assignments, confirms proposal itemization is readable, and validates Service Plan fields on the correct Company records. We adjust the mapping until the sample passes your sign-off criteria.
Execute full migration with delta pickup
The full migration runs in batches respecting D-Tools' API rate limits. Migration order: Companies first (dependency for People), then People/Leads, then Deals with proposal data and itemized blocks, then Tasks and Notes. A delta-pickup window (24–48 hours) runs after the initial load, capturing any D-Tools records modified during the cutover window. All operations are logged in a FlitStack audit log. If reconciliation identifies discrepancies, one-click rollback reverts the Nutshell state to pre-migration and we re-run the affected batch.
Platform deep dives
D-Tools
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across D-Tools and Nutshell.
Object compatibility
1 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
D-Tools: 120 API calls per minute and 10,000 API calls per day per key.
Data volume sensitivity
D-Tools 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 D-Tools to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your D-Tools to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave D-Tools
Other ways to arrive at Nutshell
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.