IT systems · Practical guide

SAP Business ByDesign: testing GxP data migration

Before uploading a migration file, decide which data the target needs and where the remaining history will be available. A missing target field could be intentionally archived information or an unintended gap. The two require different decisions.

Table of contents

At a glance

How do you test a data migration into SAP Business ByDesign?

Populate SAP Business ByDesign migration templates with source data, upload and validate them in the migration tool, convert source values to permitted target values and import the data. Load dependent objects in the correct order. Link those steps to approved mappings, data relationships and use in the target process. A successful tool step does not replace the organisation’s assessment of its GxP data.

Scope and Applicability

The article concerns initial or supplementary migration into ByDesign. Ongoing interfaces and cloud updates have different test boundaries. Establish the actual objects in scope before assuming one migration template can import every historical object.

Sources: [1]

Migration to business objects and usage planning

Begin with the future use of the data. Which material batches, identified stocks, open activities, and references are required in ByDesign? Which historical records can remain accessible via an appropriate archiving pathway? Separate active transfer from retention. A technical table export does not yet reflect the professional assessment.

The SAP ByDesign help document from February 2026 describes migration templates, file upload with validation, source-to-target value conversion, and import. Certain objects are interdependent and must be loaded in a predefined sequence. Assign your review activities to the following steps: file validation, alignment with the approved mapping, and assessment of the technical impact following import. For requirements deviating from standard templates, SAP specifically identifies the need for dedicated customized templates. Clarify available objects and gaps in support prior to decommissioning the source system.

Capture the dependencies between objects. A stock can require an item, a unit, a warehouse reference, and an identified stock quantity. When identifiers are changed, the reconciliation must maintain a traceable assignment. The selected loading sequence should take these relationships into account and be verified during a pilot run.

Sources: [1] [2]

The Mapping Document as the Professional Basis for Decision-Making

For critical fields, document source, target, significance, transformation, and verification method. A technical field mapping alone is insufficient when the status in the target field has a different impact. Therefore, specify the action derived from the target value and how its correct impact is verified.

When duplicate identifiers are merged or invalid units are corrected, the inventory changes consciously. Such changes need a comprehensible reason and a connection to the source. Uncontrolled manual corrections between export and import can make it difficult to investigate differences later.

Internal Work Aid: The Mapping Document as Business decision Basis
Data areaCritical contentOwn reconciliation
Material master Identification, unit, and relevant parameters Field comparison with approved mapping
Identified stock Product reference, batch number and date information Unique assignment and professional application
Inventory Quantity, location, and acceptable status Quantity comparison plus selected process validation
Open process Processing status and associated objects Controlled continuation in target
Historical Context Previous identification and associated documentation Reconstruction via target or archive pathway

Sources: [1]

Example and inspection table: status meaning following takeover

A batch C-44 is transferred from the legacy system. In the legacy system, status S indicates that material is locked for a specified production use. In the target system, a seemingly equivalent status is assigned. Only a process test demonstrates whether this assignment actually restricts the intended use. An identical status name is insufficient.

Prepare two comparable stocks with released and locked starting conditions. Compare identifier, product reference, quantity, and target status. Then perform the intended authorized or unauthorized business process flow. The expected behavior shall be defined as a separate process requirement; it does not constitute a general statement regarding the behavior of any ByDesign configuration.

If the intended blocking effect fails, distinguish between mapping errors and inappropriate target controls. A correctly loaded status may be technically accurate but may still have the wrong functional effect. Correction may therefore require a different configuration or an additional, justified control pathway. Repeat the relevant data and process reviews following adjustments.

The batch record integrates individual object inspections with the final status. Document the data actively transferred and ensure that required history remains accessible. All open activities and changes following the general inspection must be explicitly linked to this status.

Own work aid: Transfer of object until authorized use
CaseAssessment questionExpected evidence
Released stock Is the defined intended use feasible? Correct batch assignment and a permitted workflow
Blocked stock Does the selected usage limitation apply? Invalid subsequent step is prevented or appropriately controlled
Missing reference Is an incomplete object reference detected? No unexplained technical data record
Repeated transfer Do duplicate or overlapping objects arise? Planned retry remains traceable
Historical Investigation Can C-44 be traced back to the source process? Assignment of identifiers and required context available
Finales Delta Is the subsequent status change included? The reconciliation reflects the final version actually loaded

