Explore key challenges of SAP ECC to S/4HANA PLM migration in pharmaceutical manufacturing and how Migravion helps to resolve them.

SAP ECC to S/4HANA PLM Migration in Pharmaceutical Manufacturing: Lessons from the Field 

Digital transformation in pharmaceutical manufacturing rarely starts with greenfield systems. Most organizations operate within highly customized SAP ECC landscapes built over decades of product development, regulatory adaptation, acquisitions, manufacturing expansion, and evolving compliance requirements.

As pharmaceutical companies move toward SAP S/4HANA, many quickly discover that Product Lifecycle Management (PLM) migration is one of the most technically demanding aspects of the entire transformation initiative.

Unlike conventional master data migration projects, SAP PLM migration involves deeply interconnected business objects, complex dependencies, regulatory traceability requirements, custom-developed structures, and highly specialized manufacturing logic. Specifications, recipes, document records, classifications, and Bills of Materials (BOMs) are often intertwined through relationships that standard migration approaches cannot fully interpret or preserve.

In many cases, migration teams initially assume that PLM data migration is simply another ETL exercise — extract the data from ECC, transform it slightly, and load it into SAP S/4HANA. But real-world pharmaceutical environments are rarely that straightforward.

What appears to be structured master data often contains:

• Hidden dependencies
• System-generated relationships
• Legacy custom tables
• Flattened recipe structures
• Multi-level BOM alternatives
• Embedded business logic accumulated over years of operations

When these dependencies are overlooked, organizations risk:

• Broken specification links
• Incomplete traceability
• Invalid recipe structures
• Duplicate BOMs
• Compliance exposure
• Production disruptions
• Significant manual remediation after go-live

This article explores several real-world SAP ECC to SAP S/4HANA PLM migration challenges commonly encountered in pharmaceutical manufacturing environments and examines how advanced transformation logic, dependency-aware orchestration, and intelligent restructuring can help organizations execute successful migrations at scale.

The scenarios described here are based on an actual large-scale migration project involving:

• More than 1,200 specifications
• More than 2,500 recipes
• Hundreds of document information records (DIRs)
• Approximately 9,000 BOMs

The examples provide valuable lessons for organizations planning complex SAP PLM migrations in regulated manufacturing industries.

Why SAP PLM Migration Is Especially Complex in Pharmaceutical Manufacturing

Pharmaceutical companies operate under strict regulatory frameworks that place exceptional importance on data integrity, traceability, consistency, and auditability.

PLM data is not simply operational metadata. It directly impacts:

• Product formulation
• Manufacturing execution
• Quality management
• Regulatory compliance
• Batch consistency
• Supply chain continuity
• Product safety

As a result, PLM migration projects require far more than technical data transfer capabilities.

In pharmaceutical manufacturing environments, SAP ECC systems are frequently customized to support:

• Proprietary formulation processes
• Product-specific recipe structures
• Regulatory reporting requirements
• Regional manufacturing variations
• Specialized specification management
• Multi-level BOM logic
• Legacy integration patterns

Over time, these customizations create highly interconnected data ecosystems that differ substantially from standard SAP reference architectures.

This becomes particularly problematic during migration to SAP S/4HANA because:

• Data structures evolve.
• Object relationships change.
• Certain identifiers are regenerated.
• Legacy dependencies cannot always be reused.
• Flat legacy structures must often become hierarchical.
• New compliance and traceability expectations emerge.

Therefore, migration teams face a dual challenge. They must preserve business meaning and traceability, while adapting legacy structures to fit modern SAP S/4HANA architectures. This is where traditional migration approaches begin to fail.

Why “Lift-and-Shift” Migration Strategies Often Fail

One of the most common mistakes in SAP migration programs is treating PLM migration as a straightforward extract-load exercise.

Conventional ETL processes are generally designed to move records, map fields, apply basic transformations, and validate formatting. But pharmaceutical PLM environments require significantly more advanced handling.

In real-world SAP ECC environments:

