Run this test before you sign anything: ask the software to export every job, every photo, every invoice, and every customer note into a file you can open without their app. Then actually open it. If what comes out is a CSV with half the fields missing and none of the attachments, you don't own your data—you're renting access to it.
Most contractor tools are built to make the front door wide and the back door narrow. Onboarding is smooth because they want you in. Export is an afterthought because they'd rather you never leave. That asymmetry is a business decision, not a technical limitation, and it's worth understanding before it costs you a season of job history.
The two lock-in traps
Trap one is the all-in-one suite. It's genuinely convenient—scheduling, invoicing, CRM, and job tracking under one login. The tradeoff is that when one piece stops fitting, you can't swap just that piece. Your customer list is entangled with your invoicing which is entangled with your scheduling, and pulling one thread unravels the whole thing. The convenience you paid for becomes the reason you can't leave.
Trap two is the opposite: a best-of-breed stack where every tool does one thing well. You keep flexibility, but now your data lives in five places with five export formats and no single source of truth. Switch one vendor and you're re-mapping fields by hand. Flexibility isn't free either—it's just a different bill.
We'll be honest: there's no configuration that makes lock-in disappear. Every tool you adopt is a small bet that it'll still serve you in three years. The question isn't whether you're exposed—it's which pieces you can afford to lose access to overnight.
The day you switch tools is the day you find out who actually owned your job history—and by then it's too late to negotiate.— common lesson from contractors mid-migration
Rank your data by what hurts to lose
Not all data carries the same switching cost. Scheduling is annoying to rebuild but survivable—you can reconstruct next month's calendar in an afternoon. A CRM export that comes out clean is recoverable. But the records tied to money and disputes—signed change orders, payment milestones, proof of what was agreed—are the ones you can't afford to have trapped behind someone else's login when a client contests a bill two years later.
This is where we land differently than most stacks. We think the money-and-agreement layer is the one piece that shouldn't live inside a tool you might churn out of. Escrow works precisely because it's a neutral third party—it doesn't care which scheduling app or accounting software you use, and it isn't trying to hold your data hostage to keep you subscribed. Its whole job is to hold the record straight and hand it over when asked.
The stack we'd actually build
Keep the operational layer close and in-house-tailored: scheduling, notes, photos, and CRM in whatever fits how you already run jobs, chosen on the assumption you might replace it. Assume those tools are swappable and don't over-invest in their permanence.
Then make escrow the one deliberate third-party dependency—the neutral holder for payment terms and agreed scope, kept outside any single vendor's export policy on purpose. That's the layer where being locked in actually protects you instead of the vendor.
Before you commit to anything, run the export test on every tool you're considering, and pay closest attention to how the money layer behaves. If you want to see how the escrow piece fits alongside the rest of your stack, the contractor plans lay it out plainly.