Migrate from another OptiTech organization

Mergers, acquisitions, and restructurings mean compliance programs need to move: two organizations become one, a subsidiary spins out, or a group consolidates entities. This guide covers moving a program between OptiTech organizations without losing history.

What transfers

• Frameworks and controls: active frameworks with their controls and cross-mappings
• Evidence history: the append-only evidence log transfers with its hash chain intact, so auditability survives the move
• Documents: policies with version history, approvals, and e-signatures
• Risk and vendor registers: risks, treatments, suppliers, and contract data
• The audit log: who did what, before and after the move

1. Plan the target structure

   Decide the destination: merge into one organization, or keep separate organizations under group oversight on the Enterprise plan. If the entities face different regulators (for example, one under DORA), separate organizations with group reporting is usually cleaner.

2. Request the transfer

   Organization transfers are run by our team to keep the evidence chain intact. Contact support with the source and target organizations, and you'll get a transfer plan with a scheduled window.

3. Reconcile controls

   Where both organizations had controls for the same requirements, the import proposes which to keep. Cross-mapping consolidates the rest, and unmatched controls become tasks.

4. Reconnect integrations

   Integrations re-authenticate against the target organization. Evidence collection resumes within minutes, and the historical log from both sources remains queryable.