1. Home
  2. Services
  3. SAP implementation

SAP implementation: SAP Activate's six phases and SAP's dates for ECC

An SAP implementation takes your company from a signed SAP contract to daily work in SAP. SAP's own method, SAP Activate, splits the work into six phases: Discover, Prepare, Explore, Realize, Deploy and Run. Our team has taken SAP Business One, S/4HANA and ECC live, and we can run an SAP implementation end to end.

Checked 19 November 2026

SAP Activate splits an implementation into six phases

SAP’s implementation method is called SAP Activate. SAP Learning says it fits every SAP deployment option: cloud, on-premise and private cloud. It has six phases. SAP calls the middle four, from Prepare to Deploy, the four core phases. Discover comes before them, and Run comes after go-live.

Scroll the table sideways to see every column.

Phase What happens, in SAP’s words What you decide
Discover A non-committal phase to research SAP’s products. For a system conversion, the old ERP’s readiness to convert is checked too Which SAP product, and which path to it
Prepare Scope, project governance, the sandbox or starter system, the team’s roles and the project plans Who sits on the project, and the scope
Explore Fit-to-standard workshops show SAP’s standard processes, and the gaps go into a backlog Which gaps are worth closing
Realize All build and test work for a release, ending in a full integration test and a user acceptance test When the build is ready to ship
Deploy Production is set up, readiness to switch is confirmed, and hypercare follows go-live The cut-over weekend
Run Support and management of the live system. SAP keeps 16 standards for it, from incident management to upgrades Who looks after SAP once it is live

The first two columns come from SAP Learning. The third column is our own reading of where a buyer’s decisions fall.

SAP backs each phase with ready content. Its Best Practices give a project a baseline configuration, and its ready-to-run systems give it a prototype. The ready-to-use content sits in the SAP Activate Roadmap Viewer. SAP Learning’s course on the method runs 9 hours 25 minutes across 7 units, so plan time for your project team to learn it.

First pick one of SAP’s three paths to S/4HANA

If you run ECC today, the path shapes the project more than the phases do. SAP’s course names three ways to reach S/4HANA.

  • New implementation, also called greenfield. You set up a new S/4HANA, moving from a non-SAP system or an older SAP solution. SAP says you can refine your processes and bring over only the data you need.
  • System conversion. SAP says this turns your SAP ERP into S/4HANA and keeps its business data, custom development and configuration. SAP also says a customer on this path will likely buy new hardware, because the database runs in memory. SAP adds that other options exist.
  • Selective data transition. A tailored scope between the other two. You pick the data and settings to carry over, through SAP’s LT tool.

Lift and shift is a different move. SAP’s example takes a system that already runs S/4HANA, on-premise 2020, to Private Edition 2020 without change.

Selective data transition comes in two forms. A shell conversion copies production without its master and transaction data, then converts that empty shell. SAP says it suits a project that keeps most of its processes. Mix and match starts from a new S/4HANA install and carries over parts of the old settings and code. SAP says that suits a project that redesigns most of the solution.

There is a deadline on one path. SAP News said in October 2026 that tools to convert Business Suite 7 on a third-party database are there only until the end of 2030. After that, SAP supports only new implementations from those systems. If your ECC runs on a database other than SAP HANA, plan the choice early.

How a system conversion runs, step by step

SAP lists five main steps:

  1. Prepare the old ERP. Clean up custom code and cut the data volume.
  2. Move the database to SAP HANA, if it runs on another database today.
  3. Update the system with new applications and tables.
  4. Convert the table content to the new data model.
  5. Configure the software. Apply the changes S/4HANA requires, and reuse most of your existing processes.

SAP’s Software Update Manager (SUM) runs the database, software and data steps. SAP Readiness Check finds what in ECC must change to work on S/4HANA. It also looks at data volumes, and it rates SAP add-ons and lists third-party ones, each to be checked. The Maintenance Planner works out the upgrade path.

Teams convert a sandbox copy first. SAP says that run can be repeated several times, until the team is happy with the result and ready to plan the development, quality and production systems. During the real conversion, the source database keeps running and its data is not changed, so it stays a fallback until the whole job has finished.

A conversion also means two sets of systems for a while: one for maintenance and one for the project. SAP’s Retrofit tool copies daily fixes into the project side, so the two stay in step.

The edition decides which SAP tools build the system

S/4HANA comes in three main forms. Each one is built with different tools. SAP calls Public Edition a public cloud with set processes for chosen business and industry scenarios. It calls Private Edition standard processes plus the extensibility and reach of on-premise S/4HANA.

Scroll the table sideways to see every column.

Edition Where it runs How it is set up How it is tested
S/4HANA Cloud Public Edition A multi-tenant cloud in SAP data centers SAP Central Business Configuration creates the starter, quality and production systems and sets the scope. SAP also offers a 3-system setup for customers who need a development system SAP’s test automation tool is built in
S/4HANA Cloud Private Edition A private cloud. SAP Learning says it keeps traits of on-premise systems and supports conversions into the cloud SAP Solution Builder deploys SAP Best Practices Customers with SAP Enterprise Support may use Tricentis Test Automation for SAP as a term license
S/4HANA on-premise Hardware you size yourself. SAP names three sizing models, two of them in its Quick Sizer SAP Solution Builder, with Focused Build for sprints, which SAP says has no additional cost Same Tricentis right as above

