Skip to content

Switching software

How to migrate from BuildOps to TradesWork: who should, and how

Most commercial contractors shouldn't leave BuildOps for TradesWork. For residential-first shops that should: exports, the 30-day rule, import and costs.

Updated October 15, 2026 · 9 min read

The steps at a glance

  1. 1

    Check the fit first

    If you rely on project management, fire and life safety inspections, or Vista, Spectrum, Sage Intacct or NetSuite, stay on a commercial platform. TradesWork fits residential-first shops on QuickBooks Online.

  2. 2

    Request exports from BuildOps in writing

    Ask which records you can export, from where and in what format; collect customers, properties, assets, agreements, jobs, invoices and documents before the term ends.

  3. 3

    Import customers and the price list into a sandbox

    In TradesWork open the import page, choose Another system or a spreadsheet, drop customers with site addresses and your price list, match the columns, check the preview and import into a sandbox company first.

  4. 4

    Rebuild agreements and commercial terms

    Set up multi-site service agreements with PM visit plans and SLA hours, and turn on PO required, not-to-exceed limits and net terms for commercial customers.

  5. 5

    Run one crew side by side

    Put one residential crew on TradesWork for two to four weeks, then move commercial accounts once agreements and terms are set.

  6. 6

    Cut over accounting

    Pick a cut-over date. Invoices before it stay where they are; invoices after it come from TradesWork into QuickBooks Online.

  7. 7

    Re-collect payment methods and port numbers

    Send customers a secure link to save a card, set up commercial payers again, and port business numbers early.

  8. 8

    Final export and written notice

    Pull final exports in the last week, and if you need BuildOps to produce data afterwards, send written notice within 30 days of termination.

Start with the honest filter. BuildOps is a commercial platform with project management, fire and life safety inspections and construction accounting integrations.12 TradesWork has none of those. If they're part of how you work, moving to TradesWork would be a step backwards, and you should compare commercial platforms instead.

This guide is for the other case: a residential-first HVAC, plumbing or electrical shop that bought BuildOps for a commercial push, uses a fraction of it, and wants homeowner tools, published pricing and free office seats. For that shop, here's the plan, with the import shown on real TradesWork screens. BuildOps facts come from its own site and terms, checked October 15, 2026.

Is TradesWork the right destination?

 If you use this in BuildOps, TradesWork today is…
Submittals, RFIs, change orders, job costingNot built. Stay on a commercial platform.
NFPA inspections and deficiency trackingNot built. Stay on a commercial platform.
Vista, Spectrum, Sage Intacct or NetSuiteNot supported. QuickBooks Online only.
Maintenance agreements across multiple sitesMulti-site service agreements with PM visits and SLA hours
POs, not-to-exceed, net termsBuilt, enforced on the invoice
Residential customers and membershipsBuilt: memberships, member pricing, good/better/best

Source: BuildOps home and pricing pages; TradesWork multi-location and commercial feature

If the first three rows describe your week, close this page and look at commercial options. Our TradesWork vs BuildOps and TradesWork vs ServiceTrade pages say so directly.

The whole move on one page

  1. Week -4

    Fit check and export request

    Confirm TradesWork fits. Read your Order for the term end. Send BuildOps the written export request.

  2. Week -2

    Files in hand

    Exports opened and checked. Inspection, project and agreement records archived. Phone ports requested.

  3. Week -1

    Sandbox import

    Customers and price list into a sandbox company. Every commercial site checked. Leftover rows fixed.

  4. Weeks 1–2

    Rebuild and residential pilot

    Import into your real company. Commercial terms, service agreements and memberships set up. One residential crew live.

  5. Weeks 3–4

    Office and payments

    Office on TradesWork. Payment re-collection starts. Accounting cut-over date set.

  6. Weeks 5–8

    Commercial accounts move

    Agreements tested on real visits, then commercial accounts move.

  7. Within 30 days after term end

    Written notice, if needed

    Only if you still need BuildOps to produce data under §5(d).

What moves, what stays, what you rebuild

From BuildOpsIn TradesWork
  • Customers and properties (requested)PartlyCustomers and service locationsEach row's address becomes a service location. How a customer with many properties groups depends on your file; check every site in the sandbox.
  • Price book or rate sheet (requested)ImportsPrice bookName and price required. Code, description, category and cost carry over if present.
  • Assets by propertyKeep as archiveEquipment you re-enterAgreement sites first.
  • Maintenance agreementsKeep as archiveService agreements you set upSites, covered equipment, PM plan, SLA hours, billing cadence.
  • Jobs, quotes, invoicesKeep as archiveYour archiveThe spreadsheet importer takes customers and price lists only.
  • Projects and inspection recordsKeep as archiveYour archiveCan't be imported or produced in TradesWork.
  • Saved payment methodsKeep as archiveRe-collectedPayment data stays with the processor.
Import facts from the TradesWork spreadsheet importer. BuildOps exports depend on BuildOps' answer to your request.

BuildOps doesn't publish export instructions, so ask your BuildOps contact in writing which records you can export, from where, and in what format. Our BuildOps export guide has the full request list and a request you can copy. Then mind the clock: BuildOps' terms say it will make Customer Data available for export if it receives written notice within 30 days after expiration or termination, and that after those 30 days it has no obligation to keep the data (§5(d)).3 Your subscription term is in your Order (§10(a)).3 Get everything before the term ends.

