How to Transfer Sage Timeslips to a New PC: Step-by-Step

Moving Sage Timeslips to a new computer requires more than installing the application. You must also transfer or restore your existing database, confirm that your license is valid, and make sure the new installation can access your client information, time entries, billing records, and reports.

The process depends on how you currently use Timeslips. A single-user installation may store the application and database on one computer, while a network installation may store shared data on a server that multiple workstations access.

The safest approach is to back up the existing database, prepare the new computer, install a compatible Timeslips version, restore or reconnect the data, and test the system before retiring the old computer. This guide explains the essential steps in order, including what to do if the database is missing, the license fails, workstations cannot connect, or QuickBooks integration stops working after migration.

Before You Move Sage Timeslips to a New Computer

First, identify your existing setup. This determines which migration steps you need and helps prevent unnecessary installation or licensing changes.

Current setup	What you need to do
Single-user installation	Back up the database, install Timeslips on the new computer, and restore the backup.
Network installation with a server	Move or restore the shared database and application components as required, then reconnect workstations.
New workstation using an existing server	Install or configure the workstation to access the existing shared installation and database.
Moving to a different Timeslips version	Confirm the supported upgrade and database conversion process before opening the old data.
Moving to a new server	Plan the database location, permissions, network paths, licensing, and workstation reconnection.

Gather Your Existing Installation Information

Before changing anything, record the following details:

• Your Sage Timeslips version and release.
• Whether the installation is single-user or network-based.
• The location of the current database and application installation.
• Your available backup files and the date of the most recent successful backup.
• Your product activation information, serial number, or other licensing details, as applicable to your version.
• The names of any workstations or servers that connect to the database.
• Whether Timeslips exchanges information with QuickBooks or another accounting application.

You can check the version and product information from within Timeslips. The exact menu names depend on the release.

Important: Do not uninstall Timeslips, format the old computer, delete the existing database, or deactivate a license until you have confirmed that your data is backed up and the new installation works.

How to Move Sage Timeslips to a New Computer?

Follow these steps in sequence. Complete each stage before proceeding to the next one.

Step 1: Back Up Your Sage Timeslips Database

Creating a current backup is the most important part of the migration. It gives you a recovery point if the installation fails, the database cannot be opened, or the new computer has a compatibility problem.

1. Open Timeslips on the old computer.
2. Confirm that you have opened the correct, current database.
3. Use the application’s database backup function. The exact menu location depends on your Timeslips version.
4. Save the backup to a separate location, such as an external drive or a secure folder accessible from the new computer.
5. Check that the backup completed successfully and that the file is present at the destination.
6. If possible, test the backup by restoring it to a separate test location rather than overwriting the live database.

Do not assume that a backup is reliable simply because a file exists. A test restoration provides stronger evidence that it can be used for recovery. If Timeslips is used by multiple people, coordinate the backup with the other users and follow the version-specific instructions for ensuring that the database is not being changed during the process.

Why this matters: A current backup protects your existing client records, slips, billing history, and other database information from avoidable migration mistakes.

Step 2: Identify and Preserve the Complete Database

Before installing Timeslips on the new computer, confirm where the live database is stored. In many traditional desktop installations, the database consists of multiple related files stored together in a database folder. A file named Main.db may help identify the database, but it is not necessarily the complete database by itself. To locate the data:

1. Open the current database in Timeslips and check its location using the available database or support information.
2. Identify the folder containing the live database.
3. Check whether there are multiple database folders or backups.
4. Confirm which database is current by checking its location and relevant dates.
5. Preserve the complete database folder if you need a direct copy for a supported migration method.

Do not copy only Main.db and assume that all information has been transferred. Other required files may be stored alongside it. For most users, restoring a verified Timeslips backup is a clearer migration method than manually copying database files. A direct folder transfer may be appropriate for certain installations, but you should follow the instructions for your specific version and configuration. If your database is already stored on a shared server, you may not need to transfer it at all when replacing just one workstation.

Step 3: Prepare the New Computer

Before installing Timeslips, make sure the new computer meets the requirements for your particular release. Check the following:

• Windows version and edition.
• Available disk space and system memory.
• Administrator access for installation.
• Network connectivity, if the database is stored on a server.
• Access permissions for the intended installation and database folders.
• Compatibility with QuickBooks and any other integrated software.

Sage Timeslips Premium has specific workstation and server requirements. For example, supported Windows editions and server configurations vary by release. Do not assume that a requirement listed for the latest version also applies to an older Timeslips installation.

If you are moving to Windows 11, confirm that your exact Timeslips version supports your planned configuration before proceeding. For a network installation, also verify that the server and network configuration meet the product’s requirements. Do not place the database on an unsupported network-attached storage device simply because it is convenient.