• Relationships may depend on internally generated IDs.
• Recipe logic may exist across multiple custom tables.
• BOM validity may depend on manufacturing status rules.
• Specifications may reference dynamically created instances.
• Legacy structures may not align with SAP S/4HANA object models.

This means that successful migration requires:

• Dependency-aware orchestration
• Multi-stage transformation pipelines
• Persistent cross-system mapping logic
• Business-rule-driven filtering
• Structural data redesign
• Hierarchical reconstruction

The migration project examined in this article illustrates all of these challenges.

Challenge #1: Migrating SAP Specifications with Cross-Instance Dependencies

One of the most technically demanding parts of the migration involved SAP specification data and Value Assignment Types (VATs).

In the source SAP ECC environment, certain Admin VAT structures contained references to other Value Assignment Instances using internally generated instance identifiers. These identifiers functioned as relationship anchors within the specification model.

At first glance, this may appear manageable. However, the problem emerged during migration to SAP S/4HANA.

In SAP ECC, instance IDs already existed and relationships referenced those existing identifiers. In SAP S/4HANA, new instance IDs were automatically generated during object creation; therefore, original ECC identifiers could not simply be reused or predefined.

This created a critical dependency issue.

If the Admin VAT structures were migrated directly, that would bring about the following issues:

• Their references would point to non-existent or incorrect objects.
• Cross-instance relationships would break.
• Specification integrity would be compromised.

For pharmaceutical manufacturers, this is not a minor technical inconvenience. Broken specification relationships can affect product traceability and manufacturing consistency, as well as regulatory documentation and audit readiness.

Therefore, the migration required a fundamentally different approach.

Designing a Multi-Stage Migration Strategy

Instead of attempting a single-pass migration, the project team implemented a staged migration process designed specifically to resolve cross-instance dependencies.

The migration was divided into three major phases.

Phase #1: Initial data load

The first migration stage focused on:

• Extracting specification data from SAP ECC
• Loading specification structures into SAP S/4HANA
• Excluding Admin VAT structures during the initial load

This allowed SAP S/4HANA to generate its own internal Value Assignment Instance IDs naturally during object creation.

At this stage:

• Core specification objects were created successfully.
• New S/4HANA identifiers became available.
• Cross-reference relationships were intentionally postponed.

This sequencing decision was essential. Attempting to migrate dependent relationships too early would have introduced invalid references into the target environment.

Phase #2: Cross-reference mapping

After the initial load completed, the next challenge involved reconstructing the relationship model between the original SAP ECC instance identifiers and newly generated SAP S/4HANA instance identifiers.

This required:

• Large-scale extraction of generated S/4HANA IDs
• Complex joins between source and target structures
• Custom mapping logic based on business rules
• High-volume relationship processing involving more than 600,000 rows

The migration process leveraged advanced transformation logic to:

• Match ECC source keys
• Align them with new S/4HANA identifiers
• Preserve original business relationships
• Maintain specification consistency

This stage was particularly important because it effectively rebuilt the dependency architecture inside the target system.

Phase #3: Final enrichment and relationship restoration

Once the mappings were fully established, the final migration stage focused on restoring the dependent Admin VAT structures.

Using the newly generated SAP S/4HANA identifiers:

• Admin VAT data was loaded.
• Correct references were inserted into required positions.
• Specification integrity was preserved.

This secondary load ensured that all interdependent specification structures functioned correctly within the SAP S/4HANA environment.

The approach demonstrated an important lesson for SAP PLM migration programs: complex dependencies often require migration sequencing strategies, rather than direct one-pass loading.

Persistent Cross-System Mapping: A Critical Capability

Another important requirement involved maintaining persistent mapping relationships between the original ECC Value Assignment Instance IDs and newly generated SAP S/4HANA instance IDs. This was necessary for long-term traceability, auditability, and controlled downstream integrations.

The solution was to create persistent mappings within the SAP ESTALE table. The process involved:

• Using Migravion’s Join Tables plugin to perform joins between ECC source instance IDs and newly generated S/4HANA instance IDs.
• Implementing a custom function module to handle controlled and consistent data insertion into the target table.
• Loading the final mapping data into ESTALE using Migravion and a custom function module.

