Migrate your D-Tools data

Projects are the primary container in D-Tools, grouping tasks, change orders, locations, and billing. We export Projects via CSV or ZIP and map them to the destination's project or job object. Change orders and milestones are preserved as sub-records.

Clients (Companies and Contacts) store billing and project association data. The GetClients API returns up to 500 records per request. We paginate across all records and map client fields to the destination's contact or account object.

Locations define where items are installed within a project (e.g., 'Main Floor', 'Conference Room B'). This is a D-Tools-specific taxonomy. We map Locations to destination tags or custom address fields and validate uniqueness per project during import.

Service Plans define recurring revenue agreements tied to completed projects. Dynamic pricing can reference project labor or product values. We preserve plan structure, billing frequencies, and feature flags, but note that dynamic pricing rules must be rebuilt manually at the destination.

Tasks are created within Projects and can have due dates, product associations, and attached documents. D-Tools Cloud tasks support checklists. We map tasks to destination tasks or subtasks and preserve assignee and status fields.

Change orders are modifications to accepted proposals, tracked with pending and approved status. We export change order records as line items and map approval status and dollar deltas to the destination's project or estimate object.

Field technicians clock in and out via mobile, tied to specific projects or service calls. We preserve time-entry records including user, date, project association, and duration. Billing rates must be mapped separately.

Invoices are generated from project milestones or service plans. We export invoice records including line items, payment status, and balance due. D-Tools Payments transaction history requires separate export and mapping to the destination's payment ledger.

The i3 Program is a proprietary product database with manufacturer pricing and specifications. It does not export as user data — it is a platform resource. We do not migrate the product library itself. Customer pricing lists and custom product associations may be exported separately.

User records (technicians, project managers, office staff) are exported with name, email, and role. We map D-Tools users to destination users and flag any custom permission configurations for manual review.

Documents, drawings, and photos attached to projects or tasks are exportable as part of the project ZIP. We include them in the migration package and map file references to the destination's document store. Large attachment volumes may require chunked transfer.

Custom report definitions built in the Report Explorer are D-Tools-specific report configurations, not raw data. We export the underlying data separately so it can be rebuilt in destination reporting tools.