blue.works logo

alm360 for Migration

Selective data transfer with added value

SAP Cloud ALM is the new standard – but getting there is not a sure-fire success.

Many companies are faced with the same questions:

  • What content from the SAP Solution Manager sind noch relevant?
  • Wie vermeiden wir Altlasten und Chaos beim Umstieg?
  • Wie wird aus einer Migration ein echter Mehrwert für Projekte und Betrieb?

alm360 for Migration

Selective data transfer with added value

SAP Cloud ALM is the new standard – but getting there is not a sure-fire success.

Many companies are faced with the same questions:

  • What content from the SAP Solution Manager sind noch relevant?
  • Wie vermeiden wir Altlasten und Chaos beim Umstieg?
  • Wie wird aus einer Migration ein echter Mehrwert für Projekte und Betrieb?

alm360 for Migration

Selective data transfer with added value

SAP Cloud ALM is the new standard – but getting there is not a sure-fire success.

Many companies are faced with the same questions:

  • What content from the SAP Solution Manager sind noch relevant?
  • Wie vermeiden wir Altlasten und Chaos beim Umstieg?
  • Wie wird aus einer Migration ein echter Mehrwert für Projekte und Betrieb?

Keep scrolling for more information

A perfect match.

A successful migration begins not with technology, but with clarity about the target image.

We therefore recommend using the migration service with our alm360 Assessment to combine them. This turns a data move into a real transformation.

alm360 for Migration to SAP Cloud ALM

With alm360 for Migration to SAP Cloud ALM, we don’t just transfer data.

We create a structured transition – streamlined, well thought-out and future-proof.

Technically based on SAP Selective Data Transfer (SDT), accelerated and secured by our alm360 Data Manager methodically with the know-how from over 100 ALM projects.

alm360 Assessment

The alm360 assessment provides answers – concrete, structured and implementation-oriented, before we start the migration. It creates transparency about your system and tool landscape, evaluates the fit with SAP Cloud ALM and develops a roadmap for the introduction – or migration.

alm360 Hub / Data Manager accelerators

Our approach: selective, structured, sensible.

1. Initial check & clarification of objectives

  • Which processes and structures should really be included?
  • Where does a clean-up make sense?
  • What does your ALM target architecture look like?

2. Data extraction with the SAP SDT app

  • Use of the standard app (SM_CALM_DT)
  • Export of relevant content (processes, libraries, documents, test steps, etc.)

3. Quality check & cleanup

  • Tagging, mapping, naming conventions
  • Reduction and harmonization
  • Recommendations for a consistent setup in cloud ALM

4. Structured import & activation

  • Support with uploading to SAP Cloud ALM
  • Advice on structure, tag management and initial use
  • Ensuring connectivity to subsequent operating models

5. Enablement & Fit for Future

  • Review of the new structure
  • Recommendations for further action with SAP Cloud ALM
  • Optional: Connection to our alm360 Operations model

6. Solution Manager shutdown

  • alm360 Data Manager? ITSM, Audit, Knowledge Warehouse
  • alm360 Hub?
  • Migrate open objects instead of phasing out SolMan
  • Mapping documents from SolDoc to a non-SAP BTP DMS repository

Our approach: selective, structured, sensible.

1. Initial check & clarification of objectives

  • Which processes and structures should really be included?
  • Where does a clean-up make sense?
  • What does your ALM target architecture look like?

2. Data extraction with the SAP SDT app

  • Use of the standard app (SM_CALM_DT)
  • Export of relevant content (processes, libraries, documents, test steps, etc.)

3. Quality check & cleanup

  • Tagging, mapping, naming conventions
  • Reduction and harmonization
  • Recommendations for a consistent setup in cloud ALM

4. Structured import & activation

  • Support with uploading to SAP Cloud ALM
  • Advice on structure, tag management and initial use
  • Ensuring connectivity to subsequent operating models

5. Enablement & Fit for Future

  • Review of the new structure
  • Recommendations for further action with SAP Cloud ALM
  • Optional: Connection to our alm360 Operations model

6. Solution Manager shutdown

  • alm360 Data Manager? ITSM, Audit, Knowledge Warehouse
  • alm360 Hub?
  • Migrate open objects instead of phasing out SolMan
  • Mapping documents from SolDoc to a non-SAP BTP DMS repository

Your added value with blue.works.

  • Clear migration strategy – instead of 1:1 data transfer
  • Reduced complexity – through selective, streamlined, and documented transfer
  • Confident decision-making – which content remains truly relevant
  • Direct connection – to SAP Cloud ALM, Data Manager, and Operations

When structure makes the difference.

  • Companies switching from SAP Solution Manager to Cloud ALM
  • Organizations that want to avoid legacy issues and maintain quality
  • Project teams that see migration as an opportunity for clarity and governance
  • IT leads who want to turn changeover into real added value for projects and operations

FAQ

Is the service also suitable for on-premise systems?

Yes – we support SAP Solution Manager 7.2 and Focused Build 2.0.

How does the migration work technically?

We use the SAP SDT app and assist with export, mapping, quality assurance and import.

What is accepted – and what is not?

Only what makes sense: libraries, documents, processes, test steps – not change plans, test plans or irrelevant structures.

How long does the migration take?

Typically 2-3 months for a standardized takeover. Quick assessments can be shorter.

Is this a one-off action or part of a larger ALM strategy?

Both are possible – ideally you should integrate the migration into an overall strategy.

Our tip: Combine it with the alm360 assessment.