Home services and trades
Successware data export and archiving
By SourceX Editorial · Updated
Short answer
Successware data export and archiving means saving customers, locations, equipment, jobs, estimates, invoices, agreements and notes in open formats before a migration or contract end cuts access. The rule: confirm export routes with the vendor early, export every record family with its IDs, reconcile counts against Successware reports and keep a read-only archive you can still search.
Key takeaways
- Migrations usually move active customers and open work; closed jobs, past estimates and call history need their own export.
- Report exports flatten linked records, so pair them with a full extract or database copy that keeps the IDs.
- An export is complete only when counts, totals and sample links match control reports run in the live system.
- A database backup needs the right software to open; open formats keep the archive readable without Successware.
- A short data dictionary written before shutdown preserves what each code and status meant at your company.
What should a Successware export include?#
A Successware export should include every record family your team uses, with the IDs that join them, not just the customer list a new platform asks for. Migration projects tend to move active customers, equipment, open work and agreements, and leave years of history behind.
Think of the export in two layers. The migration layer is what the new platform imports to keep the business running. The archive layer is everything else your company may need to answer a warranty question, support an audit, settle a dispute or assess the records later.
| Record family | Typical contents | Why keep it |
|---|---|---|
| Customers and locations | Names, contacts, billing and service locations | The keys every other record points to |
| Equipment | Type, brand, model, serial and install date by location | Replacement planning and service history |
| Calls and jobs | Job type, dates, technician, status and notes | The core operational history |
| Estimates and proposals | Options presented, accepted or declined | Sales history a new system may not import |
| Invoices and payments | Line items, totals and payment status | Financial records and reconciliation |
| Agreements | Plan types, renewal dates, visit schedules | Membership history and renewal patterns |
| Lead sources and marketing | Campaign, source and call outcome | Booking and marketing analysis |
| Users and technicians | Roles and active dates | Interpreting who did what, years later |
How do you get data out of Successware?#
Getting data out of Successware usually takes a mix of built-in report exports and a fuller extract, and the options depend on your version and hosting arrangement. Report exports to spreadsheet formats work well for lists and summaries, but they can flatten linked records and trim long notes.
A full extract, where the vendor or your IT provider delivers the underlying tables or a database copy, preserves keys and history better. Ask Successware support early and in writing what extract options exist for your account, what format they arrive in, whether a fee applies and how long you keep access after your contract ends.
If the system runs on a server your company manages, your IT provider may also be able to take a full database backup. A backup is a safety net, not an archive: it needs compatible software to open, so pair it with exports in open formats that anyone can read.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Successware export and archive checklist#
The checklist below covers the export from planning through retirement of the old system. Assign one owner for the whole list; exports that belong to everyone tend to be finished by no one.
- Name an export owner and set a finish date well before access ends.
- List every record family, custom field, report and attachment type your team uses.
- Ask the vendor in writing which extracts are available, in what format and until when.
- Export each record family with its internal IDs so jobs, invoices and equipment can be rejoined.
- Export notes and long text fields in full, and spot-check that none are cut off.
- Save photos, attachments and signed documents with an index mapping each file to its job.
- Reconcile counts and totals against control reports run inside Successware before shutdown.
- Store the archive read-only, with access logging, in at least two locations your company controls.
- Write a data dictionary covering tables, fields, codes and what each status meant at your company.
- Record retention decisions and the date the old system was retired.
How do you check that an export is complete?#
An export is complete when its counts, totals and links match what Successware showed before shutdown. Run control reports in the live system, such as jobs by year, invoice totals by year and active agreements, and save them as PDFs beside the archive so the comparison can be repeated later.
Do the checks while the old system is still available. A gap found after access ends is usually permanent, and a vendor may not be able to restore it.
| Check | How to run it | What a failure looks like |
|---|---|---|
| Counts by year | Compare job, invoice and estimate counts per year with system reports | Missing early years or a sudden drop in one year |
| Financial totals | Compare invoice totals per year with the accounting system | Totals that do not tie to the books |
| Link integrity | Trace sample jobs to customer, location, equipment and invoice | Orphan jobs with no customer or invoice |
| Text fields | Compare the longest notes with what the screen shows | Notes cut off mid-sentence |
| Attachments | Open sample files from the index | Broken paths or missing photos |
| Codes | Map job types and statuses to their meanings | Codes nobody can explain |
Where should the archive live, and who can open it?#
The archive should live in storage your company controls, set to read-only, with access limited to the few people who need it. A shared folder that anyone can edit is a copy, not an archive.
Open formats, such as CSV for tables and PDF for documents and control reports, keep the archive readable without Successware. If you also keep a database backup, record the software and version needed to open it.
Retention is a separate decision. Tax, employment and contract rules set how long some records must be kept, and privacy commitments may limit how long others should be. Agree the schedule with your accountant and counsel instead of keeping everything indefinitely by default.
Illustrative: an HVAC, plumbing and electrical company retires Successware#
Illustrative: a fictional HVAC, plumbing and electrical company is moving from Successware to a newer field service platform. The new vendor's migration plan imports active customers, equipment and open agreements, but not closed jobs, past estimates or call history.
The COO names the service operations manager as export owner and asks Successware support which full extracts are available before the contract ends. The team exports each record family with IDs, reconciles job and invoice counts by year against reports run in the live system, and saves those reports as PDFs.
The decision: keep the full history as a read-only archive with a data dictionary, separate from the new platform. The outcome is that the office can still answer warranty and customer questions about old jobs, and the owner later uses the archive's metadata for a fit check without reopening the retired system.
What else can an archived job history become?#
An archived job history can become a licensable dataset once it is complete, linked and documented, which is one more reason to export more than a migration strictly requires. Years of calls, estimates, jobs, equipment and callbacks describe how a trades business actually works.
SourceX starts with metadata only: the systems, record families and years in the archive. Under the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery), rights review and privacy preparation happen before anything is shared, the supplier approves each step, and large archives stay in the company's own storage. The data is licensed, not sold.
Frequently asked questions
Should we export before or after signing with a new vendor?
Start planning before you sign. The new vendor's migration scope tells you what will move, and everything outside that scope needs its own export. Confirming export options and access dates with Successware early leaves time to fix problems while the old system still runs.
Can the new platform import our full Successware history?
Some history may import, but migrations often focus on active customers, equipment, open work and agreements. Ask the new vendor exactly which record families and years they will bring across, test with a sample, and plan a separate archive for the rest.
Do we need to keep paying for Successware after migrating?
Not if the archive is complete and readable without it. Some companies keep limited access for a transition period, where the contract allows it, to answer questions while staff learn the new system. Confirm what access your contract provides after it ends.
Is a spreadsheet export of each report enough?
For lists, often yes. For linked history, report spreadsheets rarely carry every key and full note. Combine report exports with a full extract or backup, and test that jobs can be rejoined to customers, equipment and invoices before access ends.
What about stored payment details in the old system?
Card and bank details should not travel in general exports. Leave stored payment details out of the archive, or handle them only under your payment processor's rules, and keep invoice and payment status without account numbers.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.