SAP Basis Consulting: Lean back while we look after your SAP landscape.
We manage the Basis side of your SAP systems for you, from installation and maintenance to upgrades and S/4HANA transformation.
Live preview
SAP Basis ConsultingIn short
SAP Basis consulting is the management of the technical foundation of SAP systems: installation, database, system copies, transport management, upgrades, performance and system security. At CoreTechs we take over the Basis work for your SAP landscape from installation to day-to-day maintenance, plan and execute the technical side of your S/4HANA migration, and keep your systems stable with 24/7 support. We do not provide functional module consulting (such as FI, MM or SD); our responsibility is the technical layer those modules run on.
Scope
Scope
- SAP system architecture
- Installation and maintenance
- System copies and migrations
- Version upgrades
- S/4HANA transformation projects
- Performance monitoring and 24/7 support
Deliverables
- Stable SAP environment
- Transformation roadmap
- Regular health check reports
Who is it for?
- Companies running SAP ECC that are planning an S/4HANA migration and want clarity on which migration path fits them
- Organizations with no in-house Basis expert, or at risk because they depend on a single one
- Companies that want to move SAP systems from their own data center to the cloud or other infrastructure
- Teams facing performance issues from slow SAP systems, a growing database and ever-longer batch jobs
- SAP teams that want system copies, transports and patching run through a regular, documented process
How we work
Technical assessment
We review your system landscape (development, quality and production), versions, database, interfaces, custom developments (Z code) and current operating processes. Risks and recommendations are shared in a written health check report.
Target architecture and roadmap
For an upgrade, infrastructure move or S/4HANA migration, we define the target architecture, sizing, migration path and phases. In S/4HANA projects we review readiness check results together with your functional team and business units.
Trial conversions
Before touching production, we run one or more trial conversions on a copy of the production system. Each run records duration, errors encountered and incompatibilities in custom code.
Production cutover
Using a detailed cutover plan built from the trial runs, we carry out the production migration within the downtime window you set. Fallback points and checkpoints are defined in advance.
Hypercare and ongoing Basis service
After go-live, a period of intensive monitoring stabilizes the system. Basis operations then continue with patch management, transports, user and authorization infrastructure, system copies, performance monitoring and regular health checks.
How long does it take?
The main factors that shape the duration of SAP Basis projects are the number of systems, database size, the chosen S/4HANA migration path, the amount of custom code, the number of interfaces and the downtime window the business can accept. After a free 30-minute initial call, we usually start discovery within a week; at the end of the technical assessment we provide the phases and a firm quote in writing. Ongoing Basis support runs under our SLA-based maintenance and support model.
Phases
- Preparation and assessmentReadiness check, custom code analysis, sizing and the migration path decision.
- Infrastructure preparationTarget servers or cloud environment, SAP HANA database and required components are installed.
- Trial conversionsThe migration is rehearsed on a copy of production; duration and issues are measured and the plan is refined.
- Production cutoverThe migration is performed in a planned downtime window and validation tests are completed with business users.
- Hypercare and operationsIntensive post-go-live support, followed by regular Basis operations and health checks.
What drives the cost?
The cost of SAP Basis consulting and an S/4HANA migration depends on the size of your systems and the chosen approach. We share a budget range in the initial call and a firm quote after the technical assessment. SAP license and subscription fees and infrastructure costs are separate from our service fee.
| Factor | Effect on cost |
|---|---|
| Migration path | Converting the existing system (brownfield), starting fresh (greenfield) or a selective data transition each carry a different effort and risk profile. |
| Database size | Large databases mean longer conversion runtimes, more trial runs and possibly archiving or data cleanup. |
| System landscape | Training, additional quality or satellite systems beyond development, quality and production multiply the work. |
| Amount of custom code | Fixing Z code that is incompatible with S/4HANA requires developer effort and affects the number of trial runs. |
| Interfaces and integrations | Every external system connected to SAP needs testing and possibly adjustment after migration. |
| Downtime window | A very short downtime target requires additional downtime-minimizing techniques and more trial conversions. |
| Support level | The difference between business-hours support and 24/7 Basis support sets the ongoing service fee. |
Technology options
SAP platforms
- SAP S/4HANA
- SAP ECC
- SAP NetWeaver (ABAP and Java)
- SAP Fiori front-end server
Databases
- SAP HANA
- Oracle Database
- Microsoft SQL Server
- SAP ASE
- IBM Db2
Migration and upgrade tools
- SAP Readiness Check
- Software Update Manager (SUM)
- Database Migration Option (DMO)
- Software Provisioning Manager (SWPM)
Operations and monitoring
- SAP Solution Manager
- SAP Cloud ALM
- Transport management (STMS)
Infrastructure
- SUSE Linux Enterprise Server for SAP
- Red Hat Enterprise Linux for SAP
- AWS
- Microsoft Azure
- Google Cloud
- On-premises virtualization
Example solution scenario
Technical migration from ECC to S/4HANA
Representative scenario, not a real client project.
- Profile
- A manufacturing company running SAP ECC on on-premises servers, with a large amount of custom code and several interfaces to external systems.
- Need
- The company knew it had to move to S/4HANA but could not decide between converting the existing system and starting fresh. It had a single in-house Basis expert, a large database, and production could not afford a long outage.
- Approach
- A readiness check and custom code analysis listed incompatible developments and business process impacts.
- Migration paths were compared with the functional team and business units; a system conversion that largely preserves existing processes was chosen.
- Data archiving reduced the database size, and the target SAP HANA environment was sized and installed.
- Several trial conversions on copies of production clarified runtime and errors.
- The production cutover took place over a planned weekend window, followed by hypercare and ongoing Basis support.
- Technologies
- SAP S/4HANA
- SAP HANA
- SAP Readiness Check
- SUM with DMO
- SUSE Linux Enterprise Server for SAP
- Outcome
- The migration was completed in line with the plan measured during trial conversions and within the agreed downtime window. Basis operations no longer depend on one person, all procedures are documented and the system is now monitored through regular health checks.
Frequently asked questions
What is the difference between greenfield, brownfield and RISE with SAP in an S/4HANA migration?
Greenfield means implementing S/4HANA from scratch, redesigning processes and moving only the data you need. Brownfield means converting your existing ECC system, including its data and custom code, to S/4HANA; selective data transition approaches sit between the two. RISE with SAP is not a migration path but a contract model in which SAP offers S/4HANA as a subscription bundled with cloud infrastructure and services, and it is combined with either a greenfield or brownfield approach.
Which migration path is right for us?
That depends on how satisfied you are with your current processes, how much custom code you have, whether you need to keep historical data and your budget. We review the readiness check and custom code analysis with your functional team and give you a reasoned recommendation.
How long will the system be down during an S/4HANA migration?
Downtime depends on database size, infrastructure and the techniques used. Rather than estimating, we measure it in trial conversions on a copy of production and plan the cutover to fit the window you set.
How is SAP Basis consulting different from functional SAP consulting?
Basis covers SAP's technical foundation: installation, database, upgrades, transports, performance and system security. Functional consulting configures business processes in modules such as FI, MM and SD. We take care of Basis and coordinate with your functional team or existing partner.
Can you work alongside our current SAP partner?
Yes. If you work with a partner for licensing, functional consulting or application support, we run Basis with them under a clearly defined split of responsibilities. The division of tasks is agreed in writing at the start of the project.
Can you move our SAP systems to the cloud?
Yes. We migrate SAP systems to AWS, Microsoft Azure or Google Cloud, covering sizing, the instance types the provider supports for SAP and a downtime plan. The move can be part of the S/4HANA project or a separate phase.
What does 24/7 Basis support include?
Scope is defined in the SLA and typically covers system monitoring, response to critical incidents, applying patches and security notes, transports and system copies, and regular health check reports. Response times are agreed with you based on how critical each system is.
Last updated:
Cloud, Infrastructure and Security
Other solutions in this area
Get a quote for this solution
Tell us briefly what you need and we will get back to you within one business day. The first 30-minute introductory call is free.