Migrate from D-Tools to Twenty CRM

D-Tools Clients map directly to Twenty Companies. We map Client_Name to Company name, Client_Address fields to address fields, and Client_Phone to the primary phone on the Company record. For Clients with multiple contacts, the primary contact becomes the Company point-of-record and others migrate as related People records.

D-Tools contacts attached to a Client migrate as Twenty People records linked to the corresponding Company via companyId. D-Tools stores contact name, email, phone, and job title; these map to Twenty's standard name, email, phone, and jobTitle fields. Custom contact fields become custom fields on the Person object in Twenty's data model.

D-Tools Items are product-or-service line items used inside proposals and projects. Twenty has no native product catalog object on the free or Pro tiers. We map Item_Name to a custom_text field and Item_Price, Item_Cost, and Item_SKU to custom_number fields on the Opportunity. For complex item catalogs, we create a Product custom object in Twenty linked to Opportunities by item ID.

D-Tools Proposals are scoped to a project and contain line items, pricing, and status. We map Proposal_Name to Opportunity name and Proposal_Value to a custom_number field (Twenty does not have a native deal amount field). Proposal status (Draft, Sent, Accepted, Lost) maps to Opportunity stage name, with a custom field preserving the original D-Tools proposal ID for traceability.

D-Tools Projects track the full lifecycle of an installation job — scope, locations, items, and status. Projects map to Twenty Opportunities where Project_Name becomes Opportunity name and Project_Value becomes a custom_number deal-amount field. Project status (In Progress, On Hold, Completed) maps to Twenty's opportunity stage values, which are configurable in Settings → Data Model before import.

D-Tools Locations organize items and scope within a project — a site address or room in a building. Twenty has no native Location object. We create a Location custom object with fields for name, address, and a relation to the Company (or Opportunity). Locations attach to Opportunities through a custom junction relation so project-level location context is preserved in Twenty's Kanban view.

D-Tools Service Plans track recurring service agreements with billing frequency and price. Twenty has no native recurring-billing object. We create a ServicePlan custom object with fields for plan name, billing frequency, monthly/yearly price, and a relation to the associated Company record. Service plan IDs and original terms are preserved as custom fields.

D-Tools Invoice records (generated from projects and proposals) have no direct equivalent in Twenty CRM. We preserve invoice data — invoice number, amount, date, and status — as a custom Invoice custom object linked to the Opportunity or Company. If the invoice count is low, we attach invoice summaries as Notes on the relevant record instead of creating a full custom object.

D-Tools workflow rules fire notifications or actions when entity criteria are met. Twenty's Workflow Builder handles automations but the logic cannot be migrated automatically. We export D-Tools workflow definitions (criteria, actions, triggers) as a rebuild-reference document for your Twenty admin. Workflows must be manually recreated in Twenty's Settings → Workflows after migration.

D-Tools stores a user reference (owner, creator) on Projects, Proposals, and Items. Twenty WorkspaceMembers are matched by email — the Owner_Email field on each D-Tools record is resolved against Twenty's member list. Unmatched owners are flagged before migration so your team can invite them to Twenty first or assign a fallback owner. No record lands in Twenty without a resolved owner.

D-Tools supports custom fields on Items, Clients, Projects, and Locations. Each custom field must be pre-created in Twenty's Settings → Data Model before import. We export the custom field schema from D-Tools, map field types (text, number, date, select) to Twenty field types, and include the creation step in the migration plan. Fields that do not yet exist in Twenty are created first; then the import runs.

D-Tools files attached to projects, items, or clients migrate as Twenty Notes attached to the corresponding record. File names and storage URLs are preserved in the Note body. Inline images and embedded documents are downloaded and reattached as Note files in Twenty. D-Tools' native file storage is not transferred — URLs stored as text fields point to D-Tools-hosted files until you migrate file storage separately.