CRM migration

Migrate from D-Tools to Nutshell

Field-level mapping, validation, and rollback between D-Tools and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

D-Tools logo

D-Tools

Source

Nutshell

Destination

Nutshell logo

Compatibility

86%

12 of 14

objects map 1:1 between D-Tools and Nutshell.

Complexity

CModerate

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

D-Tools logo

D-Tools

What's pushing teams away

  • Support response times are slow — customers report delays in resolving queries and slow turnaround on pricing or feature estimates.
  • Steep learning curve for new users, particularly around the integrated product library and change-order workflows, leading to extended onboarding.
  • Small or distributed teams find the platform heavy for their needs, with feature gaps in real-time collaboration across multiple office and field locations.
  • Annual pricing lock-in and limited transparency around renewal increases create billing surprises for long-term subscribers.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How D-Tools objects map to Nutshell

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

maps to

Nutshell

Company

1:1
Fully supported

D-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

maps to

Nutshell

Person

1:1
Fully supported

D-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

maps to

Nutshell

Lead

1:many
Fully supported

D-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

maps to

Nutshell

Deal

1:1
Fully supported

D-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

maps to

Nutshell

Deal (custom field)

many:1
Fully supported

D-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

maps to

Nutshell

Deal

1:1
Fully supported

D-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

maps to

Nutshell

Deal (custom fields)

1:1
Fully supported

D-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

maps to

Nutshell

Company (custom field)

1:1
Fully supported

D-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

maps to

Nutshell

Custom field on Company/Lead

1:1
Fully supported

D-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

maps to

Nutshell

Task

1:1
Fully supported

D-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

maps to

Nutshell

Note

1:1
Fully supported

D-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

maps to

Nutshell

Not migrated

1:1
Fully supported

D-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

maps to

Nutshell

Not migrated

1:1
Fully supported

D-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

maps to

Nutshell

Owner (Person field)

1:1
Fully supported

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

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.

D-Tools logo

D-Tools gotchas

High

Dual product API split (Cloud vs. SI) requires product identification first

High

i3 Product Library is a platform resource, not user data

Medium

GetClients API caps at 500 records per request with pagination required

Medium

Service plan dynamic pricing rules must be manually reconstructed

Low

Custom report definitions do not transfer between D-Tools instances

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • D-Tools API rate-limit ceiling forces batched extraction

    D-Tools Cloud enforces 120 API calls per minute per API key and 10,000 calls per day per key. GetClients is capped at 500 records per request. These limits are non-negotiable and directly govern extraction speed — a D-Tools account with 15,000 clients will require at minimum 30 GetClients API pages alone, consuming significant minutes of the daily call budget. FlitStack pipelines the extraction with exponential backoff and respects the rate ceiling automatically, but large D-Tools datasets extend extraction timelines significantly compared to platforms with higher API throughput. We surface this constraint in the pre-migration audit so you can plan the migration window accordingly.

  • Proposal itemized line items require custom-field flattening

    D-Tools proposals store multi-line items with manufacturer, part number, quantity, unit price, and extended price per line. Nutshell Deals have a single monetary amount field with no native sub-line-item structure. The itemized block must be serialized into a multi-line custom text field on the Nutshell Deal. If a proposal has 40+ line items, this custom field becomes long and may affect readability in Nutshell's UI. We flag proposals with more than 20 items before migration so your team can decide whether to split into multiple Nutshell Deals or accept the serialized format.

  • Service plan recurring-billing data has no Nutshell equivalent

    D-Tools Service Plans track billing frequency, plan lengths, feature tiers, and dynamic pricing tied to project value. Nutshell has no native recurring-billing or subscription-management object — it is a CRM, not a billing platform. We migrate service plan details (plan name, frequency, price, features) as custom fields on the associated Nutshell Company record. Recurring billing logic and payment automation must be handled in a dedicated billing tool post-migration. We provide the service plan data as a structured CSV export to feed whichever billing system you adopt.

  • Item custom fields are unstructured in D-Tools

    D-Tools Item Custom Fields are defined in the Control Panel as free-form named fields, but their values are stored per item without enforced data typing. A field named 'Serial Number' might hold numeric serials in some items and text strings in others. Nutshell custom fields require a declared type (text, number, date, picklist). We inspect each Item Custom Field's actual value distribution during the audit phase to infer the appropriate Nutshell field type — values that mix text and numbers in the same field map to Nutshell long-text to avoid data truncation.

  • Location hierarchy collapses to text in Nutshell

    D-Tools Locations are organized hierarchically within a project (site > building > floor > room) and items are assigned to locations to specify installation points. Nutshell has no native location concept on Deals or Companies. We map the primary location to a custom text field on the Nutshell Deal, and additional nested locations are appended as comma-separated path strings (e.g., 'Main Office > Floor 2 > Conference Room A'). If location precision is business-critical, we recommend migrating location data as a separate export for use in a dedicated field-service or project-management tool alongside Nutshell.

Migration approach

Six steps for a successful D-Tools to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

D-Tools logo

D-Tools

Source

Strengths

  • Purpose-built for low-voltage system integrators with industry-specific terminology and workflows.
  • i3 Integrated Product Library delivers real-time manufacturer pricing for accurate proposals.
  • Cloud and on-premises (SI) products cover both SMB and enterprise deployment needs.
  • Field-first mobile experience for technicians reduces office-to-field communication gaps.
  • Service plan management supports recurring revenue and monitoring agreement billing.

Weaknesses

  • Two distinct products (Cloud vs. SI) with separate APIs complicate cross-product migrations.
  • Support responsiveness is a recurring pain point in customer reviews, especially for pricing estimates.
  • Limited third-party integrations outside of QuickBooks and common accounting tools.
  • Custom report definitions do not export — customers must rebuild dashboards at the destination.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Moderate CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across D-Tools and Nutshell.

  • Object compatibility

    B

    1 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

    C

    D-Tools: 120 API calls per minute and 10,000 API calls per day per key.

  • Data volume sensitivity

    B

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

Estimator

Estimate your D-Tools to Nutshell 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 D-Tools to Nutshell data migrations

Answers to the questions buyers ask most during D-Tools to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most D-Tools to Nutshell migrations complete in 3–5 days of clock time for under 5,000 total records. Datasets between 5,000 and 25,000 records typically require 1–2 weeks. Accounts exceeding 25,000 records — especially those with hundreds of proposals and service plans — extend to 3–4 weeks. The D-Tools API rate limit (120 calls/min, 10,000 calls/day) governs extraction speed on large datasets. We quote based on the pre-migration audit of your actual record counts and custom-field inventory.

Adjacent paths

Related migrations to explore

Ready when you are

Move from D-Tools.
Land in Nutshell, 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