Join our Newsletter — 33% off our NHI Course
Home› Glossary› Architecture & Implementation› Brownfield Migration
Architecture & Implementation

Brownfield Migration

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Architecture & Implementation

A migration approach that converts an existing SAP system into the new platform while preserving much of the current structure. It can reduce disruption and speed delivery, but it often carries forward legacy roles, customisations, and access risks unless teams deliberately remediate them during the project.

What Brownfield Migration Means in Practice

Brownfield migration is less a clean-sheet rebuild than a controlled transformation of an existing enterprise SAP environment. The value is speed and continuity: teams keep much of the current structure, which can reduce downtime and rework, but the trade-off is that old design choices are more likely to survive unless they are explicitly addressed.

That makes the term useful for understanding migration strategy, not just technology choice. It describes a path where legacy processes, permissions, integrations, and custom code are carried forward into the new platform unless the project deliberately separates what should be retained from what should be retired.

Why Brownfield Migration Is Chosen

Organisations usually choose a brownfield approach when they need to modernise without interrupting business operations more than necessary. It can be attractive when the existing SAP estate is large, highly customised, or tightly embedded in core finance, supply-chain, or reporting processes.

The approach is often selected because it preserves configuration investment and shortens delivery timelines. It also reduces the organisational friction that comes with a full reimplementation, since users can keep familiar processes and many technical dependencies can be carried forward rather than rebuilt from scratch.

What Carries Over During the Move

The main feature of brownfield migration is inheritance. That includes existing roles, authorisations, custom objects, interface logic, master-data assumptions, and operational workarounds that may have accumulated over years of production use.

Because the method preserves structure, it can also preserve weaknesses. Access that was acceptable in the old environment may remain excessive in the new one, and customisations that once solved a local need may become technical debt if they are not revalidated against the target platform design.

Security and Access Implications

Brownfield migration is security-sensitive because a migration that preserves business continuity can also preserve hidden privilege, stale approvals, and poorly governed exceptions. A system may look modernised while still carrying forward role design flaws, segregation-of-duties conflicts, or orphaned access relationships.

That is why the migration should be treated as a security review opportunity as well as an engineering project. The safest outcome is not simply moving everything intact, but identifying which access patterns, custom functions, and administrative pathways need redesign before go-live.

Risk and Threat Considerations

Brownfield migration can create a false sense of security if teams assume the new platform automatically resolves old access problems. Legacy roles, custom code, and migration shortcuts can preserve excessive privilege or weak control boundaries into the target environment.

Failure mechanism: inherited permissions, technical debt, and incomplete remediation allow old access paths to survive the move, which can leave the post-migration environment exposed even when the platform itself is up to date.

Impact: attackers or insiders may benefit from overprivileged accounts, persistent exceptions, or unreviewed integrations, increasing the likelihood of unauthorised access, segregation-of-duties failure, and post-migration control gaps.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeBrownfield migrations often carry forward excessive access, so least privilege directly governs role cleanup.
IA-5 — Authenticator ManagementMigration projects often inherit credentials and authentication material that need lifecycle control.
CM-6 — Configuration SettingsBrownfield migration preserves existing configuration, making baseline review and hardening essential.
Recommendation — Revalidate migrated roles and remove unnecessary permissions before cutover. Rotate or replace inherited authenticators and secrets during migration. Review inherited configurations and reset insecure settings to approved baselines.
CIS Controls v8CIS-5 — Account ManagementThe term centers on preserving or remediating existing accounts and permissions during transition.
Recommendation — Inventory, review, and remove unnecessary accounts and access paths during the migration.
ISO/IEC 27001:2022A.8.9 — Configuration managementBrownfield migration depends on controlling inherited system configurations and exceptions.
Recommendation — Document and approve configuration changes and inherited exceptions before go-live.

Practitioner Guidance

Governance implication: treat the migration boundary as a control boundary, not just a technical cutover. The project should explicitly decide what is preserved, what is retired, and what must be re-authorised before it enters the new environment.

What to watch for: role sprawl, copied administrators, dormant customisations, and exceptions carried forward "because they still work" are the strongest warning signs that the migration has reproduced the old risk model instead of improving it.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org