Support Launchpad vs. SAP for Me: Which One Should You Use?
If you have spent any time managing SAP systems, you have probably typed a support ticket into one portal only to get redirected somewhere else entirely. That confusion is at the heart of one of the most common questions IT teams ask today: should you be using Support Launchpad or SAP for Me. The short answer is that this is not really an either or decision anymore, but understanding why matters a lot if you want to stop wasting time hunting for the right screen every time you need to raise a case, check a license, or download software. In this guide I will walk through what each portal actually is, why the confusion exists in the first place, and how to make sure your team is working in the right place going forward.
What Is SAP ONE Support Launchpad
SAP ONE Support Launchpad was, for years, the primary home for anyone dealing with SAP technical support. If you needed to log an incident, search for SAP Notes, request a license key, or manage S user authorizations, this was the tool you opened. It was built with system administrators in mind. The interface was organized around tiles, each one linking to a specific support function, and it did the job reasonably well for a technically minded audience that already knew exactly what they were looking for. The problem was that Launchpad never really evolved to serve anyone outside that narrow technical circle. Business users, finance teams, and anyone who was not deep in SAP Basis work found it clunky and unintuitive. As SAP pushed more customers toward cloud products, that gap became impossible to ignore.
What Is SAP for Me
SAP for Me is SAP’s newer, broader customer portal, and it has effectively absorbed everything that Launchpad used to do. Instead of tiles, it uses dashboards and cards, and instead of speaking only to system administrators, it is designed to give both technical and non technical users a clear view of their SAP landscape. That includes products, orders, licenses, provisioning, maintenance, and support all in one place. SAP began redirecting Launchpad users to SAP for Me in April 2023, ran both portals in parallel for a transition period, and by the end of June 2023 the Launchpad homepage was fully deprecated. Any old bookmark to launchpad.support.sap.com now automatically forwards to SAP for Me. So while people still search for Support Launchpad by name, the tool itself as a standalone destination no longer exists in its original form.
Why People Still Ask Which One To Use
Old habits die hard, especially in enterprise IT where teams build muscle memory around specific tools over years of daily use. If you were raising incidents through Launchpad for a decade, it makes sense that your instinct is still to look for it first. There is also a real amount of lingering confusion because SAP renamed things during the switch. What used to be called an incident is now called a case. What used to be a tile is now a card. The Incident Wizard became the Get Support application. None of the underlying functionality disappeared, but the labels changed, and that alone is enough to make experienced users feel like they are starting from scratch.
Feature by Feature Comparison
Interface and Navigation
Launchpad organized everything into a flat grid of tiles, which worked fine once you memorized where things were but offered little context for new users. SAP for Me replaces that with dashboards, the most relevant being Services and Support and Systems and Provisioning, where related tasks are grouped together with more descriptive cards and a genuinely useful search bar. If you search for a term, results are broken into categories like Knowledge Base articles, Dashboards and Pages, Downloads, Contacts, Products, and Licenses, which makes it far easier for someone unfamiliar with SAP terminology to find what they need.
Support Case Management
This is the core function most people care about, and it has actually improved. The Get Support application in SAP for Me walks you through a guided flow rather than dropping you into a blank form. It uses AI to help predict the right product category for your issue and recommends the most appropriate channel, whether that is Expert Chat, Schedule an Expert, Ask an Expert Peer, the SAP Community, or submitting a formal case. Launchpad’s old Incident Wizard could not do any of that. If your team is still manually guessing which component to select before submitting a ticket, switching fully to the Get Support flow alone is worth the adjustment period.
License and User Management
Both portals handle S user administration and license key requests, and SAP made sure this stayed familiar during the transition, so tasks like creating new S users or adjusting authorizations look and feel almost identical to what Launchpad users were used to. Where SAP for Me pulls ahead is in license utilization visibility. Instead of digging through a separate application, you get a consolidated view of consumption, orders, and licensing status tied directly to your product portfolio.
Cloud Provisioning and Self Service
This is an area where Launchpad genuinely could not compete because it was never designed for it. SAP for Me includes self provisioning for cloud services, invoice payment, and system availability monitoring through the Cloud Availability Center integration. If your organization has been moving workloads to SAP’s cloud products, this alone is reason enough to fully commit to SAP for Me rather than trying to preserve old Launchpad workflows.
Personalization
Launchpad offered essentially the same layout to every user regardless of role. SAP for Me asks new users what they work with and what tasks matter to them, then customizes the homepage cards accordingly. It also carries over your prior Launchpad tile usage automatically, so the system has a head start on figuring out what you actually need to see first.
Mobile Access
SAP for Me has a dedicated mobile app available on both the Apple Store and Google Play, letting you check support cases or system status from your phone. Launchpad never had a true mobile equivalent, so this is a straightforward win for teams that need visibility outside the office.
So Which One Should You Actually Use
At this point the practical answer is simple. SAP for Me is the only option, because SAP ONE Support Launchpad no longer exists as a separate destination. Any bookmark, shortcut, or saved link pointing to the old Launchpad homepage will redirect you automatically. Your existing Launchpad S user authorizations carried over with no extra setup required, so there is no access barrier standing in your way. The real decision your team faces is not which portal to pick but how quickly to get comfortable with the new structure. Teams that resist the change and keep trying to force old workflows into the new interface tend to struggle the most, while teams that take an hour or two to actually explore the dashboards adapt quickly.
Practical Tips For Making The Switch Smoother
Start by bookmarking me.sap.com/home directly instead of relying on old Launchpad shortcuts, since this removes any dependency on redirects and gets you straight into the current interface. Next, spend a few minutes on the personalized onboarding flow the first time you log in. It genuinely does shape your homepage around your actual responsibilities, and skipping it just means more manual searching later. If your team submits a high volume of support cases, walk through the Get Support application once with a real issue rather than a test case, since the AI driven recommendations only make sense once you see them applied to something you actually need resolved. It also helps to update any internal documentation, wikis, or onboarding guides that still reference incident numbers or Launchpad tile names, because new hires who read outdated internal docs will end up more confused than if they had no documentation at all. Finally, if you manage a team of SAP administrators, consider running a short fifteen minute walkthrough of the Services and Support dashboard specifically, since this is where the terminology changes from incident to case tend to trip people up the most in daily conversation.
Common Mistakes To Avoid
One mistake teams make is assuming they need special new permissions to use SAP for Me. They do not. Your existing S user credentials work immediately. Another common issue is people trying to manually recreate their old Launchpad tile layout inside SAP for Me instead of letting the dashboard and card system organize things its own way, which usually results in a messier experience than just accepting the new structure. Some teams also continue referring to cases as incidents internally, which is harmless in casual conversation but can cause friction when searching the knowledge base, since search results are indexed under current terminology.
Final Thoughts
The debate between Support Launchpad and SAP for Me is really a story about SAP consolidating years of fragmented tools into a single, more capable portal. Launchpad served its purpose well for the administrators who grew up using it, but it was never going to scale to meet the needs of cloud customers, business users, and mobile access demands. SAP for Me is not a rival product competing for your attention, it is simply the evolved version of the same support experience with genuinely useful upgrades layered on top. If your organization has not fully transitioned its internal habits and documentation yet, now is the time to do it properly rather than continuing to work around old muscle memory.