EN

ERP transformation, until day one on the new system is business as usual.

We manage ERP transformations on your side of the table, independent of any vendor: SAP S/4HANA migrations and other ERP projects. We bring clear decision papers to your steering committee and hands-on experience in purchasing, warehousing, materials planning, and data migration to the project. Based in Illertissen near Ulm, working throughout Germany.

  • SAP S/4HANA implementation led through go-live, with around 70,000 fixed assets and 7,000 material masters migrated
  • Interim overall project leadership, reporting to the executive board, CIO, and CFO
  • More than 15 years in supply chain and logistics; SAFe® 6.0 SPC and PRINCE2® Practitioner
Migration path from legacy systems to SAP S/4HANA Data from SAP ECC, Microsoft Dynamics, and standalone solutions passes four checkpoints (cleansing, test migration, reconciliation, and cutover) into the target system, SAP S/4HANA. SAP ECC 6.0MicrosoftDynamicsStandalonesolutions

SAP ECC 6.0: Suppliers and customers, materials, purchasing info records, stock, open purchase orders, and fixed assets.

Microsoft Dynamics: Master data and open items as an export, mapped field by field to SAP S/4HANA.

Standalone solutions: Excel lists and specialist applications. Inconsistent data is cleansed before the first test migration.

  1. Cleanse data
  2. Test migration
  3. Reconcile quantities and values
  4. Cutover

Go-live: stock, open purchase orders, and fixed assets are in the target system.

Tools and modules we also work with hands-on in your project, on request.

  • SAP S/4HANA Migration Cockpit
  • LSMW and BAPIs for legacy ECC systems
  • MM, FI-AA, PS
  • Warehouse Management (WM)
  • Materials planning (MRP)

The software is rarely the problem.

In ERP migrations, projects stall on data nobody has checked, on rules only the business knows, and on a cutover weekend without a runbook.

Data quality only shows up in the test migration.

Duplicate suppliers, missing purchasing info records, assets in the wrong class: what worked in the legacy system for years breaks during migration. Cleanup that starts only in the third test migration (mock migration) pushes back the go-live.

Business teams are brought in too late.

Materials planning, purchasing, and the warehouse run on rules that are not written down anywhere. If the new system lacks them, you notice on the first Monday after cutover: at the loading dock and in the MRP list.

The cutover is improvised.

On the cutover weekend, inventory, open purchase orders, and asset values move to the new system. That requires a cutover runbook with owners, time windows, and abort criteria.

Every month of delay has a cost.

The project team stays tied up, and day-to-day business runs short of key users. If you still need fixes for SAP ECC after 2027, you pay a premium for extended maintenance.

We start with the causes: the data, the rules of the business, and the weekend when you switch over.

Services

Where does your project stand?

SAP S/4HANA transformation

When the end of SAP ECC maintenance is getting closer and the path is still open.

Brownfield, greenfield, or selective data transition: we recommend the path based on your data and your processes. Then we lead the project through to stable operations, independent of any software vendor.

  • Readiness assessment of system landscape, data, and processes
  • Decision paper on the transition path
  • Project leadership until handover to operations

Interim project management

When a project needs leadership and no one in-house is available.

Interim program and project management for SAP S/4HANA, Microsoft Dynamics, and other ERP systems. Full-time if needed, and for only one client at a time. We lead until your own team is ready to take over again.

Supply chain planning and inventory optimization

When inventory ties up capital and materials are still missing.

Safety stocks, lot sizes, and MRP procedures based on the availability you need, and demand forecasts with measurable accuracy, including for spare parts. Plus materials planning concepts for a central warehouse that supplies several plants.

Data migration

When test migrations fail or inventory does not match after go-live.

Mapping, cleansing rules, and test migrations with the SAP S/4HANA Migration Cockpit, and with LSMW and BAPIs in legacy ECC systems. After every run, we reconcile quantities and values. If something has already gone wrong, we manage the correction of master data and assets on request.

You can engage us for each service on its own. Usually they interlock, because a migration without clean processes fails just like a process without clean data.

How each engagement starts

From legacy system to stable operations, with a decision at every phase.

Each phase ends with a documented result and a decision on whether and how to proceed.

Cutover timeline
  1. T–6 wks Dress rehearsal The full runbook is run once, with real data volumes and measured run times.
  2. T–2 wks Master data freeze Material, supplier, and customer master records change only with approval.
  3. Friday Close legacy system Complete open transactions, post stock, lock the legacy system for postings.
  4. Saturday Migration Objects are migrated in a fixed sequence, from business partners to fixed assets.
  5. Sunday Reconciliation Check quantities and values against the legacy system; reconcile asset values with accounting.
  6. Sunday evening Go/no-go Decision based on criteria agreed in advance. The fallback plan is ready.
  7. Monday Go-live First working day in the new system, with hypercare and daily reconciliation.

