SAP HANA Brownfield Migration – The Complete Checklist for 2025
With this compact brownfield checklist, you can successfully transition to SAP S/4HANA in a structured, step-by-step manner:
Phase 1: Preparation & Project Planning
☐ Document the SAP system landscape (ERP version, OS/DB, Unicode status)
☐ Define the target architecture (on-premises, private cloud, RISE)
☐ Run the Maintenance Planner and define the stack
☐ Analyze dependencies (add-ons, third-party tools, interfaces)
☐ Define the scope of the project and milestones
☐ Calculate Budget & Resources
☐ Establish a project team with defined roles and responsibilities
☐ Involve key users and business units early on
☐ Plan a communication strategy and project marketing
☐ Coordinate a backup strategy for all systems
☐ Coordinate the schedule and downtime windows
Phase 2: System Analysis & Preliminary Studies
☐ Download and run SAP Readiness Check 2.0
☐ Repeat the Simplification Item Check regularly
☐ Analyze custom code with ATC & SCI
☐ Identify & highlight unused custom code
☐ Review Business Functions & Industry Solutions
☐ Create and prepare an archiving strategy
☐ Analyze Data Volume & Growth
☐ Perform HANA sizing (CPU, RAM, storage)
☐ Check system requirements (kernel, database, OS)
☐ Optionally enable CCLM (Custom Code Lifecycle Management)
☐ Prepare Unicode conversion (if not already available)
☐ Check technical users and permissions
Phase 3: Preparatory Measures
☐ Perform Unicode conversion (if still necessary)
☐ Update Support Packages & SPAM/SAINT
☐ Install the latest SAP Notes (as per the Maintenance Planner)
☐ Prepare SAP Solution Manager for DMO/SUM
☐ Have add-ons and business functions reviewed and approved
☐ Take inventory of interfaces (IDocs, RFC, BAPIs, Web Services)
☐ Document batch jobs and schedules
☐ Save and evaluate transport orders
☐ Check workflows for compatibility
☐ Back up print and spool configuration
☐ SAP Fiori Preparations (Embedded Deployment?)
☐ Clone the system in a sandbox or test environment
Phase 4: TECHNICAL MIGRATION & CONVERSION
☐ Full backup of the database, application, and file system
☐ Configure SUM in DMO mode (including benchmarking)
☐ Perform a database migration to SAP HANA
☐ Check table migration (large objects, clusters, pools)
☐ Check the migration of user and role data
☐ Conversion of tables (MATDOC, ACDOCA, etc.)
☐ Edit and confirm simplification items in SUM
☐ Manually customize SPDD (dictionary objects)
☐ Clean up & synchronize SPAU (repository objects)
☐ Edit custom code and run unit tests
☐ Reassign transaction codes and reports (e.g., KE24 → Fiori app)
☐ Perform debugging and dump analysis on a regular basis
☐ Adjust system parameters (e.g., parallel degree, memory)
Phase 5: FUNCTIONAL TESTS & QUALITY ASSURANCE
☐ Check system startup and basic services (RFC, spool, background jobs)
☐ Check cross-client settings
☐ Monitor ST03N & ST22 for errors and dumps
☐ Test business processes (e.g., P2P, O2C, HCM, FI Closing)
☐ Test Custom Reports & User Exits
☐ Validate workflows and forms (SmartForms, Adobe)
☐ Configure and Test SAP Fiori Launchpad
☐ Test Permissions & Roles in the New S/4HANA
☐ Run performance benchmarks (STAD, HANA Studio)
☐ Perform integration testing with peripheral systems
☐ Conduct acceptance tests with business units (UAT)
☐ Document and approve regression tests
Phase 6: Go-Live & Post-Implementation Support
☐ Finalize the cutover plan, including times and assigned personnel
☐ Define go-live processes for each module
☐ Download the latest Delta backup
☐ Activate and release the production system
☐ Inform users and provide training if necessary
☐ Enable monitoring (EarlyWatch, HANA Cockpit, Solution Manager)
☐ Log Analysis and Dump Monitoring
☐ Fix permission issues
☐ Document and prioritize open issues
☐ Document lessons learned
☐ Ensure a support phase with the Hypercare team
☐ Identify opportunities for optimization (e.g., Fiori, Embedded Analytics)
Conclusion
Be fully prepared with this comprehensive, field-tested SAP S/4HANA brownfield checklist and ensure a controlled transformation with minimal risk. The better the groundwork, the smoother the migration.
