Performing the Selective Data Transfer to SAP Cloud ALM

This is the final instalment in our blog series on transitioning from SAP Solution Manager to SAP Cloud ALM. If you’ve been following along, you already know why Selective Data Transfer (SDT) is such a powerful tool, and how a bit of planning and testing up front can set you up for success.

Now comes the exciting part: bringing your content into SAP Cloud ALM and starting fresh.

But don’t worry, we’re not here to throw spreadsheets or error codes at you. This final phase isn’t just about what you’re transferring. It’s about the value you're unlocking by doing it right.

Fig 1: Library Elements handling in SDT

What Are You Really Moving?

Selective Data Transfer isn’t an all-or-nothing move. It’s a structured process that helps you bring across only the assets you really need. Here’s what’s included:

• Process Hierarchy: The structure of your business processes.
• Libraries: Key building blocks like applications, configurations, and process steps.
• Process Content: The actual workflows and diagrams.
• Test Cases: The testing scenario validation.
• Documents: Supporting files, metadata, or links to external sources.

But more importantly, it helps you:

• Streamline your ALM landscape

• Simplify how teams access and manage key information

• Establish a foundation that’s fit for continuous innovation

Whether you’re bringing documents into SAP Cloud ALM, integrating SharePoint, or refining your process libraries, SDT gives you structured control over what comes with you and what doesn’t.

Fig 2: SDT for Libraries

Think Smart, Move Strategically

Every organisation will scope and execute SDT a little differently. And that’s exactly the point.

This isn’t a lift-and-shift. It’s a chance to rethink how you manage application lifecycle content across your SAP environment, with flexibility, ownership, and alignment at the core.

Start with a clean structure. Prioritise what supports your current transformation goals and know that SAP Cloud ALM gives you the platform to evolve further as your business grows.

What About Documents?

Documents can be handled in a few different ways, depending on your needs:

• Keep them in SAP Solution Manager (and link to them from Cloud ALM)
• Move them to an external DMS like SharePoint or Google Drive
• Use SAP BTP’s DMS for full cloud integration (coming soon!)

Each option has pros and cons, and there’s no one-size-fits-all answer, just pick the route that works for your business today, with an eye toward future flexibility.

Fig 3: Migration of Documents from SAP Solman to SAP Cloud ALM

What Happens Next?

You’re no longer in the preparation stage, now you’re ready to activate the future of ALM. With your foundations in place and a proven testing approach, your final SDT upload becomes the first real milestone in your Cloud ALM journey.

From here, your teams can begin:

• Managing projects in a simplified, cloud-native workspace

• Collaborating around live process data, not static files

• Tracking changes and ownership more clearly than ever

It’s the start of a more agile, responsive way of managing SAP and it begins with a confident move today.

Catch Up on the Series

Missed a step in the journey? Here's where to go:

1. Transitioning to SAP Cloud ALM the Right Way: A Practical Look at Selective Data Transfer
2. Laying the Groundwork for Your Move to SAP Cloud ALM
3. Testing Selective Data Transfer – How to Prevent Pain Later

Let’s Make It Real

At Rapid X, we don’t just help you tick boxes, we help you make your transition strategic, structured, and successful.

If you’re ready to take the final step, or if you want to explore what’s possible  let’s talk.

Book a discovery session
Request a readiness check

Your next chapter in SAP ALM starts here!