Utilities
The Utilities section in Administration is a collection of useful features designed for use by IT staff. Most of these features require some technical skills.
These features are categorized as follows:
| Category | Features |
|---|---|
|
Security |
|
|
Performance |
|
|
Low-level access |
|
|
Check specific configurations |
|
|
Import & export |
|
|
Search engine |
|
|
Repository migration |
|
|
Other |
|
|
Experimental features |
Repository migration
These background jobs, run from Administration > Utilities > Repository, retroactively rewrite content that already exists on disk — none is required for its respective feature to work day-to-day; all are optional one-off (or repeatable) tasks for bringing existing content in line with a configuration change.
- Content Store Migration — copies content already on the filesystem backend into S3 independently for each repository folder (datastore, cache, extraction, ocr template). Use this before switching a folder's "type" property from "filesystem" to "s3" — see Change repository home. Safe to run more than once: content already present at the destination is skipped, so a final run right before the switch only picks up what changed since the previous run.
- Repository Encryption Migration — encrypts content saved before "repository.content.encryption" was turned on (or while it was temporarily off) and is listed as one row per kind: document content and extracted text (Content: datastore, extraction), and the pdf/svg/mail preview cache (Cache: document/CAD previews converted to PDF or SVG, mail previews rendered to HTML). Each row runs independently. Optional: reads already handle a mix of encrypted and plaintext content correctly, so pre-existing content stays fully usable without running this — it exists only for installations that want everything on disk actually encrypted. Safe to run more than once per row: content already encrypted is skipped.
Both report progress live (found / processed / already done / errors) and can be followed in more detail via their dedicated logs, linked from the in-progress page.