On Public Edition, the starter system comes with preset business processes and master data. Weekly or bi-weekly transports keep production in step with the quality system.

SAP sells two programs around these editions. SAP GROW is SAP’s entry point to cloud ERP, built on Public Edition and designed for companies new to SAP. RISE with SAP is for existing SAP customers moving off on-premises SAP. SAP calls RISE a guided path from on-premises ECC or S/4HANA to SAP Cloud ERP Private, and it names seven AI migration assistants. One rule shapes the choice: SAP’s Joule guide says Joule comes to Private Edition only within RISE with SAP.

Explore: fit-to-standard workshops come before any build

Explore starts from SAP’s standard. In fit-to-standard workshops, SAP’s Best Practice processes are shown in a sandbox or starter system. Each gap to the standard is then logged as a delta requirement, and the team keeps every item in one product backlog. SAP lists seven activities for these workshops.

Two of SAP’s workshop rules bear on cost. First, SAP says a fit-to-standard approach lowers delivery risk and the total cost of putting SAP in and running it. Second, SAP says any change to standard should be justified by business value.

Realize usually runs in sprints. SAP says it most often uses an agile approach, though that depends on the project. SAP Learning says a sprint lasts two to four weeks, waves generally last one to three months, and a scrum team has 5 to 9 members. A release is everything built up to one go-live, so a large rollout can have several.

SAP Cloud ALM runs the project, and you may already own it

SAP says Cloud ALM is included in SAP cloud subscriptions and on-premise maintenance agreements. SAP’s page adds that it needs no extra hardware or licenses. It splits the work into four areas:

  • Scope. Collect the business processes, solution content and requirements for the project.
  • Migrate. Move data, custom code and configuration from old systems such as ECC.
  • Build. Manage the project, set up and document the system, test it and deploy it.
  • Run. Watch the live system, find problems and fix them.

Cloud ALM now has AI helpers too. Its data management assistant uses agents such as a Transition Data Quality Scope Agent. And if you ran SAP’s Digital Discovery Assessment, its result can be loaded into Cloud ALM as the project scope. For a move to Public Edition, SAP names that assessment, Central Business Configuration and Cloud ALM as the tools.

Clean core keeps custom code out of SAP’s way

SAP says years of custom code led to more effort at each upgrade and more upkeep. Its answer is what it calls a “clean core”. For links to other systems, SAP’s lesson says to use SAP’s standard scenarios from the Business Accelerator Hub, over OData, SOAP or events.

For old custom code, RISE has a Custom Code Assistant. SAP says it reads your custom ABAP code, called Z-code in ECC, and sorts it. Some code can be replaced by standard cloud functions, some needs fixing, and some should be kept. SAP’s Extensibility workstream covers every custom change, from the written spec to the code.

For links between SAP and Salesforce, Databricks or a CRM, see SAP integration.

Data migration: what moves into S/4HANA

The path decides the data. A system conversion keeps your business data in place. In a new implementation, SAP says you may want only the key master data and transaction data from the old system. A move from a non-SAP system, such as QuickBooks, Xero or Sage, is a new implementation in SAP’s terms. In a selective data transition, SAP’s list of what can move has four parts: custom ABAP objects, configuration, master data, and transaction data. That last part can be open items plus a slice of closed history, for example 2 years.

Cloud ALM’s Migrate area handles the data, custom code and configuration. In a conversion, Readiness Check also analyses the data volume in the old system, and SAP’s first step is to cut that volume.

Testing, training and go-live

SAP’s Realize phase ends in two tests: a full integration test and a user acceptance test. On Public Edition, SAP’s test automation tool is part of the product. On private and on-premise systems, the Tricentis right above covers customers with SAP Enterprise Support.

SAP’s Solution Adoption workstream covers value management, change management and end-user training. Deploy then sets up production and confirms that the business is ready to switch. Hypercare follows go-live, and Run takes over from there.

How long an SAP implementation takes

SAP’s pages give no single duration for every project. For Public Edition, SAP says you can go live in weeks with SAP Activate. Larger projects run in waves that SAP says generally last one to three months, each made of sprints.

Scope drives the cost: the edition, the path, the number of companies, how much custom code must be sorted, and how many systems connect to SAP. You pay SAP or its reseller for licenses separately. For what firms publish for ERP projects, read what ERP implementation costs.

SAP’s support dates set the deadline for ECC

SAP sets these dates on its maintenance page and in SAP News. Your own SAP agreement may add terms, so read it too.

Scroll the table sideways to see every column.

