Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
All guides

Guide · SAP HANA

Migrate On-Premise HANA to HANA Cloud: Steps and Pitfalls

Move an on-premise SAP HANA database to HANA Cloud with the Self-Service Migration tool: prerequisites, compatibility errors, and operations changes.

Matt Angerer
November 14, 2026 · 9 min read · 12 sources

You can move the database content of an on-premise SAP HANA system to SAP HANA Cloud with SAP's Self-Service Migration tool, but it is a database migration, not an S/4HANA move. The tool copies catalog objects, schemas and data, and it leaves design-time content and remote-source setups for you to rebuild. The S/4HANA ABAP system itself still runs on an SAP HANA database that you size, patch and back up, so HANA Cloud is a companion platform for most S/4HANA shops, not a drop-in replacement.

This guide is for Basis and database administrators, architects and developers who have been asked, "Can we just move HANA to the cloud?" It covers the options, the prerequisites, the migration steps, the findings you will have to fix by hand, and what changes in daily operations.

Start with the decision: which HANA are you talking about?

The first mistake is treating "HANA Cloud" and "on-premise HANA" as two versions of the same thing. SAP says SAP HANA Cloud, SAP HANA database is not replacing SAP HANA on-premise, and that it is the successor of the SAP HANA Service. The same SAP tutorial notes that existing HANA customers can extend their on-premise landscape to the cloud rather than leave it behind.

On the ERP side, the picture is narrower. The ABAP Platform 2025 underlying S/4HANA 2025 is described as supporting only the SAP HANA database with full use of its advanced capabilities. I could not find a source in this research that lists HANA Cloud as the database for the S/4HANA ABAP stack. Before you commit to a design, check the Product Availability Matrix and the release notes for your exact S/4HANA release.

OptionWhat it is for an S/4HANA landscapeWho operates the databaseTypical use
On-premise SAP HANAThe database under S/4HANA on-premise or a customer-run private setupYour Basis and DB team, or your hosting partner under contractThe ERP database of record
SAP HANA Cloud, SAP HANA databaseAn SAP-managed database service in SAP BTPSAP operates the service; you manage schemas, users and instancesSide-by-side data, analytics, extensions, and HANA-based apps
S/4HANA reading HANA CloudVirtual tables from the ABAP layer into HANA CloudBoth sides, with an agreed data-access designReporting or integration without copying data into ERP

The third row is the one that often works. SAP community guidance says you can create a virtual table so S/4HANA reaches data in HANA Cloud through SDA, even on HANA Runtime Edition, though you cannot create tables directly in the database layer there. Treat that as a design option to validate, not a default.

What the Self-Service Migration tool moves, and what it does not

The tool is run from SAP HANA Cloud Central. SAP's help says it lets you migrate the full on-premise database, excluding database users if you choose, or migrate selectively by schema or by XS Advanced service instance. Selective migration can run in iterations, which helps if you are moving one application schema at a time.

The scope is narrower than many teams expect. SAP's documentation says the tool migrates catalog objects, schemas, tables and the data stored in the database. It also says that SAP HANA repository content, such as calculation views, SDI flowgraphs and design-time database objects, is not migrated and must be handled manually. The same page notes that remote sources come across in an invalid state and need reconfiguration.

For the on-premise scenario, SAP's compatibility table lists catalog and schema data migration for SAP HANA Platform 2.0 on-premise, with XSA service instance migration also supported. Read that as the supported path. Anything outside the table is a project decision, not a tool option.

Prerequisites to check before you book the downtime

Start with the revision. SAP's help states the source must be at SAP HANA Database Revision 53 or greater. Older SAP community posts describe the same gate in terms of SPS 05 revision 53, so use the current help text as the rule and record the exact revision in your migration plan.

Then check the network path. The on-premise database must allow encrypted connections. If you use SAP Cloud Connector, it must be installed on the on-premise side and registered in the BTP subaccount that hosts the HANA Cloud instance. Without Cloud Connector, the SQL port must be reachable from the internet, and SAP Note 3153915 lists the migration service IPs you would need to allow.

Finally, set up the users. The migration uses a dedicated migration user on the source database. A migration user is created in the source database with the privileges it needs, and you connect through Cloud Connector. You also supply DBADMIN credentials for the target. Record who owns each credential and when it is disabled.

The migration flow, step by step

The wizard follows a fixed sequence. SAP's documentation describes phases named Plan, Preparation, Execution, Validation and Finalization. The Cloud Foundry page is the source for those names, but the same phases frame the on-premise flow.

  1. PlanPick the scope: full, by schema, by table or by XSA instance
  2. PrepareMigration user, Cloud Connector or NAT allow-list, target instance sized
  3. CheckCompatibility run; log every Critical, Error and Warning
  4. ExecuteOffline copy of catalog and data; downtime is planned for the source
  5. ValidateRow counts, object counts, sample business queries, app smoke tests
  6. FinalizeDeactivate the migration user and close out clean-up
Figure 1. The Self-Service Migration flow from on-premise SAP HANA to HANA Cloud, with the checks a sign-off needs

Two details change your downtime plan. SAP's community guidance says the tool is an offline migration, so downtime must be planned, and preparation can run before the cutover window. Also, the migration has to be finished in one window. The Cloud Foundry wizard archives migrations not completed within 60 days, so do not leave a half-run migration open across a project gap.

The compatibility findings you will have to fix

The severity model is the part to read closely. The tool reports Critical, Error, Warning and Info findings. Critical items block the migration. Error items will not migrate because HANA Cloud lacks the feature. Warning items migrate but may behave differently on HANA Cloud.