The solution delivered several important advantages:

• Improved traceability between SAP ECC and S/4HANA specification structures, which is especially critical in pharmaceutical environments where auditability and lineage visibility directly impact compliance readiness.
• Reusable mapping logic for subsequent migration and enrichment stages, allowing the project team to avoid rebuilding relationships during later transformation cycles and reducing overall migration complexity.
• Reduced risk of broken specification references and invalid dependencies, which helped maintain the integrity of interconnected specification structures after migration into SAP S/4HANA.
• Scalable processing for high-volume relationship mapping scenarios involving more than 600,000 rows, demonstrating that complex dependency-aware migration can still be executed efficiently at enterprise scale.

Challenge #2: Migrating Legacy Recipe Structures

Recipe migration introduced another layer of complexity, because one category of recipes in the SAP ECC environment was stored in flat custom tables rather than in the hierarchical structure required by SAP S/4HANA Recipe Development.

In addition, specification information related to these recipes was maintained separately in another flat table containing only identifiers, creating fragmented dependencies across multiple ECC tables.

As a result, the migration dataset could not be transferred directly into SAP S/4HANA.

The project team faced two interconnected challenges:

• Reconstructing the logical relationships between recipes and specifications from fragmented ECC structures
• Converting flat legacy data into the hierarchical structure required by SAP S/4HANA Recipe Development

This complexity is common in long-running pharmaceutical SAP environments where years of customization often produce data models that no longer align with modern SAP S/4HANA architectures.

Before migration could begin, the recipe structures first had to be reconstructed and semantically reorganized into a format compatible with the target environment.

Reconstructing Recipe Relationships Across Multiple Tables

The first stage of the recipe migration focused on rebuilding the logical relationships between fragmented recipe and specification data stored across multiple SAP ECC tables.

Because the source data existed in flat structures, the migration team first had to reconstruct the complete business context before the dataset could be transformed into an SAP S/4HANA-compatible format.

This process required complex joins across several ECC tables and involved combining recipe records with specification-related information distributed throughout the legacy environment.

The reconstruction workflow included:

• Joining flat tables using composite keys across multiple fields
• Retrieving RECNROOT values from table ESTRI
• Extracting specification identifiers from table ESTRH
• Combining specification IDs with recipe data to assemble the complete migration dataset

One of the primary challenges involved handling composite-key joins between legacy tables that were not originally designed for direct migration into SAP S/4HANA Recipe Development structures. Rather than working with a single cohesive business object, the migration process had to dynamically rebuild relationships between recipe records, specification identifiers, reference objects, and supporting ECC structures.

This step was critical; SAP S/4HANA Recipe Development requires a significantly more structured and relationship-aware data model than the fragmented flat-table approach used in the legacy environment.

Therefore, the reconstruction phase served as the foundation for the subsequent transformation process by restoring the logical connections necessary to create complete and semantically correct recipe structures for migration.

Transforming Flat Recipe Data into Hierarchical Structures

Once the relationships between recipes and specifications were reconstructed, the next challenge involved converting the flat legacy dataset into the structured format required by SAP S/4HANA Recipe Development.

The source ECC data was not organized as hierarchical business objects. Instead, recipe information existed as flat rows that lacked the structural organization expected by the target SAP S/4HANA environment.

As a result, the migration process required far more than simple field mapping or format conversion. The dataset had to be fundamentally reorganized into a new structural representation capable of supporting SAP S/4HANA Recipe Development requirements.

To achieve this, the transformation process included:

• Converting flat rows into structured hierarchical records.
• Applying row multiplication logic to generate the required target structures.
• Restructuring datasets to align with SAP S/4HANA Recipe Development load requirements.
• Building transformation workflows using Migravion’s Transformation Plugin.
• Leveraging Migravion’s Python-based transformation logic to handle advanced restructuring scenarios.

One of the key complexities involved generating multiple interconnected target records from single flat-source entries. This required the migration logic to interpret business relationships and dynamically construct the hierarchical structures expected by SAP S/4HANA.

