Old ACT! and legacy CRM databases: preserving decades of customer history

Why old ACT! and legacy CRM files are worth saving#

Old ACT! databases, and those of other desktop-era contact managers, often hold the longest continuous customer record a manufacturer or distributor has. Many were set up before the company's current ERP, and they kept every call, quote follow-up, complaint and visit note that sales reps logged over the years.

That history explains things the ERP cannot: why a customer left for a competitor and came back, which rep negotiated a pricing exception, what a buyer complained about before a large order. For an owner planning succession or a sale, it is part of how the business actually works.

The risk is physical. These databases tend to live on one aging PC or server, on an unsupported version of Windows, administered by someone who has left. When that machine fails or goes to recycling, the history goes with it.

Step one: inventory every part of the database#

An old ACT! or legacy CRM database is rarely a single file, so the first step is a full inventory of its parts. In many later ACT! installations, the file users open is a small pointer to a database running in a separate database server, with attachments in supporting folders. Other desktop-era contact managers changed database formats across their versions, so older and newer installations need different tools; check which one yours uses before planning the export. In most of these products, linked documents may be nothing more than paths to files on a shared drive.

• 1The database files and the PC or server that hosts them.
• 2Attachment, document and email folders that sit beside the database.
• 3Shared-drive paths that linked documents point to.
• 4The software version, installer media and license key.
• 5Administrator user names and passwords, or who can reset them.
• 6Any existing backups, with their dates and where they are stored.
• 7Custom fields, lookup lists, templates and saved reports.

Step two: protect the original before anyone opens it#

The original database should be copied and set aside before anyone tries to open, repair or upgrade it. If the machine still runs, take a full image of the disk; if it does not, have the drive copied by someone who knows not to write to it.

Work only on copies from then on. Opening an old database in a newer version can convert it in place, and repair utilities can discard records they cannot read. Keep the untouched original in read-only storage with a checksum, so you can show later that nothing changed.

Record the version number from the program's Help or About screen while the machine still runs. That number decides which tools and versions can open the data later.

Step three: open a working copy#

Opening an old ACT! file usually requires a compatible version of ACT! itself, because the data is not stored in a format Excel can read. The same holds for most contact managers of that era. Choose the route that matches the version you found and the skills you have on hand.

Step four: export the history, not just the contact list#

The history is the part worth saving, and a contact list export alone rarely carries it. Plan a separate export for each record type and keep the internal record IDs that link them, so a note can still be tied to its contact and company.

Export to plain formats: CSV for tables and the original files for attachments. Then check the result against the working copy by opening a handful of long-standing customers on screen and confirming that every note, activity and attached document appears in the export with the right date and contact ID.

• 1Companies and contacts, with record IDs and custom fields.
• 2Notes and history entries, with dates, record manager and author.
• 3Completed activities: calls, meetings and to-dos with their results.
• 4Opportunities or sales stages, with products and outcomes.
• 5Email records and attached documents, matched to contacts.
• 6Groups, lookup lists and user names needed to decode the fields.

Illustrative: a manufacturer's old CRM server in the storage room#

Illustrative: a fictional industrial fastener manufacturer, family-owned and preparing to sell to its management team, still runs its original desktop contact manager on a server in a storage room. The company changed CRMs years ago but imported only active contacts, and the old server is due for recycling.

The COO has the drive imaged first, then IT builds a virtual machine with the original software version. History exports run table by table with contact IDs. Linked documents point to a drive letter that no longer exists, so IT recovers them from an old file-server backup and re-links them by path.

The result is a read-only archive in which each customer's history matches its ERP customer number. The incoming owners can see how key accounts were won and kept, and the company knows exactly what the archive holds if a licensing review ever comes up.

What to keep, restrict or drop#

Records in an old CRM do not all deserve the same treatment, so sort them before they reach the archive. Decide on the working copy, never on the original.

How SourceX looks at legacy CRM archives#

SourceX looks at a recovered ACT! or other legacy CRM archive as historical customer-relationship records, most useful when they can be linked to orders or service records in another system. The first conversation uses metadata only: product and version, years covered, record types and whether history links to customer numbers.

If the archive moves through the SourceX five-step transaction, Rights checks purchased lists and customer terms, Preparation removes names, contact details and personal remarks, and Approval stays with the company. The recovery steps themselves become part of the provenance recorded in the SourceX Evidence Packet.