CRM migration
Field-level mapping, validation, and rollback between D-Tools and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.
D-Tools
Source
Zoho CRM
Destination
Compatibility
11 of 12
objects map 1:1 between D-Tools and Zoho CRM.
Complexity
BStandard
Timeline
5–10 business days
Overview
D-Tools Cloud serves low-voltage system integrators with a project-centric data model: Clients (the company/contact parent), Projects (with tasks, milestones, and line items), Service Plans (recurring maintenance agreements), and a field-collaboration layer for technicians. The platform exposes data via a Cloud API limited to 120 calls per minute and 10,000 calls per day, with GetClients returning up to 500 records per page. Zoho CRM uses the standard Leads-Accounts-Contacts-Deals structure with a custom-module layer for business-specific objects, plus Blueprint workflows, Zia AI (Enterprise+), and an API credit system. We migrate D-Tools Clients to Zoho Accounts and Contacts, D-Tools Projects to Zoho Deals with custom fields for project metadata, Service Plans to custom Zoho modules, and activities (tasks, notes, attachments) to their Zoho equivalents. We preserve original create/update timestamps and owner assignment via email matching against Zoho users. Workflows, automations, D-Tools Payments configuration, and integrations (including the existing D-Tools-Zoho sync) cannot migrate — those must be rebuilt or reconnected manually after cutover. The migration runs against the D-Tools Cloud API using paginated extraction, transforming data through our mapping layer before bulk-loading into Zoho via the REST API, with a delta-pickup window capturing in-flight changes during the cutover window.
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 Zoho CRM, 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
Zoho CRM
Account
1:1D-Tools Client is the primary company/contact parent record. We map it to Zoho Account (Organization) with the Client name as Account Name, phone as Phone, and address fields mapped directly. For Clients with a single named contact, we also create a corresponding Zoho Contact record linked via Account Name lookup.
D-Tools
Client Primary Contact
Zoho CRM
Contact
1:1D-Tools stores one primary contact per Client (name, email, phone). We map to Zoho Contact with First Name, Last Name (parsed from the full name string), Email, and Phone. The Contact links to the migrated Account via Account Name matching. Secondary contacts on the Client require additional extraction and import as related Contact records.
D-Tools
Project
Zoho CRM
Deal
1:1D-Tools Projects are the core work-order entity with status, scheduled dates, and line-item scopes. We map to Zoho Deal (which Zoho labels as 'Potentials' in some UI contexts) with Project name as Deal Name, projected revenue from line items as Amount, and the Project status mapped to a custom Stage field since Zoho Deal stages are sales-pipeline oriented, not installation-status oriented.
D-Tools
Project Task
Zoho CRM
Task
1:1D-Tools Project tasks (checklist items, milestones, and assignments) migrate as Zoho Tasks. Task Subject maps from task name, Due Date from the task due date, and Status from D-Tools completion flag (Complete maps to 'Completed', open maps to 'Not Started'). Owner assignment resolves via email match against Zoho users.
D-Tools
Project Change Order
Zoho CRM
Deal + Custom Fields
1:1D-Tools change orders modify accepted proposals with separate pricing. We preserve change order records as a custom multi-line field on the Zoho Deal — storing the CO number, description, amount delta, and approval status. Multiple change orders on a single Project become multiple line entries in the custom field or separate child Deals depending on your Zoho configuration preference.
D-Tools
Service Plan
Zoho CRM
Custom Module (Service_Plan__c)
1:1D-Tools Service Plans store recurring maintenance agreements with plan lengths (monthly/annual), billing frequencies, features, and tax rates. Zoho CRM has no native equivalent. We create a custom Service_Plan__c module in Zoho with fields for Plan Name, Billing Frequency, Monthly/Annual Price, Features (multi-select), and a lookup to the Account. The plan status (Active/Expired) migrates as a pick-list field.
D-Tools
Project Attachment / Document
Zoho CRM
Attachments (Notes module)
1:1D-Tools stores drawings, photos, and documentation on Projects. We download each file and re-upload to the corresponding Zoho Deal as an Attachment. File size limits: Zoho caps individual attachments at 25MB. Larger files (e.g., CAD drawings) are flagged before migration so you can choose to store them externally and link via URL custom fields instead.
D-Tools
User / Owner
Zoho CRM
User
1:1D-Tools users (sales reps, technicians, project managers) are resolved by email match against Zoho CRM users. Unmatched users are flagged before migration — you either invite them to Zoho first or assign records to a fallback Zoho user. D-Tools roles and permission sets (Admin, Technician, Sales) have no direct Zoho equivalent and must be reconfigured in Zoho Profiles and Roles post-migration.
D-Tools
Project Location
Zoho CRM
Account Address Fields
1:1D-Tools Locations store installation-site addresses used across projects. If the location is a new site not yet in D-Tools as a Client, we create a separate Location record in Zoho as an Account with a Location Type custom field set to 'Installation Site'. The billing address remains on the Client-Account; the site address attaches to the Deal via custom address fields.
D-Tools
D-Tools Product Library Item
Zoho CRM
Product
1:1D-Tools maintains an integrated product library with manufacturer, model, description, and dealer pricing. We map these to Zoho Products with the product name, unit price from dealer pricing, and manufacturer as a custom field. Inventory quantity (if tracked in D-Tools) migrates to Zoho Product quantity on hand only if you enable inventory management in Zoho.
D-Tools
Project Line Item
Zoho CRM
Deal Line Items / Products
many:1D-Tools Project line items include products, labor, and miscellaneous charges with quantity, unit price, and extended price. We merge these into Zoho Deal Line Items linked to the migrated Product records, preserving quantity and pricing. Labor line items without a product counterpart migrate as a generic Zoho Product named 'Installation Labor' or as a custom line item field depending on your Zoho configuration.
D-Tools
D-Tools Workflow Rule
Zoho CRM
Blueprint / Workflow (not migrated)
1:1D-Tools Workflow Rules trigger notifications and actions based on SI entity criteria. These cannot migrate to Zoho — the trigger conditions, action types, and entity model differ fundamentally. We export your D-Tools Workflow Rule definitions as a structured JSON reference file so your Zoho admin can rebuild equivalent rules in Zoho Blueprint or Deluge scripts. Automations must be rebuilt; they are not transferred automatically.
| D-Tools | Zoho CRM | Compatibility | |
|---|---|---|---|
| Client | Account1:1 | Fully supported | |
| Client Primary Contact | Contact1:1 | Fully supported | |
| Project | Deal1:1 | Fully supported | |
| Project Task | Task1:1 | Fully supported | |
| Project Change Order | Deal + Custom Fields1:1 | Fully supported | |
| Service Plan | Custom Module (Service_Plan__c)1:1 | Fully supported | |
| Project Attachment / Document | Attachments (Notes module)1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Project Location | Account Address Fields1:1 | Fully supported | |
| D-Tools Product Library Item | Product1:1 | Fully supported | |
| Project Line Item | Deal Line Items / Productsmany:1 | Fully supported | |
| D-Tools Workflow Rule | Blueprint / Workflow (not migrated)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
Zoho CRM gotchas
API access requires Professional tier or above
Subform fields do not export cleanly via CSV
API credit consumption is non-linear
Export download links expire in 7 days
Owner (User) assignments require pre-mapped user IDs
Pair-specific challenges
Migration approach
Audit D-Tools API access and extract data manifest
We begin by validating API credentials against the D-Tools Cloud API and running a discovery extraction that inventories all Client records, Project records, Service Plans, Product library entries, and user accounts. This establishes the total record count per entity type, identifies records with missing required fields (email addresses for owner resolution), and surfaces D-Tools custom fields that may not appear in standard API responses. The manifest is delivered as a structured CSV summary for your review before we proceed to schema setup.
Configure Zoho CRM custom modules and custom fields
Before data loads into Zoho, we deliver a Zoho Setup Plan that specifies the custom Service_Plan__c module with all required fields, custom date fields on Deal for project timelines, and the DTCId reference fields on Account and Deal. Your Zoho admin (or our team acting with admin credentials) creates these in your Zoho sandbox or production environment. We recommend using a Zoho sandbox for the first migration run to validate field mapping and relationship resolution before touching live data.
Resolve D-Tools users to Zoho users by email
D-Tools user records are matched against Zoho CRM users by email address. For any D-Tools user without a corresponding Zoho user account, we flag the record before migration and assign records to a designated fallback Zoho user. This step prevents records from landing in Zoho with null owners. We also export D-Tools role definitions as a reference document so your Zoho admin can configure Zoho Profiles and Roles to approximate your current D-Tools permission structure post-migration.
Run a sample migration with field-level diff
A representative slice migrates first — typically 50–200 records spanning Clients, Contacts, Projects, Service Plans, and a sample of tasks. We generate a field-level diff report that compares source D-Tools values against the migrated Zoho values for every mapped field, including the custom fields and timestamp fields. You review the diff, verify the Service Plan custom module structure, and approve before the full migration run. This is the validation gate that prevents bulk data issues from reaching production.
Execute full migration with delta-pickup cutover
The full migration loads D-Tools data into Zoho CRM via the Zoho REST API, respecting API credit limits and D-Tools rate limits. After the initial load completes, a delta-pickup window (typically 24–48 hours) captures any records created or modified in D-Tools during the cutover period. All operations are logged to an audit file. One-click rollback reverts Zoho to its pre-migration state if reconciliation fails. After rollback is confirmed, you can re-run the migration with the updated delta included.
Deliver D-Tools workflow export and Zoho rebuild reference
Alongside the migrated data, we deliver the D-Tools Workflow Rules as a structured JSON export, a D-Tools role-permission matrix for Zoho Profile/Roles rebuilding, and a post-migration checklist covering: disabling the D-Tools-Zoho integration (if D-Tools is decommissioned), reconnecting Zoho integrations (Zapier, accounting connectors), and running record-count reconciliation between D-Tools and Zoho to confirm completeness. The workflow JSON captures all trigger conditions, action types, and entity criteria so your Zoho admin has a rebuild reference for Zoho Blueprint stages and Deluge scripts.
Platform deep dives
D-Tools
Source
Strengths
Weaknesses
Zoho CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between D-Tools and Zoho CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across D-Tools and Zoho CRM.
Object compatibility
All 8 core objects map 1:1 between D-Tools and Zoho CRM.
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 Zoho CRM migration scoping. Not seeing yours? Book a call.
Walk through your D-Tools to Zoho CRM 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 Zoho CRM
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.