OptimiDoc Server Help Center
OptimiDoc Server Help Center
Breadcrumbs

Upgrade and Migration

This section covers upgrading OptimiDoc to a new version, migrating an installation to a different server, and moving the database from LocalDB to a full SQL Server instance. Follow these guides for a smooth transition with minimal downtime — and, where encryption is enabled, without losing access to your stored secrets.

In This Section

Page

Description

General Upgrade

In-place upgrade procedure: pre-flight checks, backup, running the installer, verification and rollback.

Migration to a New Server

Moving an installation to new hardware or a new VM, including the database, configuration, DNS/IP cutover — and recovering the encryption keys on the new machine.

LocalDB to SQL Server

Migrating the OptimiDoc database from SQL Server LocalDB to a standalone SQL Server or SQL Server Express instance.

About Version 26.07

Version 26.07 (released 7 July 2026) is the first published release since 26.01. The most visible change for anyone upgrading from 26.01 is the user interface: the modern React UI is now the default — browsing the server root redirects to /ui — while the previous console remains available at /old. First login after the upgrade lands on the new dashboard. See the Release Notes for the full change list before you begin.

Before You Begin

All upgrade and migration procedures share these prerequisites:

  • Full backup of the OptimiDoc database and the App_Data configuration folder.

  • Maintenance window — schedule downtime and notify users that printing and scanning will be briefly unavailable.

  • Administrator access to both the OptimiDoc web console and the Windows server.

  • Matching versions — when migrating, run the same OptimiDoc version on the target server as on the source before restoring a database.

  • Encryption recovery key — if encryption is enabled, download the recovery key (.odrk) from the Encryption page and store it securely before any hardware or server change. Because the master encryption key is bound to the machine, you need this file to recover your keys on new hardware. This is essential for Migration to a New Server; an in-place upgrade on the same machine does not require it.