Why this matters: Installing the application on an incompatible system can create problems that appear to be database or licensing errors.

Step 4: Install the Correct Sage Timeslips Version

Once the new computer is ready, install the version that matches your migration plan.

1. Obtain the installer from your legitimate Sage download or product installation source.
2. Confirm that the installer matches the intended Timeslips product and version.
3. Sign in to Windows with an account that has administrator permissions.
4. Run the installer and follow its instructions.
5. Enter the requested activation information if prompted.
6. Complete the installation and launch Timeslips to confirm that the application opens.

For current Sage Timeslips Premium installations, Sage’s installation instructions recommend installing the application on the local computer’s drive. The precise location and licensing procedure may differ for older releases and network configurations. If you are reinstalling the same version, do not automatically install a newer version just because it is available. A newer release may require database conversion, which should be planned and backed up before you proceed.

If your existing Timeslips version is no longer available through the normal download portal, locate your original installation media or ask Sage about legitimate access to the required installer.

Important: If you are moving from an older version to a newer one, follow the supported upgrade and conversion procedure. Do not open your only copy of the production database in a version that may convert it until you have a verified backup.

Step 5: Restore the Database on the New Computer

After installing the correct version, restore the backup you created in Step 1.

1. Copy the backup file to a suitable local drive on the new computer if it is stored on removable media.
2. Start Timeslips.
3. Open the database restore function.
4. Select the correct backup file.
5. Choose the intended destination for the restored database.
6. Review the destination carefully before confirming the restoration.
7. Allow the process to finish and check for any error messages.
8. Open the restored database and confirm that it loads successfully.

Menu names may differ by version, so use the backup and restore instructions for your release.

Watch the destination carefully. Some restore workflows can overwrite an existing database if you select the wrong location. If you want to preserve the original or perform a test restoration, choose a separate database location when that option is available. After restoration, verify several important items:

• Client records are present.
• Recent time entries and expenses are available.
• Billing information and transaction history appear correct.
• Reports and statement options are available.
• The latest expected data is present.

Do not rely solely on the fact that Timeslips opens. Check actual records and compare them with information you know was entered before the migration. If you are moving a database to a newer Timeslips version, the restoration may also initiate or require a conversion. Keep the original backup untouched and follow the version-specific conversion instructions.

Step 6: Confirm the Sage Timeslips License

A successful installation does not necessarily mean that the license has transferred correctly. Depending on the product version and installation type, Timeslips may request activation information or use licensing arrangements associated with a network installation. To check licensing:

1. Open Timeslips on the new computer.
2. Read any activation or licensing message carefully.
3. Compare the prompt with your existing product and registration information.
4. Follow the licensing procedure for your version.
5. If the license is already in use or activation fails, contact Sage or your authorized support provider before making repeated changes.

For a single-user installation, the new computer may need the appropriate activation key or registration information. For a network installation, adding a replacement workstation is not always the same as transferring a single-user license. The workstation may need to connect to the existing licensed installation instead. Avoid deleting license configuration files or clearing licenses as a trial-and-error fix. Those actions can affect other users or prevent an existing installation from opening.

Step 7: Reconnect Timeslips to the Correct Database

If the application opens but displays an empty database, old information, or a missing-database message, it may be opening the wrong location. To check:

1. Identify the location of the database you restored or retained.
2. Use Timeslips’ database-opening function to select the intended database.
3. Confirm that the selected database contains your current records.
4. Close and reopen Timeslips to verify that the correct database remains accessible.

For network installations, check the shared database location and confirm that the new computer can access it with the required permissions. Do not create a new live database simply because the existing one does not appear automatically. Creating an empty database may make Timeslips open, but it will not bring back your previous client and billing data.

If the database does not open, record the exact error message and investigate the path, permissions, database completeness, and version compatibility before attempting further repairs.

Step 8: Reconnect Workstations if You Moved to a New Server

If you have moved the shared Timeslips installation to a different server, the existing workstations may still point to the old server. This step is not normally required when you are replacing only a workstation and keeping the original server unchanged. For a server migration:

1. Confirm that the database has been backed up and restored or moved using the supported procedure.
2. Verify that the new server’s Timeslips installation and database work before reconnecting other users.
3. Confirm that the intended shared folders are accessible.
4. Check the access permissions required by Timeslips.
5. On each workstation, use the version’s supported workstation or Station Administrator configuration options to update the installation path if necessary.
6. Point the workstation to the correct Timeslips configuration file or shared installation location, as appropriate for that release.
7. Use a consistent path configuration across workstations.
8. Open Timeslips from each workstation and verify that it connects to the same live database.