The most common design-time trap is HDBCDS. A SAP community write-up notes HANA Cloud has no HDBCDS plug-in, so projects that still generate those artifacts will fail or conflict. The same write-up recommends moving to the package-based definitions and clearing the double definitions before you migrate.

SQL and procedure code also needs a review pass. A community example from an HANA application migration shows TRUNCATE statements being replaced with DELETE FROM, and series entities not being supported on HANA Cloud. Your developers should expect this kind of change in procedures and calculation views.

What changes in daily operations

On-premise HANA gives you the root user, the OS and the full parameter set. HANA Cloud does not. SAP's own migration guidance points out that several predefined database users are required to operate the service, and one of them is controlled exclusively by SAP to create users and run system activities. Your runbooks should assume you cannot touch those accounts.

The tools are familiar. The same SAP tutorial says SAP HANA cockpit and SAP HANA database explorer are the two tools you use on both platforms, though the cockpit differs in places. Plan training on that difference, not on the tool names.

Data movement between the two also changes. The Smart Data Integration model uses the Data Provisioning Agent and works in both directions between on-premise HANA and HANA Cloud. That agent becomes a monitored component on your Basis side, with its own patching and access checks.

Patch cadence is the last piece. HANA on-premise follows SPS and revision maintenance on SAP's schedule, and the dates are not all in plain view. For example, SAP's support date for SPS 05 was June 2025, which has now passed. For current SPS dates, check SAP Note 2378962, which requires an SAP login. Your HANA Cloud instance follows SAP's service calendar, so write down which of your revisions and service versions must be validated together.

A sign-off checklist for the cutover

  • Source revision is recorded, and it meets the current SAP help requirement.
  • Cloud Connector or direct connection is tested, with the encrypted connection confirmed.
  • Migration user and DBADMIN credentials are owned, logged, and disabled at finalize.
  • Compatibility report has every Critical item resolved and every Error and Warning item dispositioned.
  • HDBCDS and repository content have a rebuild plan and a named developer.
  • Remote sources and virtual tables are reconfigured and tested with real queries.
  • Row counts and key business totals match between source and target, signed by the functional owner.
  • Runbooks reflect the SAP-controlled users and the Data Provisioning Agent support model.

If your team is still deciding whether the database move belongs in the same program as the ERP move, the RISE testing ownership guide sets out what a RISE contract does and does not hand to you. For a broader view of how HANA choices affect data and performance, the row store vs column store guide shows which tables to check before you move them.

For the platform basics, the free SAP HANA Database Essentials for Platform Teams course in the Academy covers the architecture you need before you migrate. If your landscape is moving under RISE, the Academy course on operating S/4HANA Cloud Private Edition under RISE covers the operating model around the database.

Frequently asked questions

Can I move my S/4HANA on-premise database into SAP HANA Cloud?

I could not verify that HANA Cloud is a supported database for the S/4HANA ABAP stack. The sources I checked describe the S/4HANA 2025 ABAP platform as running on SAP HANA, and HANA Cloud as a companion for extensions, data and virtual tables. Confirm the answer for your exact release in the Product Availability Matrix before you plan the move.

Does the Self-Service Migration tool move my calculation views and design-time objects?

No. SAP's documentation says repository content such as calculation views, SDI flowgraphs and design-time database objects is not migrated by the tool. You rebuild them in the target, with the design-time artifacts updated for HANA Cloud.

How long is the downtime for an on-premise HANA migration?

It depends on data volume and the scope you choose, so measure it in a rehearsal. The tool is an offline migration, so the source must be planned down for the copy. Run the compatibility check and a full dress rehearsal first, and use those timings to set the cutover window.

What is the biggest operational change after the move?

You lose direct control of some predefined users and the underlying service, and you gain a managed platform with its own maintenance calendar. The practical change is in your runbooks, access model and monitoring of the Data Provisioning Agent. Test those changes as part of the cutover, not after it.

Sources

  1. Understand the Differences Between SAP HANA On-Premise and SAP HANA Cloud, SAP HANA Database, SAP Developers, undated
  2. ABAP Platform in SAP S/4HANA Cloud Private Edition and SAP S/4HANA 2025, SAP Community, 2026
  3. SAP S/4HANA Data Management and Analytics empowered by SAP HANA Cloud, SAP Community
  4. Migrate an SAP HANA On-Premise Database to SAP HANA Cloud, SAP Help Portal, SAP HANA Cloud Migration Guide
  5. The Self-Service Migration Tool for SAP HANA Cloud, SAP Help Portal
  6. Connect to an SAP HANA Platform On-Premise Database, SAP Help Portal, SAP HANA Cloud Migration Guide
  7. Migration of SAP Hana On-Premise Database to SAP HANA Cloud, SAP Community
  8. Migrate an SAP HANA Service Database (Cloud Foundry) to SAP HANA Cloud, SAP Help Portal
  9. Are you curious about Self-Service Migration Tool for SAP HANA Cloud?, SAP Community
  10. Migrating CDS projects from HANA Service or HANA 2 to HANA Cloud, SAP Community, 2023
  11. SAP-samples/xsc-cap-migration, SAP samples on GitHub
  12. Planned Release of SAP HANA 2.0 SPS05 and Impact on Maintenance for SAP HANA, SAP Community blog, 2020

More on SAP HANA

How this guide is made: researched with AI-assisted search across SAP documentation and practitioner sources, with every fact linked to its source. Found an error or have field experience to add? Tell us.