Name the SAP change before sizing the server
| Project | What changes |
|---|---|
| SAP application platform migration | The application server OS or hardware changes while supported application behavior is retained. |
| SAP HANA x86 to Power migration | The HANA platform changes; revision and certified configuration govern the method. |
| SAP database-engine change | The database changes and the selected SAP product needs its approved conversion procedure. |
| SAP S/4HANA business conversion | Application and business-process changes add work beyond a hardware migration. |
Record the complete SAP and database stack
Capture SAP product/release, kernel, Unicode status, installed add-ons, database/revision and the OS release for each tier. Record SAP sizing evidence, peak memory, data volume, growth and recovery targets. Include interfaces, transports, print/spool services and scheduled jobs.
Have the responsible SAP team confirm the exact product, database, OS and Power configuration in the current SAP support matrices and relevant notes. A supported Linux distribution is not a complete SAP HANA certification.
SAP on HP-UX or Solaris needs a qualified system copy
Determine whether the application tier, database tier or both will change. A move from HP-UX or Solaris to AIX or Power Linux needs the procedure for the exact SAP product and database. Use SAP’s applicable system-copy documentation and approved tools; do not treat OS files or a database backup as a universal system-copy method.
Keep source application versions and add-on support with the target decision. An application upgrade can be a prerequisite, a separate later task or an intentionally combined project after qualification.
HANA on x86 can have a documented same-endian transfer
SAP’s HANA 2.0 system-copy documentation includes backup/recovery between Intel Linux and little-endian Power Linux under its stated prerequisites. An x86-to-Power HANA move therefore does not always require logical export/import. Confirm the source/target revisions and current SAP rules for the actual system.
Where a qualified system-replication design is proposed, verify the supported combination and rehearse initialization, synchronization and takeover. Choose the method from the documented requirements and measured outage rather than a generic “near-zero downtime” promise.
Changing the SAP database is a separate conversion decision
Moving an SAP application from Oracle or another database to HANA changes more than the processor. Use the conversion or migration procedure supported for that SAP product, release and target. Include data preparation, sizing, custom-code checks and business validation.
Keep a same-engine platform move distinct from a database-engine conversion when comparing the scope, outage and recovery work.
S/4HANA conversion has business work beyond the Power move
A Power destination can be one infrastructure choice within an S/4HANA project. It does not perform the business conversion. Application ownership must cover supported source releases, add-ons, data preparation, custom code and process acceptance alongside the infrastructure team.
Rehearse SAP business operation on the proposed target
| Acceptance area | Evidence before production |
|---|---|
| Sized and certified Power configuration | Approved SAP sizing and the exact software/platform combination. |
| Interfaces, batch and business transactions | Representative end-to-end processing with reconciled results. |
| Backup, availability and recovery | Successful recovery tests and ownership of retained services. |
| Final synchronization and cutover | Measured timings and a decision before the destination accepts writes. |
Plan the Power destination with Midland
Use the assessment to decide which workload belongs on Power before comparing hardware. Midland’s Power model catalog supplies the server identities; software eligibility and measured workload demand decide the configuration.
Prepare the conversion inventory and Bring your current OS, application and database versions to Midland.
Sources and release checks
Technical guidance checked October 21, 2026. Confirm the exact application edition, OS release and target architecture with its vendor before ordering. Older technical papers explain migration methods; they do not establish current certification.