Skip to content

Checklist

Taking over SAP Basis support

Forty-six questions to answer before signing a SAP Basis support contract: starting point, scope, SLAs, monitoring, patching, security, transition and exit terms.

Checklist · 7 pages, 46 questions in 8 areas · Published: October 2026 · English edition; also available in Polish.

Key findings

  1. An SLA only works when it separates response, restoration and resolution times and names who keeps the clock.
  2. With standard maintenance for SAP Solution Manager 7.2 ending in 2027, the contract has to name the monitoring tool and a plan for moving the rules across.
  3. Security monitoring, hardening and periodic penetration testing belong in the same conversation as Basis support, because the Basis team is the one that acts on an alert.

What is inside

  • Starting point
  • Service scope
  • SLAs and incident handling
  • Monitoring and daily operations
  • Patching and SAP Security Patch Day
  • Security
  • Transition period
  • Exit terms

Who it is for

CIOs, SAP team leads and anyone preparing a tender or a change of SAP Basis support provider.

Available on request

Taking over SAP Basis support - checklist

Forty-six questions to answer before signing a SAP Basis support contract: starting point, scope, SLAs, monitoring, patching, security, transition and exit terms.

  • An SLA only works when it separates response, restoration and resolution times and names who keeps the clock.
  • With standard maintenance for SAP Solution Manager 7.2 ending in 2027, the contract has to name the monitoring tool and a plan for moving the rules across.
  • Security monitoring, hardening and periodic penetration testing belong in the same conversation as Basis support, because the Basis team is the one that acts on an alert.

Fields marked with an asterisk are required.

Related services

  • SAP Basis 24/7

    The checklist walks through the whole SAP Basis support transition: scope, SLAs, monitoring, patching and exit terms.

  • SAP Security

    Part 6 covers security in the support contract - hardening, monitoring, privileged access and penetration testing.

  • SAP partnership

    The checklist helps you choose a SAP partner to run SAP Basis and SAP S/4HANA systems.

  • SAP Security Patch Day

    Part 5 covers how the support contract handles SAP Security Patch Day.

  • S/4HANA Conversion

    Parts 2, 5 and 7 cover the split of responsibilities under RISE with SAP and taking over support after the conversion.

  • NIS2 / DORA Audit

    Part 6 covers requirements for ICT service providers in the support contract.

  • SAP Security Review and Pentests

    Part 6 covers the frequency and scope of periodic penetration testing in the support contract.

  • SecurityBridge for SAP

    Part 6 covers SAP security event monitoring and alert response times.

  • Rev-Trac

    Parts 2 and 5 cover change management and approval of production changes.

Companion article

Read the article

Get in touch