How to switch from D-Tools and keep every room, rack and service plan intact
Short answer: decide first which half of D-Tools you are replacing. Many AV integrators keep D-Tools SI (or another design tool) for Visio and AutoCAD drawings and move projects, field work, closeout and service plans to an operations system. Then read your agreement for the renewal date, ask D-Tools for CSVs of clients, sites, project items with serials and MACs, the product catalog and your service plans, and save your as-builts and closeout packs as files. Move one install crew or the service desk first, and keep D-Tools readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first team runs real jobs the day after the setup call, on your own room types, stages and forms. Everyone else moves on a schedule you set. One price per company, with unlimited users, so installers, programmers and service techs all get a login.
Leaving D-Tools? See your setup first
Send us a D-Tools export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave D-Tools, with the facts checked
D-Tools has served AV, security and low-voltage integrators since 1998, and SI's design-to-bill-of-materials link is still the benchmark. Integrators who look elsewhere usually aren't unhappy with the drawings. They are unhappy with what happens after the proposal is signed: seats, add-ons, the accounting link, and the paperwork that gets the final invoice paid. Each point below was checked against D-Tools' own pages on 19 November 2026.
Every installer, programmer and service tech is a seat
D-Tools SI starts at $1,800 per user per year with a five-user minimum, and setup, catalog work and custom reports are billed as professional services at $200 an hour. On D-Tools Cloud, the entry plan includes one office user and one field user, and extra field users cost $12 to $25 a month each. Fieldproxy is one price per company with unlimited users, so a subcontracted rack builder or a seasonal installer gets a login without a budget meeting. See pricing.
source: D-Tools: System Integrator pricing (per user per year, 5-user minimum, professional services)source: D-Tools: Cloud pricing (plans, field users, accounting add-on, setup)
Accounting that only flows one way
D-Tools' own QuickBooks FAQ for SI says the link is mostly one-way: estimates and purchase orders go to QuickBooks, and product data comes back only by CSV export and import. On Cloud, QuickBooks Online, QuickBooks Desktop (Windows only) and Xero are a $50 a month add-on. Fieldproxy syncs two-way with QuickBooks Online, Desktop and Enterprise and with Xero, and deeply with Sage (invoices, bills, credit notes, suppliers). Exactly what syncs is agreed and tested during setup.
source: D-Tools: Frequently asked QuickBooks questions for System Integratorsource: D-Tools: QuickBooks integrationsource: D-Tools: Cloud pricing (plans, field users, accounting add-on, setup)
The closeout pack lives in a spreadsheet
Owner specs such as the DoD's UFGS 27 41 00 and Cornell's 27 41 16 ask for a device schedule per room (make, model, serial, IP, MAC, firmware), verification results, training sign-off and the uncompiled control code. Many integrators build that by hand beside the design tool. In Fieldproxy, serial and MAC are captured when the box is opened, IP and firmware at the bench test, and the room can't move to owner walk until its verification list and closeout pack are complete.
source: US DoD: UFGS 27 41 00 Audio-Visual Systemssource: Cornell University: Section 27 41 16 Integrated Audio-Video Systems
Service plans need a home that knows the room
D-Tools sells and schedules service plans in both SI and Cloud. What integrators struggle with is the years after the warranty: response clocks per plan tier, covered versus billable tickets, and alerts from Crestron XiO Cloud (email, SMS and an API) or Q-SYS Reflect (webhook and email). In Fieldproxy the warranty starts at acceptance on each room, the service plan carries its phone and onsite targets, and an alert can be set up to open a ticket on the right room with its clock already running.
source: D-Tools: System Integrator features (Visio, AutoCAD, project management, Mobile Install)source: D-Tools: Cloud pricing (plans, field users, accounting add-on, setup)source: Crestron: XiO Cloudsource: Q-SYS: Reflect overview
The Portal.io merger, and a renewal coming up
D-Tools and Portal.io announced their merger on 25 August 2026. The merger FAQ says there is no forced migration, no decision to combine the platforms, and current pricing continues under existing agreements, with notice before any change. Strata-GEE reports that private equity firm Greybull Stewardship has held majority ownership of D-Tools since 2016. Nothing changes today, but many teams use the next renewal to test whether a different split of tools fits better. That is a fair reason to look, not a reason to panic.
source: D-Tools: Portal.io merger announcement (25 August 2026)source: D-Tools: Portal.io merger FAQsource: Strata-GEE: Private equity owned D-Tools acquires Portal
Phones, texts and AI that do the follow-up
After a big install the service desk takes the โthe display in room 204 won't turn onโ calls. Fieldproxy's AI agents answer calls, texts and emails, log the ticket on the room, book the visit and chase signatures on change orders, with a person confirming changes where you want that. Through the Fieldproxy MCP server, Claude, ChatGPT or Copilot can read your rooms and service plans and create jobs or quotes, each change confirmed by a person.
Stay on D-Tools if
- Your business wins work on engineered drawings and your designers live in Visio or AutoCAD. D-Tools SI's drawing-to-BOM link is stronger than anything we do, so keep it for design even if operations move.
- Your books are in NetSuite or Sage 100 and the SI link is doing its job. Fieldproxy is not a general ledger, so check on the call how it would connect to your books.
- You are a small residential crew that mainly needs fast proposals. Portal.io or D-Tools Cloud costs less than a guided setup, and Fieldproxy is a guided setup, not a self sign-up.
- You are mid-term on SI. Read the term and renewal date first; you can build and test a Fieldproxy setup now and switch at renewal.
- Your D-Tools setup works and your team likes it. The merger FAQ says nothing is forced, so don't switch to solve a problem you don't have.
Before you go
What to export from D-Tools, and how
We didn't find a general data-export guide on D-Tools' site, so treat the routes below as questions to put to D-Tools support before your renewal. D-Tools' QuickBooks FAQ confirms CSV export and import for product data in SI, and SI's reports can usually be saved as files. Ask early: if setup or reports were built as professional services, a custom export may be billed the same way.
| Data | How to get it out of D-Tools | What happens to it in Fieldproxy |
|---|---|---|
| Clients, sites and contacts | Ask D-Tools for a CSV of clients, sites and contacts, with the D-Tools IDs. | Client, building and room records, with the D-Tools ID kept as a reference field so nothing is matched by name alone. |
| Project items and device data | Ask for project items with make, model, serial, MAC, IP, firmware, room and rack wherever they were captured. | Devices on each room and rack, each with a QR code. Missing serials and MACs are flagged for the next site visit, not guessed. |
| Product catalog and labor types | SI exports product data as CSV (D-Tools' QuickBooks FAQ describes this). On Cloud, ask support for the catalog as a CSV. | Your price list with your dealer costs, plus labor types for shop, site, programming and commissioning hours. |
| Open proposals and change orders | Save each open proposal and change order as a PDF, and ask for line items as a CSV. | Open quotes rebuilt per room so the client can approve good, better or best options from a link. |
| Open projects, tasks and punch lists | Export or save the schedule, open tasks and punch items for each live project. | Live projects at the right stage, punch items as records with a photo, an owner trade and a due date. |
| Service plans and service orders | Ask for each plan: client, rooms covered, tier, start, end, price, billing frequency and open service orders. | Service agreements with response targets and preventive visits, starting on their existing dates. |
| Drawings, as-builts and closeout packs | Save the Visio or AutoCAD files and PDFs from your file store, project by project. | Attached to each room as as-builts and submittals. Drawings are still edited in your design tool. |
| Staff and subcontractors | A plain list: name, role, trade, certifications, phone, email. | Unlimited users with roles; subcontractors get a portal login or a job link. |
source: D-Tools: Frequently asked QuickBooks questions for System Integratorsource: D-Tools: System Integrator features (Visio, AutoCAD, project management, Mobile Install)source: D-Tools: System Integrator pricing (per user per year, 5-user minimum, professional services)
What doesn't come with it
What doesn't export, and what we rebuild
An export carries records, not the way your account is set up. Here is what to expect, and who does the work.
The drawing-to-BOM link
SI syncs Visio and AutoCAD drawings with the bill of materials, and a draw-first mode builds the BOM from the layout. That link is D-Tools' own and doesn't travel. If you keep SI for design, approved drawings become submittals on the room in Fieldproxy, and the build can't be scheduled until the rack elevation is approved.
source: D-Tools: System Integrator features (Visio, AutoCAD, project management, Mobile Install)
Workflow rules, reports and proposal templates
Workflow rules, custom reports and proposal layouts are settings, not records. Screenshot them and send us a few finished proposals and reports. We rebuild the stages, report templates and approvals around how you work, keeping your names where they make sense.
The catalog's managed pricing
D-Tools says its library covers products from more than 1,800 brands. You keep the items and costs you actually sell, but a vendor-maintained library and its price updates don't come with you. Tell us which suppliers you buy from most and we agree how the price list is kept current.
Accounting history
Invoices and payments already posted live in QuickBooks, Xero, NetSuite or Sage 100, not in D-Tools. They stay where they are. Only what Fieldproxy invoices from the switch date onward flows through the new link.
Do these before you cancel D-Tools
- Read your D-Tools agreement for the term, renewal date and notice period, and get anything unclear in writing.
- Ask support for every export in the table above, and keep the files somewhere you control.
- Save as-builts, closeout packs, device schedules and control code files for every project still under warranty.
- Screenshot workflow rules, report layouts, proposal templates and your labor types.
- List every live service plan with its end date, so no renewal or preventive visit is missed during the move.
- Turn off D-Tools' accounting link for anything Fieldproxy now invoices, so nothing reaches the books twice.
- If you keep D-Tools for design only, check which seats you still need at renewal.
Send us your D-Tools export and see it running in your setup.
Get DemoLive within a day
The move from D-Tools, day by day
Migration to Fieldproxy is free and assisted: our team builds your setup and moves your data. You're live within a day, meaning your first team runs real jobs in Fieldproxy the day after the call. How fast everyone else follows is your call.
Live within a day means your first team runs real jobs the day after the setup call, not that every project moves at once. A very large catalog, many integrations or messy device data add time, and we say so on the first call.
What happens on go-live day- 1
Before the call: decide the split and request the exports
You, about an hour
Decide whether D-Tools keeps design and proposals or goes completely. Find your renewal date. Ask D-Tools for the exports, and pick a first team to move: one install crew, or the service desk. - 2
The setup call: one room, from proposal to service plan
You and Fieldproxy
Walk us through one project: the room types, how the rack is built and labeled, what you verify, who signs off, what the closeout pack holds and when the warranty starts. Send a finished closeout pack and a service plan contract. - 3
We build your setup
Fieldproxy's team
Client, building and room records; room type templates with their equipment and verification lists; submittal and change order approvals; receiving screens that capture serial and MAC; install, verification and closeout forms; and service plans with response clocks. The same setup runs on the web and on the Android and iOS app. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Clients, sites, rooms, devices, catalog, open proposals, live projects and service plans, mapped and checked for duplicates, with the D-Tools IDs kept. As-builts are attached to the rooms they describe. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, or Xero, or the Sage link, checked against real invoices. Service plan billing is tested before anything posts. - 6
Live: the first team on Fieldproxy
The day after the call
One crew runs a new install, or the service desk takes today's tickets, in Fieldproxy: required photos of mounts, safety cables and labels, QR codes on racks, signatures at handover. Everyone else stays on D-Tools for now. - 7
Weeks or months: projects close, plans renew, then switch off
Your schedule
New projects start in Fieldproxy; projects already running finish in D-Tools. Service plans move on their renewal dates. When the last D-Tools project has closed out, take the final exports and let the term end.
Cutover
Running D-Tools and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace D-Tools, not to sit on top of it, so the rules below are about ending the overlap cleanly. Our view from moves we have run, not a sourced fact.
Split by project, not by task
A project lives in one system from start to closeout. New projects start in Fieldproxy; projects already in D-Tools finish there, unless they are early enough to move cleanly. Nobody keys the same rack twice.
One system invoices each job, one owns each service plan
Both systems can post to QuickBooks or Xero. Agree which projects and plans each one bills, and a numbering rule, and switch off D-Tools' link for anything Fieldproxy bills. A service plan moves on its renewal date, so no client is billed or visited twice.
A fixed switch-off date
Keep D-Tools readable, not in use, until your renewal date or the last closeout, whichever comes first. The Watcher agent flags overdue punch items, missed preventive visits and service tickets close to their response target while the team is new to Fieldproxy.
The fear
What if a closeout pack is due in the middle of the move?
A project near closeout is the worst one to move: the final payment depends on a device schedule, a verification report and signed training records, and the client's consultant reads every line. This is how we keep that safe.
- 1
Projects near closeout finish where they started
If a project is past rough-in, it closes out in D-Tools. Only new projects and service plans move, so no pack is rebuilt in a hurry. - 2
See your own rooms before you commit
We build your room types and load your exports before you sign, so you judge your own device schedule and verification list, not a demo company's. - 3
Your closeout format, your template
Send a closeout pack a client accepted. The device schedule and verification report come out of Fieldproxy in that layout, so the consultant sees nothing new. - 4
Nothing goes out without a person
AI agents stay off until you switch them on, and any change they propose can wait for a person to confirm. Your data stays yours: export it any time, or read it through the API or the MCP server.
Where things live
D-Tools terms and where they go in Fieldproxy
So installers and the service desk know where things went on the first morning. If you keep D-Tools for design, the first rows stay in D-Tools and arrive in Fieldproxy as approved files.
| In D-Tools | In Fieldproxy |
|---|---|
| Visio and AutoCAD drawings (SI) | Stay in your design tool; approved drawings are submittals on the room |
| Product library and catalog | Price list with your costs and labor types |
| Proposals and options | Quotes per room with good, better or best options the client approves from a link |
| Change orders | Change orders that need client approval before the work is scheduled |
| Projects, Gantt and tasks (SI) | Projects with your own stages, rooms and scheduled crews |
| Punch lists | Punch items with a photo, owner trade, due date and closed date |
| Item tracking | Devices with serial, MAC, IP and firmware, captured at receiving and bench test |
| Mobile Install app (SI) | Technician app with forms, required photos, signatures, QR per rack, GPS check-in, 27 languages; no per-seat limit |
| Service plans and service orders | Service agreements with response clocks, preventive visits and covered or billable tickets |
| QuickBooks, Xero, NetSuite, Sage 100 links | Two-way QuickBooks Online, Desktop and Enterprise, and Xero; Sage; others agreed on the setup call |
| Portal.io proposals | Quotes and customer links; Portal.io can stay for proposals if you prefer |
Straight answers
Switching from D-Tools: FAQ
How long does it take to switch from D-Tools to Fieldproxy?
Is D-Tools being shut down after the Portal.io merger?
Can I keep D-Tools for design and use Fieldproxy for everything else?
What does migration from D-Tools cost?
Does Fieldproxy work with QuickBooks, Xero and Sage?
Does the technician app work offline in a building with no signal?
Can AI agents handle service calls after an install?
Can I use ChatGPT or Claude with Fieldproxy?
Can Fieldproxy produce the device schedule an owner spec asks for?
Sources
Where the facts on this page come from
Every D-Tools fact links to D-Tools's own pages, opened on 19 November 2026. Features and terms change, so check the current page before you decide. More detail, with every source, is in How Fieldproxy is set up for AV integrators.
- source: D-Tools: homepage (since 1998, products and brands)
- source: D-Tools: System Integrator pricing (per user per year, 5-user minimum, professional services)
- source: D-Tools: Cloud pricing (plans, field users, accounting add-on, setup)
- source: D-Tools: System Integrator features (Visio, AutoCAD, project management, Mobile Install)
- source: D-Tools: QuickBooks integration
- source: D-Tools: Frequently asked QuickBooks questions for System Integrator
- source: D-Tools: Portal.io merger announcement (25 August 2026)
- source: D-Tools: Portal.io merger FAQ
- source: Strata-GEE: Private equity owned D-Tools acquires Portal
- source: Portal.io: Pricing
- source: Crestron: XiO Cloud
- source: Q-SYS: Reflect overview
- source: US DoD: UFGS 27 41 00 Audio-Visual Systems
- source: Cornell University: Section 27 41 16 Integrated Audio-Video Systems
Leave D-Tools without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a D-Tools export. We show you your own setup and data running in Fieldproxy before you commit.
Plan my switchFree, assisted migration. One price per company, unlimited users. Changes are a conversation.