Migrate from D-Tools to Pipedrive

D-Tools Projects map directly to Pipedrive Deals. The project name becomes deal title, estimated project value becomes deal amount, and the D-Tools project status (Active, Completed, Archived) maps to a corresponding Pipedrive pipeline stage. Owner assignment resolves by email match against Pipedrive users. Original D-Tools project create date is preserved as a custom datetime field.

D-Tools project metadata beyond standard deal fields — such as project type (residential/commercial/government), system scope summary, and project manager notes — requires a D-Tools Project custom object or custom fields in Pipedrive. FlitStack creates these in Pipedrive before migration and maps the data field-by-field.

D-Tools contacts (stored under the Clients API, max 500 records per request) map to Pipedrive People. The contact's name, email, phone, and company association carry over as direct field mappings. D-Tools contacts without an email are flagged during validation — Pipedrive requires at least one unique identifier for deduplication.

D-Tools organizations (the parent entity for contacts and projects) map to Pipedrive Organizations. Organization name, address, phone, and website transfer directly. D-Tools supports N:1 contacts-to-organization relationships, which collapse to a primary organization link in Pipedrive with additional relationships handled via Organization Contact Roles.

D-Tools Locations represent physical installation sites with parent-child hierarchies (site → room/zone). Pipedrive has no native location object. We flatten D-Tools location hierarchies into a custom Location__c text field on the Deal, and append full location details as an Activity note with original timestamps. If the location hierarchy is critical for reporting, we can generate a separate Locations custom object.

D-Tools items — whether equipment products, labor line items, or bundled packages — map to Pipedrive Products. The item name becomes product name, SKU becomes product code, and unit price transfers directly. Package items with multiple sub-components are preserved as product bundle information in a Pipedrive custom field since Pipedrive Products have no native sub-item hierarchy.

D-Tools allows 75 custom fields per item (20 text, 3 long text, 12 list, 12 number, 12 date, 12 boolean, 4 hyperlink). Pipedrive supports custom fields on Person, Organization, Deal, and Product objects. Each D-Tools item custom field is created as a matching Pipedrive custom field, preserving field type and option list values for list-type fields.

D-Tools Service Plans store recurring billing configuration (fixed or dynamic pricing, plan lengths, billing frequencies). These map to Pipedrive Deals with a Service_Plan__c custom field holding the plan name and terms. Recurring billing logic does not transfer — Pipedrive has no native recurring billing engine and requires a separate integration or rebuild.

D-Tools Workflow Rules trigger notifications and actions based on entity criteria. Pipedrive Automations handle similar triggers but use a different rule syntax and UI. Workflow logic does not migrate automatically. FlitStack exports the D-Tools Workflow Rule definitions as a structured JSON reference document that your Pipedrive admin can use to rebuild equivalent automations in Pipedrive's Automation builder.

D-Tools project attachments (drawings, spec sheets, photos uploaded to project records) are downloaded and re-uploaded to Pipedrive as Files attached to the corresponding Deal. Files are stored at Pipedrive's storage limits per plan tier. Inline images in D-Tools notes are extracted and re-hosted as Pipedrive file attachments.

D-Tools project statuses (e.g., Proposal, Engineering, Procurement, Installation, Completed) map to Pipedrive pipeline stages by value. We create a stage-to-stage mapping table before migration and apply it consistently. The probability and forecast category per stage must be reconfigured in Pipedrive since D-Tools does not store stage probability.

D-Tools users and owners on projects, contacts, and items resolve by email match against Pipedrive users. Users present in D-Tools but not yet invited to Pipedrive are flagged before migration. Records owned by unmatched users are assigned to a designated fallback Pipedrive user to avoid orphaned records.