Thus, the transformation stage became a critical bridge between legacy ECC flat-table architectures and modern SAP S/4HANA Recipe Development structures.

This scenario reflects a broader pattern frequently encountered in pharmaceutical SAP modernization projects: legacy environments often contain business-critical data models that evolved over many years of customization and operational adaptation, but no longer align with contemporary SAP architectures. In such cases, successful migration depends not only on transferring data, but also on redesigning how that data is structured, interpreted, and connected within the target environment.

By transforming fragmented flat records into semantically organized hierarchical objects, the migration process ensured that the resulting recipe structures were fully compatible with SAP S/4HANA, while preserving the underlying business logic embedded in the original ECC data model.

Why Structural Transformation Matters More Than Data Transfer

One of the most common misconceptions in SAP migration projects is the assumption that moving data from SAP ECC to SAP S/4HANA is primarily a technical transfer exercise.

In reality, pharmaceutical PLM migration projects are often transformation initiatives disguised as migration programs.

Legacy SAP ECC environments frequently contain:

• Flat custom tables
• Fragmented business relationships
• Embedded operational logic
• Cross-object dependencies
• Structures shaped by years of process adaptation and customization

While these architectures may function effectively within the legacy landscape, they are often incompatible with the more structured and relationship-aware data models used in SAP S/4HANA. As a result, simply extracting and loading records into the target environment rarely produces usable business data.

Instead, successful migration requires the ability to:

• Reconstruct business relationships from fragmented source structures.
• Reinterpret legacy data models within the context of SAP S/4HANA.
• Transform flat datasets into hierarchical business objects.
• Preserve semantic meaning and operational logic during restructuring.
• Maintain traceability across interconnected PLM structures.

The recipe migration scenario described above illustrates this challenge particularly well.

Before the data could be loaded into SAP S/4HANA, the migration process first had to:

• Rebuild relationships between recipes and specifications
• Reconstruct logical business objects from fragmented ECC tables
• Generate structured hierarchical records from flat datasets
• Align the resulting structures with SAP S/4HANA Recipe Development requirements

In other words, the project required the creation of a new structural representation of the data rather than a direct replication of the legacy model.

This distinction is especially important in pharmaceutical manufacturing environments, where PLM data directly supports product formulation and manufacturing execution, as well as quality management and regulatory compliance. Therefore, structural inconsistencies introduced during migration can have downstream operational and compliance implications, far beyond the migration project itself.

For this reason, modern SAP PLM migration programs increasingly depend on transformation-aware migration approaches capable of handling:

• Complex dependency orchestration
• Multi-stage restructuring workflows
• Business-rule-driven transformations
• Hierarchical data generation
• Large-scale semantic data alignment

Organizations that treat migration as a data transformation initiative rather than a simple transfer exercise are typically far better positioned to achieve long-term data quality, governance, and operational stability within SAP S/4HANA.

Challenge #3: Creating Consolidated “Golden” BOM Structures

eBOM migration introduced yet another layer of complexity because the legacy SAP ECC environment contained multiple BOM alternatives distributed across different production scenarios, material types, and validity periods.

Over time, the BOM landscape had evolved into a highly fragmented structure shaped by:

• Alternative production versions
• Material-specific variations
• Status-dependent records
• Overlapping validity dates
• Plant-specific configurations
• Duplicate component assignments

As a result, the migration dataset contained numerous BOM structures that were technically valid within the legacy environment, but no longer aligned with the organization’s target-state SAP S/4HANA data model.

Migrating all historical alternatives directly into SAP S/4HANA would have introduced:

• Duplicate BOM structures
• Inconsistent production definitions
• Redundant component records
• Increased governance complexity
• Higher long-term maintenance overhead

The project team therefore faced two interconnected challenges:

• Identifying which BOM records should remain valid within the future SAP S/4HANA environment
• Consolidating fragmented and overlapping alternatives into unified “golden” BOM structures

This complexity was further increased by the fact that BOM validity depended on the BOM records themselves, as well as related manufacturing context, including production recipes, material attributes, classification data, operational statuses, and validity periods distributed across multiple SAP tables.

