Transport AC

Your iManage content, in your hands.

Transport AC (Auxiliary Cache) keeps a regularly updated, verified and encrypted copy of your iManage documents, metadata and security in a repository you host, with keys you control, ready for backup, reporting, integration and emergency access.

Your content, in a copy you control

Moving to iManage Cloud raises questions the platform alone does not answer. Where is our independent copy? How do we report across all our content when our reporting tools cannot run against the cloud? How do other systems reach it? What do we fall back on if iManage cannot be reached? Ad hoc exports are not an answer at firm scale.

What you get

• A complete local copy. Documents, profile metadata, security, users and groups, workspaces and folders from your iManage library, copied to a location you choose.
• Scheduled, incremental updates. After the initial load, a daily task picks up only what changed in iManage. A weekly verification finds and repairs anything missing or modified.
• Encrypted, with your keys. Cached content is stored encrypted, and the encryption keys stay with the firm, not with RBRO or iManage.
• Lightweight by design. It does not replicate the whole iManage environment. Limit the initial load to recent content and exclude clients or matters that should not be cached.
• Reporting and integration. Query the repository database directly for auditing and reporting, and feed tools that cannot call iManage's own interfaces.
• Emergency access. When iManage cannot be reached, administrators find documents in the cache and provide copies to users, with a download history.
• Notifications. Email alerts on task failures, with run status and error reporting.

Works with

iManage Cloud and iManage Work on premises as the source. The cache is hosted on premises, on your infrastructure.

Common questions

Does Transport AC replace iManage's own backups?

It gives you an independent copy that you hold, refreshed daily and verified weekly, which is what audit and risk teams ask for.

‍

Does it affect iManage performance?

Updates run as a scheduled task and are incremental after the initial load. Reporting runs against the cache, not against iManage.

‍

What can we report on?

Profile metadata, security, custom fields, users and groups, workspaces and folders, plus the documents themselves.

‍