Many ACT! users are surprised to discover that installing the latest version of ACT! doesn’t automatically allow them to open databases from much older releases.
That’s because ACT! has changed its database architecture multiple times over the past four decades.
Major changes have included:
- Moving from DOS to Windows
- Changing the database file format
- Migrating to Microsoft SQL Server
- Changing SQL Versions
- Introducing new database tables
- Adding support for attachments
- Expanding security and user permissions
- Enhancing synchronization and remote databases
- Supporting cloud and web access
Each of these changes required modifications to the underlying database structure. As a result, the newest version of ACT! may not recognize databases created many years earlier.
What Is an Intermediate ACT! Upgrade?
An intermediate upgrade involves opening your database in one or more earlier versions of ACT! before converting it to the latest release.
Think of it like updating an old computer operating system. You often can’t jump directly from a decades-old version to the newest one—you need to pass through one or more intermediate versions first.
For example, an ACT! 6 database typically cannot be opened directly in ACT! Premium v26. Instead, it must first be converted using one or more compatible versions before it can be upgraded again.
The exact path depends on the version, the condition of the database, and whether any previous upgrades have already been performed.
What If My Act! Database Is Corrupted?
Version compatibility is only one part of a successful conversion.
If your database has damaged indexes, missing files, SQL corruption, or other integrity issues, it may need to be repaired before any upgrade can begin.
Common symptoms include:
- “Database cannot be opened.”
- “Unsupported database version.”
- Login failures.
- Missing contacts.
- Missing notes or histories.
- Synchronization errors.
- SQL connection errors.
- Unexpected program crashes.
Fortunately, many damaged databases can be repaired without losing valuable customer information.
Tech Benders’ Recommendation
Before attempting any database conversion:
- Identify the ACT! version that created the database.
- Create a complete backup.
- Determine whether the database is file-based or SQL-based.
- Check the database for corruption.
- Follow the appropriate upgrade path rather than skipping versions.
Taking these steps greatly reduces the risk of data loss and increases the likelihood of a successful conversion.
In the next section, we’ll explain the recommended upgrade paths for every major ACT! release and identify the situations where intermediate conversions are required.