As a result, the migration process could not rely on simple table extraction and loading logic. Before migration could begin, the BOM structures first had to be validated, filtered, enriched, deduplicated, and semantically consolidated into a cleaner and more governable target-state structure compatible with SAP S/4HANA.

Building a Multi-Step BOM Transformation Pipeline

To transform fragmented legacy BOM structures into consolidated “golden” records suitable for SAP S/4HANA, the migration team implemented a multi-stage transformation pipeline designed to validate, enrich, filter, and consolidate BOM data across multiple interconnected SAP objects.

Rather than relying on direct table migration, the process combined business-rule-driven validation with complex cross-table transformation logic to ensure that only consistent and production-relevant BOM structures were migrated into the target environment.

The transformation workflow included several major stages:

• Initial data extraction and filtering: The migration process began with extraction and filtering across core SAP tables (e.g., MKAL, PLKO, MARA, and MAST) to establish the manufacturing context required for downstream validation and BOM consolidation.
• Business-driven validation: BOM alternatives were evaluated based on production relevance, operational statuses, validity periods, and material attributes to ensure that only active and manufacturing-relevant structures were selected for migration into SAP S/4HANA.
• Complex cross-table joins: Migravion’s Python-based transformation plugin was used to connect BOM, recipe, material, and classification data distributed across multiple SAP tables, enabling the migration process to reconstruct complete production relationships before consolidation.
• Detailed BOM extraction: BOM header and item-level data was retrieved from STKO and STPO to preserve the full structure of each relevant BOM before transformation and deduplication.
• Data enrichment: Material and classification data was added to provide the manufacturing context needed to distinguish between overlapping BOM alternatives and to support accurate consolidation decisions.
• Transformation and deduplication: BOM items were transformed, duplicate components across alternatives were removed, and validity dates were harmonized to create consolidated “golden” BOM records.
• Final data load: Consolidated BOM structures were loaded into SAP S/4HANA after validation, enrichment, restructuring, and deduplication were completed.

This approach demonstrates how complex SAP S/4HANA migration projects require transformation pipelines that combine technical migration logic with manufacturing-specific business rules.

In pharmaceutical environments especially, successful BOM migration depends on transferring records between systems, as well as validating operational relevance, preserving manufacturing consistency, and reducing legacy structural complexity, before the data reaches the target SAP S/4HANA landscape.

Common SAP PLM Migration Pitfalls in Pharmaceutical Manufacturing

SAP PLM migration projects in pharmaceutical manufacturing often become significantly more complex than initially expected; legacy SAP ECC environments typically contain years of accumulated customizations, fragmented business logic, and deeply interconnected data structures.

Many migration challenges do not emerge at the extraction stage, but later during transformation, validation, and target-state alignment, when organizations discover that legacy data models no longer fit SAP S/4HANA structures and governance requirements.

Some of the most common pitfalls include:

• Underestimating ECC customizations: Long-running pharmaceutical SAP environments often contain custom tables, embedded transformation logic, and non-standard relationships that are not immediately visible during initial migration assessments.
• Treating PLM migration as simple ETL: Conventional extraction and loading approaches rarely account for semantic restructuring, dependency orchestration, hierarchical transformation, and business-rule-driven validation required for SAP S/4HANA PLM migration.
• Ignoring cross-object dependencies: Specifications, recipes, BOMs, classifications, and document records are frequently interconnected across multiple SAP objects, making isolated table-by-table migration approaches highly risky.
• Migrating obsolete or redundant structures: Legacy ECC systems often contain outdated BOM alternatives, inactive recipes, duplicate components, and historical records that increase complexity and reduce data quality if transferred directly into SAP S/4HANA.
• Failing to preserve traceability: Pharmaceutical manufacturing environments require clear lineage visibility and relationship traceability to support compliance, auditability, and downstream operational consistency after migration.
• Overlooking structural incompatibilities between ECC and SAP S/4HANA: Flat legacy tables and heavily customized ECC data models often require significant restructuring before they can function correctly within modern SAP S/4HANA architectures.
• Underestimating business-rule complexity: In many PLM migration scenarios, determining whether a record is valid for migration depends on production relevance, material attributes, statuses, classifications, recipe relationships, and validity periods distributed across multiple SAP objects.
• Postponing data consolidation until after go-live: Migrating fragmented or duplicate structures into SAP S/4HANA without prior harmonization frequently shifts complexity into the target environment and increases long-term governance and maintenance overhead.