Agile where it helps. Plan-driven where it has to be.

We work with SAFe® 6.0 and PRINCE2® and combine both: iterative in design and testing, with fixed milestones for migration and cutover. A cutover weekend is not a sprint.

  1. Assessment and readiness

    System landscape, data, processes, and interfaces. Result: a well-founded decision on the transition path and a realistic timeline.

  2. Target processes and data strategy

    Together with the business: target processes, migration objects, cleansing rules, and owners for each data area.

  3. Test migrations

    Full runs with reconciliation of quantities and values, until the migration runs the same way every time.

  4. Cutover and go-live

    A cutover runbook with owners, time windows, checkpoints, and abort criteria. The cutover weekend follows the runbook.

  5. Hypercare and handover

    Support through the first weeks of operations, quick fixes, and an orderly handover to your team.

Our approach and method in detail

From our project work

From overall project leadership reporting to the executive board to materials planning for a central warehouse that supplies several plants.

Large enterprise, logistics

Warehouse consolidation and materials planning

We are reviewing MRP procedures and developing materials planning concepts for a central warehouse that supplies several plants. We also define the requirements for the interface to a logistics service provider's system.

Our role: Consulting and project management, ongoing engagement

Martin Hörnig, Managing Director of Bayard Unternehmensberatung

Martin Hörnig

Managing Director, ERP transformation and interim project management

Leads ERP projects and has taken implementations through go-live, most recently with SAP S/4HANA. Previously held leadership roles in supply chain and logistics at large corporations, up to division level. Has designed and implemented materials planning (MRP) procedures.

Your point of contact stays the same from the initial call to handover. For larger projects, we bring additional specialists onto our team, in agreement with you before the project starts.

  • Certified SAFe® 6.0 Practice Consultant (SPC)
  • PRINCE2® Practitioner
  • German (native), English (business fluent)
  • Available throughout Germany, including as interim project manager

Insights from our projects

Deadlines, tool choice, and cutover planning explained, with tables and checklists you can use in your own project.

All articles

Frequently asked questions

We already have an implementation partner. What do you add?

We sit on your side of the table. We review designs and tests, keep schedule and budget in view, and prepare the decisions for your steering committee.

Because we are not tied to any vendor and do not sell licenses, our recommendations stay independent.

When do we need to be off SAP ECC?

For SAP ERP 6.0 (ECC) on enhancement package 6 or higher, mainstream maintenance ends on December 31, 2027. For older enhancement packages, it ended at the end of 2025.

SAP offers extended maintenance until the end of 2030 for an additional fee. Without it, customer-specific maintenance applies: no new fixes and no new legal changes.

Depending on scope, a migration takes one to two years from project start to go-live, plus the decision and partner selection. If you have not decided on a path yet, start the readiness assessment now. SAP ECC end of maintenance: the deadlines

Brownfield or greenfield: which is right for us?

Brownfield converts your existing system, with its configuration and history, and is usually faster. Greenfield starts from scratch and pays off when your current processes no longer work anyway. Selective data transition sits in between.

The readiness assessment shows which option fits, based on your data and processes. The three paths to S/4HANA compared

Consulting or interim project management: what's the difference?

In a consulting role, we provide your project team with analysis and concepts and support it in critical phases. In interim project management, we lead the project ourselves, for a set period and with a clear handover goal. The two can be combined.

How do we keep the project knowledge in-house?

Decisions, plans, and the cutover runbook are documented and stay with you, and your internal project manager is involved from the start.

Do you also work with Microsoft Dynamics?

Yes. In Microsoft Dynamics projects, we take on project leadership, including interim project management, and data migration. Cleansing, test migrations, reconciliation, and cutover follow the same rules in every ERP system.

Do you work on site or remotely?

Both, throughout Germany. Workshops, the dress rehearsal, cutover, and the first days after go-live should take place on site. In the Ulm, Neu-Ulm, Illertissen, Memmingen, and Günzburg area, we are especially close by. ERP consulting in the Ulm region

What does working with you cost?

That depends on scope and role. A well-defined readiness assessment is a different matter from months of interim project management. After the initial call, you receive a proposal with a clearly described scope.

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

What can we help with?

We process your details only to handle your inquiry (Art. 6(1)(b) and (f) GDPR). Retention period and your rights: Privacy policy.

We usually reply within two business days.

Initial call Call