Home services and trades
Archiving legacy Wintac data before you retire it
By SourceX Editorial · Updated
Short answer
To archive Wintac data before you retire it, take a full backup of the company data, prove it restores on another machine, then export readable files for customers, sites, equipment, service history, invoices, agreements and receivables with Wintac's own numbers intact. Keep both in two company-controlled locations, along with the installer and license details.
Key takeaways
- A Wintac backup is only proven once it restores and opens on a different machine.
- Readable exports outlive the software; backups still need Wintac, or someone who can read its database, to open them.
- Keep Wintac's customer, site, work order and invoice numbers in every export so the files can be joined again.
- Write down where the archive lives, who may open it and how long it is kept before the old server is switched off.
Why Wintac archives need more care than cloud exports#
Wintac archives need more care because many contractors ran Wintac on an office server or workstation, so the data sits on hardware the company controls rather than in a vendor's cloud. That cuts both ways: no vendor will switch off access when a subscription lapses, but nobody else is keeping a copy either.
The usual risks are physical and practical. An aging server, an unsupported operating system, a lost license key or the retirement of the one person who knew where everything was stored can each make years of service history unreadable. Retirement projects are often triggered by a move to cloud field service software, a server replacement or the sale of the company, and each of those is a deadline.
The four-part archive plan#
The four-part archive plan covers a full backup, readable exports, a retention location and checks that the records are still useful. Each part has a clear test for done, so the project ends with evidence rather than an assumption.
| Part | What to do | Done when |
|---|---|---|
| Full backup | Run Wintac's backup routine and have IT copy the data folders with the program closed on every workstation | A second machine restores the backup and opens the company data |
| Readable exports | Export customers, sites, equipment, service history, invoices, agreements, receivables and the price book with Wintac's numbers | Record counts match what Wintac shows on screen and in reports |
| Retention location | Store two copies in company-controlled locations with named access | The access list and retention period are written down |
| Usefulness checks | Keep ID fields, notes, attachments and a short data dictionary | Someone outside the project can trace one job from call to payment |
Part one: a full backup you have tested#
A full backup you have tested is the foundation, because it preserves everything Wintac stored, including fields no report shows. Work with whoever manages your server, and do not delete or reformat anything until the restore test passes.
- Identify the Wintac version, where the company data is stored and every workstation that connects to it.
- Close Wintac on all workstations before the backup runs.
- Run the backup and copy the data folder, plus any document or image folders linked to records.
- Restore onto a separate machine, open the company data and check recent invoices and service tickets.
- Keep the installer, version notes and license or registration details with the backup.
- Export or photograph setup lists such as job types, technician codes and tax codes that give stored codes their meaning.
Part two: readable exports that outlive the software#
Readable exports matter because a backup still needs Wintac, or someone who can read its database, to open it. Spreadsheet or CSV exports can be opened by anyone, searched by address or equipment, and loaded into a new system or a simple database years from now.
Export each record family separately and keep Wintac's own numbers as columns: customer number, site number, equipment ID, work order or service ticket number, invoice number and agreement number. Those numbers are what let you rebuild a job's history across files. If you ran accounting inside Wintac rather than a linked accounting package, give your accountant receivables, payables and ledger detail as of the cutover date.
Keep printed-style reports, such as invoice copies and aging reports, as PDFs too. They are not searchable at scale, but staff can read them without help, and they match what customers and auditors saw at the time.
Part three: where the archive lives and who can open it#
The archive should live in company-controlled storage with two copies: for example, a file server with its own backups and a second copy in a company-owned cloud account or an offline drive kept in a secure place. A former employee's personal drive or a technician's laptop does not count, however convenient it seems during the project.
Limit access to named roles, such as the controller, the office manager and IT, and log who opens the archive. Set a retention period with your accountant and counsel that reflects tax records, warranties, lien and contract claims and any legal holds, and write down who approves destruction when that period ends.
Illustrative: an electrical contractor retires its Wintac server#
Illustrative: a fictional residential and light commercial electrical contractor is moving to cloud field service software. Its Wintac server sits in a back office, and the office manager who has run it for years plans to retire soon. The new vendor will import customers, sites and equipment, but not closed service history.
IT runs the backup and the restore test, which reveals that a folder of scanned permits and photos linked to records sat on a different drive and was missed. That folder is added. The office manager exports each record family with Wintac's numbers and writes a one-page data dictionary before her last day. When the owner later explores licensing, the linked service history and technician notes are what the reviewer asks about first.
What makes old Wintac records still useful#
Old Wintac records stay useful when they keep three things: links between records, the narrative in technician and call notes, and outcomes such as the invoice, the payment and any callback. Those three answer warranty questions and customer disputes, and they are also what AI developers look for in long service histories, because they show how real jobs unfolded over many years.
Run these checks before the old server is switched off, while there is still a way to fix a gap.
- Pick a long-standing customer and trace one job from the first call to payment using only the exported files.
- Confirm technician notes are complete and not cut off at a field length limit.
- Check that equipment records still point to the right sites and service tickets.
- Open a sample of attachments from the archive copy, not from the old server.
- Ask someone who was not on the project to answer a customer question from the archive alone.
How SourceX looks at legacy archives#
SourceX reviews archives like these starting from metadata only: the system, years covered and record families. Under the SourceX Enterprise Data Value Framework, age weighs against recency while scale, domain expertise and human-generated signal can weigh in favor. If a package proceeds through the SourceX five-step transaction, Preparation removes customer names, addresses and phone numbers from exports and notes, and Delivery happens from your own storage; SourceX does not host large archives.
Nothing leaves your server or archive during that first review, and you approve the final scope before any prepared copy is delivered.
Frequently asked questions
Can our new field service vendor import Wintac history?
Some vendors offer conversion from Wintac, but the scope varies. Ask exactly which record families they import, whether service history arrives as full records or summaries, and whether attachments come across. Build your own archive regardless, because a conversion is not a backup.
Do we need to keep a working copy of Wintac?
Not if your exports are complete and tested. Keeping a restorable backup with the installer and license details gives a fallback for questions the exports cannot answer, and some companies also keep an image of the old server on a virtual machine.
What if the person who knew Wintac has already left?
Start with IT and the server itself: find the data folder, the installer and any saved reports. Old report layouts show which fields mattered. Vendor support or a consultant familiar with Wintac may help, and nothing should be deleted until a restore test passes.
Is old Wintac data still worth reviewing for licensing?
It can be. Age reduces recency, but long, linked service histories with detailed technician notes can still interest AI developers. No one can put a value on it until a buyer engages with a specific, prepared package, and the first step is a metadata-only fit check.
Should we clean up Wintac data before archiving it?
No. Archive the data as it is, duplicates and all, so the copy matches the source system. Cleanup belongs on the way into the new platform or in a working copy of the exports. Cleaning the archive itself can remove details you may later need for a dispute, an audit or a warranty claim.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.