System What SAP says
SAP ERP 6.0 (ECC) in Business Suite 7 Mainstream maintenance runs to the end of 2027 for the core applications, including the latest three enhancement packages of SAP ERP 6.0
The same, with extended maintenance An optional three years, from the start of 2028 to the end of 2030
Systems on a third-party database Tools to convert them exist only until the end of 2030. After that, new implementations only
Qualifying customers A time-bound Transition Option supports business continuity from 2031 through 2033, if their systems move to SAP ERP, private edition on SAP HANA before 31 December 2030. SAP aims it at its largest and most complex customers, and further eligibility rules apply
Business Suite 7 customers SAP News, 7 October 2026, in a post for those on third-party databases or Java, says to plan to finish the move to SAP Cloud ERP by the end of 2030
S/4HANA At least one release in maintenance until 2040, as SAP announced on 4 February 2020

So an ECC customer who starts Discover today has a few years, not many, and the conversion tools for third-party databases end with 2030. A conversion needs sandbox runs, and a new implementation needs fit-to-standard workshops, before any go-live date is real.

What our team has done

Our team has taken SAP Business One, S/4HANA and ECC live. We can run an SAP implementation end to end.

Across all ERPs, our team has taken nine live, from SAP to QuickBooks. Across ERPs, our team has also delivered small modules, each built for one business problem. Our team has moved companies off QuickBooks, Xero or Sage into a full ERP.

We sell five services, alone or as one project: consulting and discovery, process mapping, implementation, training, and support after go-live. Training runs on site or remote, as you prefer.

Our team’s data and cloud work covers AWS, Azure, Google Cloud and private servers.

Once SAP runs, AI agents can take jobs such as emailed orders off your team’s desk. See SAP AI agents. For Business One, see SAP Business One consulting. For other ERPs, see ERP implementation services, and for builds our team has finished, see our case studies.

Questions

What is SAP full form?

SAP stands for Systems, Applications, and Products in Data Processing. That is SAP's own answer on its company page. The name started in German: SystemAnalyse Programmentwicklung, which means System Analysis Program Development. SAP's history page says five former IBM employees started the company on 1 April 1972. Today the name covers many products, from SAP Business One for smaller firms to S/4HANA.

What are the four stages of implementation?

In SAP's method they are Prepare, Explore, Realize and Deploy. SAP Learning calls these the four core phases, because project delivery happens between Prepare and Deploy. Two more phases sit on either side. Discover comes first, while you research SAP's products. Run comes last, once the system is live. So an SAP Activate project has six phases in all.

What are the four types of implementation?

For a move to S/4HANA, SAP's course names three transition paths. A new implementation, or greenfield, sets up a fresh S/4HANA. A system conversion turns your SAP ERP into S/4HANA and keeps its data, code and settings. A selective data transition sits between the two. SAP also describes a lift and shift, which moves a system already on S/4HANA to Private Edition without change.

How to implement SAP MM?

MM is SAP's name for materials management, which SAP says covers procurement and inventory. SAP says users have long called these business functions modules, and the short names stay common in job ads and training. In an S/4HANA project, buying and stock sit inside the scope set in Prepare. In Explore, fit-to-standard workshops show SAP's standard processes for them, and your team records each gap. The build and tests follow in Realize.

How long does an SAP S/4HANA implementation take?

It depends on the edition and the path. SAP says Public Edition can go live in weeks with SAP Activate. Bigger projects run in waves. SAP Learning says waves generally last one to three months, and each holds sprints of two to four weeks. A conversion adds sandbox runs before the real one, and SAP says those runs can be repeated several times until the team is satisfied.

Should we convert ECC or start again on S/4HANA?

Convert when you want to keep how you work today. SAP says a conversion keeps your business data, custom code and settings. Start again when you want to refine your processes and bring only the data you need. A selective data transition is the middle way: you pick what moves. Mind the date. SAP says tools to convert Business Suite 7 on a third-party database are there only until the end of 2030.

What does SAP Cloud ALM cost?

SAP says Cloud ALM is included in SAP cloud subscriptions and in on-premise maintenance agreements. Its page adds that you own it already and need no extra hardware or licenses to run it. So if you hold an SAP cloud subscription or an on-premise maintenance agreement, the project tool for scope, data moves, build, tests and monitoring comes with it. Check your own contract for the details.

Do we need an official SAP partner to do this?

Not for this work. What decides a go-live is a team that knows SAP from the inside and builds on SAP's published tools and APIs. Our team has taken SAP Business One, S/4HANA and ECC live. You license SAP from SAP or its reseller, and we take the consulting, setup, data move, training and agent build from there.

Can you implement SAP Business One as well as S/4HANA?

Yes. Our team's SAP go-lives cover Business One, S/4HANA and ECC. SAP says Business One is designed for small and midsize businesses, while S/4HANA Cloud and SAP ERP are for organizations of all sizes. Business One has its own licenses, add-ons, cloud hosts and support dates. So it gets its own page: SAP Business One consulting.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Plan your SAP implementation with us

Bring your SAP edition, the systems you run today and the go-live date you have in mind. The first call is free.

Book an SAP project call