Switch from Workiz
Switching from Workiz to JobStack: a step-by-step guide.
You've decided to move off Workiz. This guide walks through what to export, how to clean it up, how to import into JobStack, and how to run both in parallel so you don't get stranded.
Why operators leave Workiz
- Phone isn't actually your main channel. You signed up for the call features but found most of your business comes through text and web. The phone infrastructure cost stopped pencilling.
- AI for text/email lagged. Workiz invested in call AI; for operators whose inbound is text-heavy, that's not the AI you needed.
- Pricing felt heavy for a small operation. $165+/mo entry is steep for a solo or two-person business with modest call volume.
- Wanted simpler, faster, less. Workiz has depth you appreciated but didn't always use. JobStack does the 80% case with less ceremony.
What carries over, what changes
Carries over
- Customer list
- Job and visit history
- Open and historical invoices
- Payment records
- Notes attached to customer records
Needs setup or rethinking
- Call recordings and transcripts (download what you need to keep)
- Tracking phone numbers (port or reassign)
- Marketing attribution by channel
- Lead routing logic
- Genius AI call summaries
- Call-based reporting and KPIs
The migration, step by step
- 1
Export your data
In Workiz, go to Settings → Export. Pull CSVs for Customers, Jobs, Invoices, and Payments. Download recordings you legally need to retain — they don't migrate.
- 2
Plan your phone replacement
Decide where your tracking numbers go. Port to a VoIP provider (CallRail, OpenPhone), forward to your cell, or consolidate. Do this before cutover; lost calls = lost revenue.
- 3
Audit your customer list
Multi-year Workiz accounts accumulate duplicate records from repeated calls. Clean these up before import.
- 4
Import into JobStack
Upload your cleaned CSVs. The importer maps standard fields automatically.
- 5
Set up replacement marketing attribution
If you were tracking call sources for ROI, set up CallRail (with UTM tracking for web) or Google Analytics tagging. Otherwise you'll lose source attribution at cutover.
- 6
Reconnect payments and other integrations
Stripe, QuickBooks, calendar — standard JobStack integrations, each under 2 minutes.
- 7
Test with real jobs
Run actual end-to-end flows. Pay attention to invoice-and-payment handoff if that touches your accounting workflow.
- 8
Parallel run for a week
Workiz stays accessible for call history lookups; JobStack handles new jobs.
- 9
Cancel Workiz and archive
Final exports, then cancel. Save recordings and exports per retention requirements.
Common gotchas
-
Tracking phone numbers are tied to Workiz. Port them out before canceling or you'll lose them.
-
Call recordings don't migrate. Download anything you need for legal or compliance reasons before access lapses.
-
Marketing attribution by call source won't carry over. Set up CallRail or equivalent if you need this.
-
Dispatching workflows in Workiz are deeper than JobStack's. Simplify, don't try to rebuild one-for-one.
-
Per-channel reporting in Workiz is excellent. JobStack's reporting is simpler — set expectations.
Realistic timeline
- Week 1 Export, plan phone replacement, port numbers, import to JobStack.
- Week 1–2 Set up replacement marketing attribution, reconnect integrations.
- Week 2 Parallel run; Workiz for call history, JobStack for new jobs.
- End of week 2 Cancel Workiz, archive recordings and exports.
Ready to start?
Get migration help, free at launch.
JobStack launches soon. Sign up to get early access plus white-glove migration from Workiz — we'll get on a screen-share and do most of the work with you.
Get notified + migration helpFrequently asked questions
How long does Workiz migration take?
Can I keep my Workiz phone numbers?
Will I lose my call recordings?
What if I still need some call tracking?
Is migration support available?
Guide verified as of May 2026. Workiz feature names and export workflows may change; if a step doesn't match what you see, check Workiz's current help documentation. Workiz is a trademark of its owner.