Sources: [1]

Perform pilot runs and verify final data status

A pilot run should be conducted using a known source inventory and a clearly defined tool configuration. Document the import scope, errors, warnings, and technical discrepancies. Assess whether the dataset is representative enough to support critical transformations. Rare edge cases must not be excluded solely due to low frequency if their potential impact is significant.

Between the pilot run and final acceptance, new batches and status changes may occur. Define a leading source timestamp and establish a process for handling subsequent modifications. A delta comparison should identify the actually modified objects. Simply reusing a previously successful import package does not confirm the final data state.

Plan a controlled shutdown. Who decides on unresolved discrepancies? Which functionalities remain locked? When can the legacy system still operate usefully? A rollback also affects processes established since the transition. The answers must align with the specific project and be available prior to productive cutover.

Sources: [1]

Release, historical data, and handover are linked

A release file combines technical run, professional comparisons, evaluated differences and permitted use. Name excluded data and their access path. A statement such as "Migration complete" should refer to a clearly defined scope. Otherwise, it remains open whether historical change information, attachments or open processes were considered at all.

For storage, a readable export is not automatically sufficient. Verify that the required meaning and context are preserved. If a historical decision can only be justified in conjunction with a method version or an earlier status, that context must remain appropriately accessible. The specific solution may vary depending on the data type.

Provide mapping, attribute assignments, reconciliation reports, and remaining operational tasks. The internal team should be able to trace any subsequently reported discrepancy back to the adopted status. Only in this way can it be determined whether a deviation arises from migration, configuration, or a subsequent change.

Sources: [1]

Next steps

  • Define data scope, historical residuals, and responsible parties.
  • Mapping including definition of missing and invalid values.
  • Perform a test import with critical relationships and exceptions.
  • Combine the final import status and technical alignment for release approval.
Further reading:

Project experience and collaboration

Check mapped values against the subsequent business transaction

Your data owners select a known batch or another critical business object. We compare its source values, approved mapping and migrated target values against the intended use. A standard template may support the technical transfer. If it excludes required objects, we agree how to retain the necessary data before access to the source ends. We include the final change made after the dress rehearsal. A successful Validate step alone does not establish that the migrated data are correct for business use.

Frequently asked questions about ByDesign data migration

Can "Validate" and a successful import be sufficient for GxP compliance proof?

No. Tool validation and successful technical import are only components. Compare the approved mapping, critical contents, relationships, and subsequent usage in the target environment. A technically accepted status may lead to incorrect outcomes in a functional context. Deliberate exclusions and required history must also be properly justified.

Sources: [1] [2]

How do we handle inactive data that is not actively transferred by ByDesign?

Assess the required usage, significance, and retention period. An appropriate archiving or access solution can preserve the necessary context outside the operational system. Document and verify this approach prior to the withdrawal of source access. An unexecutable import does not imply an automatic reduction in retention obligations.

Sources: [1]

Can the mapping be modified after the test?

Yes, controlled. The impacts must be assessed and the affected tests must be repeated. Final import must not be based on an unverified mapping.

Sources: [1] [2]

How do we handle a new source change after the general test?

Capture the final source state and verify the planned delta takeover. A previous successful general sample does not validate a subsequent change. Particularly, status, open activities, and relationships may be affected. The final reconciliation must explain the actual last takeover and its authorized usage.

Can the technical loading sequence be technically relevant?

Yes, if objects are interdependent or target rules are applied during transfer. Verify the actually planned sequence in a suitable pilot run. A test environment with existing references may mask missing dependencies. Identify preconditions and assess the final target state.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. SAP: Business ByDesign Data MigrationSAP Business ByDesign, February 2026: Migration templates, validation, value realization, import, and dependencies. Tool validation must be distinguished from internal subject-matter data review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Ensure professional assurance of the ByDesign migration

With source data, approved mapping, and a known business object, we assess technical transfer, target relevance, and required historical access.

  • SAP S/4HANA validation →

    Support an SAP go-live with evidence your team can defend at audit while keeping validation on schedule. We take a risk-based approach from the template to the interface for greenfield or brownfield projects and existing ECC systems.

Send a project enquiry Customer testimonials →