this is the follow up to leaving verizon connect work? how to move your clients and job history into your next tool. that one covers the export basics. this one starts after the zips land: what's in them, and how much jobber or housecall pro can actually take.
the dates to plan around
from verizon's final transition deadlines & data export cutoffs article (updated 22 oct 2026):
- 31 dec 2026: end of active service.
- 4 jan 2027: platform ui restriction. admin logins go straight to the data migration tool and the mobile app stops.
- 28 feb 2027: last day to start a new export. verizon says large exports "can take over a week to process".
- 31 mar 2027: last day to download finished zip files. after that verizon says job logs, signatures and media attachments are "irretrievably purged".
verizon's final billing cycles page says that after 31 dec 2026 "the user interface will be locked". so plan for 31 dec, and treat the later dates as a safety net for exports only.
what's in the attachment zips
honest caveat: i don't have a real work export, and verizon doesn't publish a sample, so no file names here. this is what verizon's migration tool guide (updated 21 oct 2026) says:
- date range exports come as zip files grouped by month.
- "jobs with attachments" gives you job and task data plus attached files like photos and documents. "attachments will be in individual folders numbered for each associated job."
- you also need the plain jobs export in csv. verizon calls it "your master key": "column a in your csv contains the unique 'job id,' which corresponds exactly to the numbered folders in your downloaded zip file."
- the faq on the same page says attachment file names "correlate directly" with those job ids.
so the workflow is: unzip a month, open that month's jobs csv, and use column a to go from a numbered folder to a client, address and date. if your files look different, trust your files.
same goes for column names. verizon's guide only names column a, so any work column names you see below or in a mapping are a starting point, not gospel. take the real ones from your own export. the map in the guide marks them "check your export" for exactly that reason.
opening them without making a mess
- unzip each month into its own folder named for the month, like
2024-03. keep the original zips untouched somewhere else. - don't double click the csv. use your spreadsheet's import option and set id, phone and zip columns to text, so job ids and leading zeros survive.
- spot check: pick a job you remember, read its column a, open that folder. if the photos match, the month is good.
if you want to keep a readable copy of the old jobs before you import, there's a free viewer that opens the zip, csv and json files from a work export as a browsable archive. the files stay in your browser, nothing gets uploaded.
what jobber can import
i read these on 23 oct 2026.
clients (import clients, updated 6 aug 2026): csv, tsv or psv. admin only, and it won't run in an incognito or private window. each file must be under 2.5mb, (about 5000 rows), so split bigger lists. it takes names, company, phones, email, addresses, notes and tags. if the street column is empty, no property gets created. only text client custom fields import, not dropdowns, and only jobber's built in lead sources.
jobs (import jobs, updated 10 sep 2026): this is a beta feature, admin only. up to 1000 jobs per import. past jobs come in as complete and archived, but only if the start date is within ten years. columns include job title, instructions, client name, notes, property address, start date and times, assigned to and total price. client name and the full property address, including country, are mandatory, and jobber warns not every export includes one. no job level custom fields. jobs attach to existing clients only on an exact name or address match, otherwise you get a new client, so import clients first and keep names identical. you get 10 minutes to revert an import.
attachments: neither import doc mentions photos or files. jobber's notes and attachments page allows 500 mb per file on notes, but that's manual upload, not an import.
what housecall pro can import
from prepare to import your data (updated 23 jan 2026):
customers: customer id, names, company, addresses, phones, emails, notes, tags and lead source. zip codes "must be a real usa zip code", phone numbers must be 10 or 11 digits, and "custom fields cannot be created". anything without a matching field goes into notes or tags first.
jobs: the jobs import takes the customer fields plus job id, invoice number, notes, subtotal, tax, payment details, scheduled, start and completion dates and job type. each row has to be one job. if your export spreads a job over several rows (say, one per line item), you have to merge them or only the first row goes in.
on the max plan, housecall pro's data import team can bring over customers, job history, equipment and price book for you.
attachments: again, no photo or file field in the import. their attachments page covers uploading files to jobs by hand, and the mobile photo page caps pdfs uploaded from a phone at 5mb. i couldn't find a documented size limit for web uploads or for the import file itself.
so what actually moves
- clients: yes, both, after some column cleanup.
- job records: yes, both, as csv. jobber's is beta and capped at 1000 per file.
- photos, signatures, pdfs: no bulk import in either tool's docs. keep them in your archive, or re upload the few you need onto the right jobs by hand.
import clients, then a small test batch of jobs, check them, then do the rest. and keep the work zips forever.
written with ai assistance and checked against verizon's, jobber's and housecall pro's published help docs on 23 oct 2026.
Top comments (0)