Upgrade Content Central
Back up, run the installer, update the database, verify — the complete in-place upgrade procedure, including the one step people miss and the 7.8 lookup-list gotcha.
Before you begin
- A verified database backup (see: Back up your Content Central database)
- Administrator access to the Content Central server
- A maintenance window — users will be interrupted
At the end of this guide, your server runs the latest Content Central with your database upgraded to match, verified working, and a backup you could roll back to.
An upgrade is three acts: back up, run the installer, update the database. The third one is the step people miss — the installer updates the software, but the database update is a separate action you perform afterward.
Moving to a new server? You don't need this guide's in-place steps, and you don't need to reinstall your old version anywhere. Install the current release on the new server and follow Move Content Central to a new server — the Migration Assistant restores your existing database onto the new build, and the Create/Update Database step below is the only piece of this guide you'll reuse.
Can I upgrade directly from my version?
Check what you're running first: in Content Central, go to Admin > About and note the version. Then skim the release notes — they list what's changed in every release between your version and the current one, which is how you decide whether this upgrade brings the fix or feature you're after. The installer upgrades in place from recent versions — you run it on the server and it takes care of the rest. If your version is more than a couple of major releases old, or your setup is unusual (custom integrations, a web root install), send your version number to Ademero support and confirm the path before scheduling the window — a two-minute email beats a stalled Saturday upgrade.
Upgrades are a benefit of an active maintenance plan. If you're unsure whether yours is current, that's the other thing to confirm in the same email.
Who performs the upgrade, and what is included?
An active maintenance plan includes the software upgrade and Ademero performing the upgrade on your existing installation, including on-premises installations. There is no separate Professional Services charge for that upgrade. Your IT team or IT partner can also perform it using this guide. Contact Ademero Support to arrange assistance; server moves, cloud migrations, and unrelated new configuration are separately scoped work.
Having Ademero perform the upgrade
Send Support the lookup screenshots below so we can review existing external data connections and identify any preparation needed before moving to 7.8.
Tell Support your preferred date and time for the upgrade maintenance window so we can confirm availability. Users need to be out of Content Central during the upgrade.
Just before the agreed window, have your IT team or IT partner take and verify fresh server/database backups and confirm that the server allows outbound HTTPS access.
At the agreed time, Ademero connects remotely, performs the installation and database update, and handles the one-time license activation live if your installation uses an older offline key.
The remaining installation steps in this guide are for your IT team or IT partner if they are performing the upgrade themselves.
Coming from an older version? Arrange a one-time activation first
Current Content Central activates online — on startup it confirms your license with Ademero's licensing service over the internet. Older versions used an offline license key, and the upgraded software won't accept that old key on its own: it has to be activated once, online, before anyone can sign in.
Does this apply to you? Your version is printed at the bottom of the Content Central login page — for example, © 2006-2026 Ademero, Inc. v7.5.9204 (you don't have to sign in to read it; it's also under Admin > About once you're in). If that build number — the last part — is below 9435 (any version older than 7.5.9435, released 31 October 2025), you're on the offline-key era and this applies. Not sure how to read it, or your version looks unusual? Send your version and license key to Ademero support — a two-minute check that confirms whether you need this and saves a stalled Saturday.
What happens if you skip it: after the upgrade, Content Central shows an activation screen instead of the login page and no one can sign in until the license is activated. Your documents are untouched — it's a licensing gate, not data loss — but it's a hard stop.
How to avoid any downtime:
Before your maintenance window, contact Ademero support and tell them you're upgrading an offline-key installation, so they can activate your license from their side for this one-time transition.
Allow outbound HTTPS (TCP 443) from the server during the upgrade. A locked-down server that blocks outbound traffic has to permit this at least long enough to activate. (Ademero recommends leaving it open: once activated the software keeps running through brief outages, but ongoing license checks and support features rely on it.)
Coordinate the timing so support activates your license as the upgrade finishes. Done together, activation clears within about a minute of the services restarting, and your users never see the activation screen.
This is one-time. After the first online activation, later upgrades re-activate on their own, as long as the server keeps its normal outbound internet access.
Part 1 — Before you touch anything
The upgraded Content Central confirms its license online, so the server needs outbound HTTPS (TCP 443) to reach Ademero's licensing service. Most servers already allow this; a locked-down server that blocks outbound traffic won't activate and will hold users at an activation screen after the upgrade. If yours restricts outbound traffic, arrange to open 443 for the upgrade — and if your firewall filters by host, ask Ademero support for the exact address to allow.
Back up the database and verify it — full instructions here. Keep this backup until you've been stable on the new version for a comfortable period; it is your rollback.
Copy your configuration files somewhere safe:
ConnectionInfo.xmlfromC:\ProgramData\Ademero\Content Central\, and — if your IT team ever customized it —web.configfrom the Content Central website folder. The installer preserves the important settings automatically, but a two-minute copy beats discovering an exception.
Check your license status in the Configuration Manager. An expired maintenance plan blocks the upgraded version from running — if maintenance shows expired, contact Ademero before upgrading, not after.
Restart the server if Windows has a pending reboot. A half-pending Windows update is a classic cause of installer failure halfway through.
Tell your users: Content Central will be unavailable for roughly two hours.
While preparing, you may notice database drivers on the server that have nothing to do with Content Central (MySQL drivers are the classic example — some other application installed them). Content Central runs on Microsoft SQL Server. Don't uninstall drivers just because they're visible; another application probably needs them.
Part 2 — Run the installer
Download the current stable installer: dl.ademero.com/ccinstall.exe — this link always points to the latest stable release, and the version it installs is the top entry in the release notes. The installer downloads what it needs during installation — if your server can't reach the internet, use the offline package dl.ademero.com/ccinstall-offline.zip instead: extract the entire ZIP into one folder and run
ContentCentral_setup.exefrom there (every file in that folder is part of the installer — don't move or skip any).
Run the installer on the Content Central server, as an administrator, and follow the prompts. It stops the Content Central services, upgrades everything in place, reconfigures the website, and restarts the services — your settings, documents, and database connection carry through.
What you should see: the installer completes without errors. If it asks to reboot, reboot and continue with Part 3.
Part 3 — Update the database
Open the Configuration Manager (Start menu > Ademero) and click Create/Update Database. This upgrades your database to match the new software version.
warningDo not close the Configuration Manager and do not restart the server while the database update runs. On a large system it can work silently for many minutes — that's normal. Interrupting it mid-update is the single most damaging thing you can do in an upgrade; if it seems stuck, call Ademero support before touching anything.
What you should see: the update completes and reports success. If you skip this step, the website shows a database-version message instead of the login page, and the services idle — that message is your reminder to come back and run this step, not a failure.
Part 4 — Verify
Browse to your Content Central site. What you should see: the login page — and after logging in, your normal dashboard.
Open a few documents, run a search, and capture a test document end to end.
Trigger a workflow or approval on a test document, and confirm a notification email arrives — mail settings occasionally need attention after upgrades.
Confirm the required installed services below show Running in Windows Services. Start Search PostgreSQL before Search, and preserve services intentionally disabled before the upgrade.
Windows Services display name Ademero Content Central Capture Service Ademero Content Central Catalog Service Ademero Content Central Workflow Service Ademero Content Central Integration Service Ademero Content Central Health Service Ademero Content Central Search Ademero Content Central Search PostgreSQL Ademero Content Central Component Library Ademero Diagnostics Service noteOlder installations may have only the five core services. Search, Search PostgreSQL, Component Library, and Diagnostics depend on the components installed; an absent service is not a failure. Diagnostics may be shared with other Ademero applications, so coordinate its maintenance with their administrators. SQL Server and the IIS website are separate from this list.
If the license shows unactivated after the upgrade
For an install that already activates online, your license normally carries straight through. If Content Central shows unregistered or unactivated afterward: give it a little while (activation retries on its own), confirm the server still has outbound HTTPS access, then contact Ademero support with your license key if it hasn't cleared — quick to resolve, and your documents are unaffected.
If you upgraded from an offline-key version, an activation screen is expected, not a fault — follow Coming from an older version? Arrange a one-time activation first near the top of this guide to clear it without downtime.
Upgrading from a version before 7.8? Read this
Content Central 7.8 moved to 64-bit, which is invisible everywhere except one place: external data lookups (fields that pull choices from another system via ODBC — vendor lists from your accounting system, for example). Those connections are registered per-bitness in Windows, and existing 32-bit entries don't carry over.
Symptom: after the upgrade, a lookup field that used to show a choice list renders as an empty text box, or lookups silently return nothing. Fix: re-create each data source in the 64-bit ODBC Data Sources administrator (Start menu > "ODBC Data Sources (64-bit)") with the same name it had before. Sources built on Excel/Access/text files also need Microsoft's 64-bit Access Database Engine installed first.
Send Support screenshots to check lookup preparation
Before upgrading, your IT team can send these screenshots so Support can compare the configured sources with the Windows connections and drivers:
On the Content Central server, open the Windows Start menu, search for ODBC Data Sources (32-bit), and open it. Select the System DSN tab and take a screenshot of the list.
Return to the Windows Start menu, search for ODBC Data Sources (64-bit), and open it. Take a screenshot of the System DSN tab, then select Drivers and take another screenshot. Include the window title and readable names in each image.
Sign in to your current Content Central site as an administrator. Open Administration, then External Data Sources, and take a screenshot of the list—even if it is empty.
For each source in that list, click its Details icon. Take a screenshot of the upper section showing Name and the selected Select System DSN value. Click Cancel to return to the list without making changes, and repeat for the remaining sources.
Attach the screenshots to your Support ticket reply so we can review them before the upgrade.
Support can review these screenshots and identify existing connections that need 64-bit preparation for the upgrade. This upgrade-related assistance is included in active maintenance. A configured source alone does not prove that a field currently uses it; additional configuration review may be needed. Setting up unrelated new connections is separately scoped work.
Update Content Director on every computer that edits documents
Content Central 7.8 no longer accepts the Content Director that came with earlier versions. After the upgrade, Edit does not open documents on any computer that still has the old one.
Before the upgrade: ask users to check in every document they have checked out. After the upgrade: install the 7.8 Content Director on each of those computers. It replaces the old version, so there is nothing to uninstall first. The steps are in Install or update Content Director.
If the upgrade fails
Don't improvise — the safe rollback is: reinstall the previous version's installer, restore your pre-upgrade database backup, and you're back where you started. Never run old software against an upgraded database or vice versa — matched pairs only. If anything about the failure is unclear, stop and contact Ademero support with the installer log; rolling back correctly takes minutes, rolling back incorrectly takes days.
