Skip to content
English
Submit a support ticket
  • There are no suggestions because the search field is empty.

How do I prepare to migrate to Entity Management?

Consolidate duplicate per-entity programs into one centrally managed framework.

If you adopted Impero before Entity Management, you've probably built around the old access limits - most commonly by copying the same control program once per entity because that was the only way to scope access. Entity Management lets you consolidate all of that into one centrally managed framework. This article explains how to prepare.

Note! Migration is a planning exercise as much as a technical one. For larger groups, involve your Customer Success Manager or the support team early.

Where you're starting from

Most organizations are in one of these situations:

  • Duplicate programs per entity - many near-identical programs (often the same controls, copied), each scoped to one entity, with minor local tweaks.

  • One program, separated by tags - a single program where entities are distinguished using assignment tags.

  • One framework per ERP system - different control sets for different parts of the business.

Your starting point determines how much consolidation work there is. If you already run a single program and just live with the data-separation limits, switching on Entity Management is straightforward - you enable it and match entities to the existing assignments. If you're split across many duplicate programs, there's more mapping to do.

The target setup

The goal is a master control library - one control program (or one per process, e.g. order-to-cash, procure-to-pay) that holds your controls once. You then attach entities to it and manage all access and assignments at the entity level. The old duplicate programs are retired, but their history remains accessible.

How to prepare

  1. Inventory your current programs and controls. List every program and the controls inside, so you can see where the same control has been copied across entities.
  2. Confirm the controls match across entities. Consolidation assumes each entity runs the same set of controls. Note any genuine local variations you want to keep, versus copies you can collapse.
  3. Map old to new. Decide your target structure - one library, or one program per process - and map each existing control to its place in it.
  4. Define your entities. Create the entities you'll attach to the new program(s). See How do I set up my entity structure?.
  5. Plan access. Decide which users and groups get Admin / Edit / View on which entities.
  6. Consolidate and cut over. Build the master library, attach entities, match assignments, then retire the old programs. History stays available.