if you run a field service business on verizon connect work (it used to be called fleetmatics work), it's being retired, and the part that actually matters is getting your clients and job history out and into whatever you use next.
the dates, straight from verizon's comprehensive faq: "We recommend completing all exports by December 31, 2026." on january 1, 2027 it goes read-only and mobile sync stops. and "After the final shutdown on March 31, 2027, the platform will be inaccessible and all data will be purged." international customers have their own faq page, so check that one if you're outside north america.
also worth knowing early: verizon won't hand your data to your next provider. their words: "To protect your privacy, we cannot move data directly to a third party." you download it, then you bring it to the new tool.
one honest caveat: i haven't seen a real export file, and there's no public sample export, so everything below about files and formats is what verizon's docs say. check it against what you actually get.
1. who can export, and where
only full account administrators can use the export. in the top nav of work there's a migration tool button, which opens in a new tab or window (verizon's guide). if you click it and nothing happens, your browser is probably blocking it as a pop-up. allow pop-ups for work2.fleetmatics.com and try again. if it loops back to the dashboard, verizon suggests firefox or a private window.
there's also the older route from before the shutdown: settings > import/export data > export data. it exports clients, suppliers, items and jobs as excel or csv, and jobs can be filtered by job start date, creation date or invoice date (2022 article, so the menu may differ now).
2. what to export
the migration tool splits things in two.
general exports (no dates): clients, and start/finish questions.
date-range exports: accounts (your inventory and purchases accounts), invoices, jobs (data only), jobs with attachments, purchase orders, quotes, suppliers. each range can be at most 2 years apart, and verizon says not to overlap ranges.
each category comes as csv or json. verizon says if you're unsure, pick csv, since excel or google sheets can open it.
two extras people skip: every category has a view schema button, and there's a show er diagram button with a download option. save both. if your next provider isn't one of verizon's partners, verizon says those providers "do not have access to our export data schemas", so the schema and diagram are the closest thing to a map of your data you can give them.
3. running it without losing your place
- text exports are quick. anything with photos, signatures and pdfs can take "several days to over a week".
- don't cancel or re-request a slow one. that resets your spot in the queue. closing the browser doesn't stop it.
- run jobs with attachments in small chunks. verizon's own tip is monthly or quarterly.
- results land on the job history page, grouped into zip files by month. each download is only available for three weeks after it finishes, so watch the "available until" column and grab every month.
- work deletes job records that haven't been modified in 7 years, so anything before about september 2019 is already gone (retention policy). a range from before then, or one with no completed jobs, gives you a 0-record file.
- if a file comes back blank but you can see the jobs in the jobs tab, verizon suggests smaller chunks (6 months or a year). for export trouble, their faq lists work.support@srv.verizonconnect.com.
4. check the files the same day
- unzip every month and make sure each one actually has something in it.
- open the clients csv and a couple of job files. do names, addresses and phone numbers look right? pick a busy month and roughly compare the row count to what the jobs tab shows.
- check attachments. verizon says they come in folders numbered for each job, and file names match the job id in the job csv. pick three jobs you remember, find their files and open a photo.
- keep two copies in two places, like a laptop and an external drive.
5. a browsable offline copy, by hand
after you move you'll still want to look things up ("what did we do at this address in 2022"). a plain spreadsheet does most of it:
- never edit the original files. copy them into a "working" folder and edit the copies.
- import the csv through the spreadsheet's import option instead of double-clicking it, and set postcode, zip and phone columns to text, otherwise leading zeros can disappear.
- one workbook, one sheet each for clients, jobs and invoices. paste each month's jobs under the last, and keep only one header row.
- freeze the header row and turn on filters to find jobs by client or address.
- verizon says jobs link back to the client name, so a lookup (xlookup or vlookup) can pull client details into the jobs sheet.
- add a column with each job's attachment folder path. in desktop excel a hyperlink to a relative folder path can open the folder, as long as the workbook sits next to the unzipped folders. test it on one row first.
- save the workbook as .xlsx, but keep the original csvs and zips too. those are your real backup.
6. what people commonly miss
- attachments. plain "jobs" is data only. photos, pdfs and signatures only come with jobs with attachments, and that's the slow one, so start it first.
- notes. verizon's docs don't spell out which note fields end up in the job export. open a job you know has notes and check the export for them. if they're missing, copy the important ones while you can still log in.
- invoices, quotes, purchase orders, suppliers. each is its own export. your accountant will probably want the invoices.
- inventory items and price books. verizon's master data page lists them as csv exports, but the migration tool's list doesn't name inventory items, so check settings > import/export data for them.
- start/finish questions. small, but export them.
- client custom fields. work supports them. check they show up in the clients export.
- recurring jobs. i couldn't find anything saying recurrence patterns export. write down your recurring schedules.
- gps. if you use reveal, that's a separate platform and keeps running, but verizon says the work/reveal integration stops once you move off work.
7. planning the move into your next tool
- before you commit, ask the new tool what it can import (clients, job history, attachments) and in what format.
- give their onboarding people a small sample of your files plus the schema and er diagram from step 2.
- verizon's faq says you can take your exports "to any field service provider of your choice", but mapping the files is then that provider's job.
- move clients first, since jobs hang off clients. then upcoming and recurring work. job history can go in too, or stay in your offline copy if the new tool can't take it.
- verizon's migration checklist says to train your team on the new tool well before december 31, 2026. run both for a bit if you can.
- keep the original zips untouched after the move.
that's it
none of this is hard, just slow and easy to put off. queue the attachment exports this week, download each month inside its three-week window, check a few files, and your history goes wherever you do.
Written with AI assistance and checked against Verizon's published docs.
Top comments (1)
tr.ee/dev-to