Bring it into TradesWork

Start a 14-day TradesWork trial with no card. Open Settings, Integrations and go to the import page; you need the Owner or Admin role.

1. Choose Another system or a spreadsheet

The source buttons sit across the top of the import page; press Another system or a spreadsheet. Drop CSV, Excel or a ZIP, up to 50 MB per drop. TradesWork never logs in to BuildOps.

app.tradeswork.app · TradesWork importer with another system or a spreadsheet selected
TradesWork importer with another system or a spreadsheet selected
Real TradesWork screen, sample export files.

For commercial customers with many sites, check that each site came through with the right address, and add any that didn't by hand before you build agreements on them. Keep the BuildOps customer and site IDs as a column in your spreadsheet. When someone asks about a job from two years ago, that ID is how you find it in your archive.

What you set up by hand

  • Commercial terms. On each commercial customer, turn on PO required, set a not-to-exceed limit and net terms, and add billing and site contacts. Blocking invoices without a PO is a setting that's off by default; turn it on if your customers require POs.
  • Service agreements. Pick the sites and covered equipment, the PM visit plan, SLA response hours and billing cadence. Visits become jobs ahead of time and billing consolidates to one invoice per customer per month. SLA tracking is a countdown on the job; it won't escalate on its own.
  • Residential memberships. For homeowners, set up membership plans with member pricing.
  • Assets. Add equipment for agreement sites first.

The side-by-side run, and re-importing newer exports

Move residential work first, where TradesWork is strongest. Put one crew on it for two to four weeks while BuildOps runs everything else. Move commercial accounts once their agreements and terms are set and tested on a few real visits.

If the office adds customers or sites in BuildOps during the run, export again and drop the file. Customers are matched by the Customer ID column you mapped, or by name and address, so a re-drop updates rather than duplicates, and it never deletes anything.

Accounting, payments and phones

Accounting. TradesWork syncs with QuickBooks Online. BuildOps lists Vista, Spectrum, Sage Intacct, NetSuite and QuickBooks.2

  • Already on QuickBooks Online: pick a cut-over date. Invoices before it stay as they are and are collected where they were billed. Invoices after it come from TradesWork; imported customers never post. Turn off BuildOps' sync on that date and watch for duplicate customers.
  • On another accounting system: moving to QuickBooks Online is its own project. Talk to your controller first; for many commercial shops this alone rules TradesWork out.

Payments. BuildOps lists a Payments+ add-on.2 Card and bank details stay with the processor. Send homeowners a secure link to save a card in TradesWork, and ask commercial customers who pay electronically to set up payment again.

Phones. Port business numbers from Settings, Phones, Numbers, Routing and Texting, Bring your numbers. Ports take one to two weeks; keep old service active until each port shows done.

What switching costs

CostExampleYour number
TradesWork subscription10 × $99 = $990 a month; office staff free
BuildOps overlapPer your Order; BuildOps doesn't publish pricing
Office rebuild time30–60 hours (example): commercial terms, agreements, assets
Tech training2–3 hours per tech (example), residential crew first
Accounting moveOnly if not on QuickBooks Online
Lost workflowsProjects, inspections: must not be needed

BuildOps to TradesWork checklist

  • Fit check passed: no projects, inspections or construction accounting needed
  • Term end from your Order in the calendar
  • Written export request answered and files opened
  • Inspection, project and agreement records archived
  • Sandbox import checked, every commercial site confirmed
  • Customers and price list imported into your real company
  • Commercial terms and service agreements set up and tested
  • Residential pilot complete
  • Accounting cut-over date set, BuildOps sync off
  • Payment re-collection and phone ports under way
  • Final exports stored twice

The bottom line

For a commercial-first contractor, BuildOps is the better tool and this migration isn't worth it. For a residential-first shop carrying more platform than it uses, TradesWork can be a simpler, published-price fit, as long as you're on QuickBooks Online and your commercial accounts need terms and agreements, not inspections and projects. Use the buyer's guide to check.

Footnotes

  1. BuildOps, home page. https://buildops.com/ ↩

  2. BuildOps, Pricing. https://buildops.com/pricing/ ↩ ↩2 ↩3

  3. BuildOps, Terms of Service, last updated May 28, 2026, §5(d), §10(a). https://buildops.com/terms-of-service ↩ ↩2

Free download

Field Service Software Scorecard

Weight what matters to your shop, score up to five systems, and see year-one cost side by side.

Get it free
  • 30 criteria across booking, dispatch, field app, selling, money and reporting
  • Your own weights, totals calculated for you
  • Year-one cost worksheet: licenses, add-ons, setup, payments
  • Demo question list to ask every vendor

Frequently asked questions

Usually not. TradesWork has no project management, no fire and life safety inspection or deficiency workflows, and works with QuickBooks Online only. It fits residential-first shops with some commercial accounts.

Sources

Last reviewed October 15, 2026. Third-party sources are marked; some are written by competing vendors.

  1. 1.BuildOps Terms of Service (last updated May 28, 2026)
  2. 2.BuildOps pricing
  3. 3.BuildOps home page

Ready to run a tighter shop?

Try the TradesWork AI plan free for 14 days. Bring your customers and price book, or start fresh with a price book made for your trade.

  • No credit card
  • No contract
  • Cancel any time
Three workers in coveralls unloading equipment from a van