Organizations that recognize these risks early are typically better positioned to design migration strategies focused on technical data transfer, as well as structural transformation, relationship preservation, and long-term data quality within SAP S/4HANA.

What Successful SAP PLM Migration Requires

One of the most important lessons from complex SAP ECC to SAP S/4HANA PLM migration projects is that technical migration success does not automatically translate into operational success. A project may successfully load millions of records into SAP S/4HANA and still leave the organization with fragmented PLM structures, poor data usability, increased governance and maintenance overhead, and ongoing manual remediation effort.

For pharmaceutical manufacturers, where PLM data directly supports regulated production processes, this distinction becomes especially important.

Successful migration requires a broader transformation strategy focused on system conversion, as well as improving the quality, consistency, and maintainability of the future-state PLM environment.

In practice, this means migration initiatives must address several interconnected dimensions simultaneously:

• Data quality and harmonization: Legacy SAP ECC environments often contain years of accumulated inconsistencies, duplicate structures, overlapping alternatives, and outdated records that should be rationalized before reaching SAP S/4HANA.
• Transformation flexibility: Migration projects frequently require custom restructuring logic, staged processing, and object-specific handling that cannot be fully addressed through standardized migration templates.
• Scalability of transformation workflows: Pharmaceutical PLM landscapes may contain thousands of interconnected specifications, recipes, BOMs, and document records that require coordinated processing across multiple migration stages.
• Preservation of operational context: Migration processes must maintain the business meaning of interconnected PLM structures so that the resulting SAP S/4HANA environment supports downstream manufacturing, quality, and compliance processes without disruption.
• Future-state maintainability: The target environment should not simply replicate legacy ECC complexity, but instead provide cleaner and more governable structures aligned with long-term SAP S/4HANA operating models.

This is where transformation-oriented platforms like Migravion can provide substantial value. By supporting flexible orchestration, custom transformation logic, SAP-aware processing, and large-scale restructuring workflows, Migravion enables organizations to address the technical mechanics of migration, as well as structural and governance challenges that frequently emerge during SAP modernization initiatives.

In projects involving highly customized pharmaceutical PLM environments, this approach can significantly improve:

• Consistency across interconnected datasets
• Readiness for governance and compliance initiatives
• Long-term maintainability of PLM structures
• Usability of migrated business objects within SAP S/4HANA
• Reduction of post-go-live remediation effort

Ultimately, organizations that treat SAP PLM migration as an opportunity to modernize and harmonize their data landscape — rather than simply transfer legacy structures into a new system — are typically far better positioned to realize the long-term operational benefits of SAP S/4HANA.

Conclusion

SAP ECC to SAP S/4HANA PLM migration in pharmaceutical manufacturing is far more than a technical data transfer exercise. Complex relationships between specifications, recipes, BOMs, classifications, and document records require transformation-aware migration strategies capable of preserving business logic, ensuring traceability, and aligning legacy structures with modern SAP S/4HANA architectures.

As this project demonstrates, successful migration depends on a combination of:

• SAP-specific domain expertise
• Flexible orchestration workflows
• Business-rule-driven transformation logic
• Strong focus on data quality and governance

For pharmaceutical organizations, these capabilities are essential for successful system conversion, as well as for improving long-term maintainability, compliance readiness, and operational stability within SAP S/4HANA.

Migravion helps organizations address these challenges by enabling complex SAP transformation workflows, dependency-aware migration orchestration, and large-scale restructuring of highly customized PLM landscapes.

Planning an SAP ECC to SAP S/4HANA migration? Contact the Migravion team to discuss how to simplify complex PLM transformation scenarios and modernize your SAP data landscape with confidence.