For many traditional network setups, a consistent Universal Naming Convention (UNC) path, such as a server and shared-folder path, can be more reliable than drive letters that may be mapped differently for different users. Follow the requirements for your particular Timeslips version. Do not assume that copying the old configuration file unchanged will work when the server name or share location has changed. If one workstation connects successfully but another does not, compare the paths, permissions, and configuration settings on the two computers before changing the database itself.

Step 9: Test QuickBooks Integration

If your Timeslips installation exchanges data with QuickBooks, test that connection after the migration. Do not assume that integration will continue to work just because Timeslips and QuickBooks both open successfully. Follow these checks:

1. Confirm that the correct QuickBooks product and version are installed or accessible.
2. Verify that the QuickBooks company file is available from the new computer.
3. Check whether the existing integration requires a particular Windows user, access permission, application configuration, or connection method.
4. Open the integration settings in Timeslips and review the existing configuration.
5. Check any required application permissions or authorization prompts.
6. Perform a small, controlled test using the integration workflow supported by your setup.
7. Confirm the results in both applications before resuming routine transfers.

The exact process depends on your QuickBooks edition, Timeslips version, and integration method. For example, an older integration using a local desktop installation may have different requirements from a network or newer configuration.

If the integration fails, do not repeatedly transfer live billing information. Identify whether the failure involves the company file path, application compatibility, permissions, or the integration component itself. For a QuickBooks integration error after migration, verify compatibility with Sage and the relevant QuickBooks documentation before changing settings or reinstalling either application.

Common Problems When Moving Sage Timeslips to a New Computer:

Migration issues are easier to diagnose when you match the symptom to the most likely cause instead of reinstalling the application repeatedly.

Problem	What to check first
Database is missing	Confirm the database location and select the correct database.
Timeslips opens an empty database	Check whether a new or test database was selected instead of the production database.
Database will not open	Verify that the complete database is present and that the Timeslips version is compatible.
License error appears	Confirm activation information and whether the setup is single-user or network-based.
Workstation cannot connect	Check the server path, shared-folder access, permissions, and workstation configuration.
QuickBooks integration fails	Verify application compatibility, company-file access, permissions, and integration settings.
Recent records are missing	Confirm the backup date and make sure the correct database was restored.
Database conversion fails	Preserve the original backup and follow the supported conversion procedure for the relevant versions.

How to Move Sage Timeslips to a New Computer Without Losing Data?

The safest way to reduce the risk of data loss is to maintain a clear separation between the original database, the backup, and the migrated working database. Follow these principles:

1. Keep the original data unchanged. Do not delete or overwrite the old database while setting up the new computer.
2. Use a verified backup. Confirm that the backup completed and, where possible, test a restoration.
3. Confirm the database location. Avoid confusing a test database, an empty database, and the production database.
4. Check the version before conversion. A move to another computer is not necessarily the same as an upgrade to a new Timeslips version.
5. Verify the migrated records. Check recent client activity and billing information rather than relying only on a successful application launch.
6. Test the complete workflow. Confirm that users can enter time, access billing information, run reports, and use integrations as required.
7. Create a new backup after migration. Keep it separate from the working database and follow your organization’s backup policy.

If the old computer is damaged and you cannot open Timeslips, check whether you have a usable backup before attempting recovery. If no backup is available, preserve the existing drive or recovered database files and obtain qualified assistance before making changes that could reduce the chance of recovery.

How to Prevent Sage Timeslips Migration Problems?

A little preparation can prevent many installation and database issues.

• Maintain regular backups and periodically test restoration.
• Keep a record of your Timeslips version, product information, database location, and network configuration.
• Confirm operating-system and application compatibility before replacing hardware.
• Document any QuickBooks integration settings and dependencies.
• Keep server and workstation paths consistent where required.
• Verify that users have the appropriate folder permissions.
• Coordinate server moves with everyone who uses the database.
• Retain the old computer or a complete, verified copy of its data until the new setup has been tested.

For network installations, plan the migration during a maintenance window so users are not making changes while the database is being moved. If your business relies on billing and time-entry records every day, consider preparing the new computer and verifying the installation before the final migration. This can reduce downtime and make it easier to return to the original setup if something goes wrong.

Conclusion: 

To move Sage Timeslips to a new computer safely, start by identifying your installation type and creating a reliable backup. Prepare the new computer, install the correct Timeslips version, restore or reconnect the database, verify licensing, and test any network workstations and QuickBooks integration.

The most important precaution is to preserve the original database and backup until the migrated installation has been thoroughly checked. If you encounter a licensing error, database conversion failure, or network connection problem, diagnose that specific issue instead of repeatedly reinstalling the application. Following this sequence helps you move your Timeslips installation while protecting existing client records, time entries, and billing information.

FAQs of Move Sage Timeslips to a New Computer: