SolMan migration
Preserve Solution Manager ChaRM and ITSM history in a sealed archive, run TENSOR in parallel with Solution Manager, and cut over against a checklist computed from live data.
SAP Solution Manager's mainstream maintenance ends in 2027. The SAP integration gives you two tools for leaving it: a sealed, read-only archive for the ChaRM change documents and ITSM tickets that SAP's own migration path does not carry, and a migration mode that turns the usual 6 to 12 months of parallel operation into a measured process.
At first launch, the SAP module is scoped to named landscapes, bounded evaluations or coexistence with Solution Manager. It is not positioned as a replacement for SolMan ChaRM across every landscape.
The SolMan historical-data archive
Importing
- You import ChaRM change documents and ITSM tickets from a CSV export of Solution Manager, under Settings → SolMan archive imports.
- Column names are accepted liberally (
External ID,EXTERNAL-ID,externalid). The required fields are external ID, kind, title and created date. - Dates may be ISO, German (
01.04.2023) or SAP format (20230401). - XLSX files are not read directly — export Solution Manager data to CSV. XLSX support is planned.
Dry run first
Every import starts with a dry run. It shows counts, rejected rows with reasons, overlaps with earlier batches and sample rows. Nothing is written until you confirm. A row is rejected when a required field is missing or the kind or date cannot be read; the report names the reason, so you can fix the export and repeat the dry run.
Sealing
A confirmed batch is imported in chunks and sealed with the SHA-256 hash of its content in the audit chain. From then on:
- archive records can never be edited or deleted;
- corrections are a new batch that supersedes the old one;
- the archive can be verified against the audit chain.
Records that reference transports are linked to the live transports in TENSOR.
Batch lifecycle
| Step | What happens |
|---|---|
| Dry run | The CSV is parsed; you see counts, rejects with reasons and overlaps. Nothing is stored. |
| Confirmed and sealed | Rows are imported in chunks and the batch is sealed with its content hash. |
| Superseded | A newer batch replaces it; the old one remains on record. |
Browsing and exporting
The archive is browsable under Changes → SolMan archive, with search and filters for Kind (ChaRM change, ITSM ticket), Status, Batch and Year. Each record shows its Provenance: import batch, import time, content hash and the sealing audit row.
Each batch can be exported as evidence — a CSV with a signed manifest — from Settings → SolMan archive imports. Archive requesters and assignees are masked for roles without de-masking rights.
| Who | Can |
|---|---|
tenant_admin | Dry-run, import and supersede batches (integration.config.manage); read and export the archive |
auditor, compliance_officer | Read and export the archive (sap.archive.read, sap.archive.export) |
external_auditor | Read the archive (sap.archive.read) |
Migration mode
The migration mode records how far your tenant has moved from Solution Manager to TENSOR. Every change of mode is audited.
| Mode | Meaning |
|---|---|
| Off | Default; no migration tracking. |
| Parallel run | Solution Manager and TENSOR run side by side; dashboard and cutover checklist are active. |
| Cut over | Cutover date recorded; the widget shows a migrated summary. |
You set the mode under Settings → SAP integrations → SolMan migration.
The migration dashboard
In Parallel run, the migration dashboard (page SolMan migration) shows:
- Agent health;
- Inventory coverage;
- Transport-sync freshness;
- Drift — Cloud ALM and transport drift;
- Archive import status.
A SolMan migration widget on the administrator start page summarises the same picture.
The cutover checklist
The cutover checklist is computed from live data, with no manual ticks. Each item has a Fix link that opens the page that resolves it.
- Connector agent healthy for 7 consecutive days
- At least one sealed SolMan archive batch
- A change closed through a production import
- SAP separation-of-duties catalog seeded
- Production CAB configured for every landscape
The CAB role per landscape stage is partially available: it is stored and checked by this checklist, but there is no screen to set it yet.
Cutting over
When every item is green, you choose Cut over and confirm. TENSOR records the cutover date in the audit trail, and the dashboard widget collapses to a Migrated from Solution Manager summary.
A migration path in outline
- Switch on
sap_integrationand run the initial setup, which seeds the SoD catalog. - Register your SAP systems, define landscapes and enrol a connector agent.
- Set the migration mode to Parallel run.
- Import SolMan history — dry run, then confirm — so at least one batch is sealed.
- Let transports flow through TENSOR until a Change closes through a production import, while Solution Manager keeps running.
- Watch the dashboard until the agent has been healthy for 7 consecutive days and every checklist item is green.
- Cut over.
Step-by-step instructions are in Guides for auditors and migration.
Operations and evidence
SAP monitoring alerts as incidents, HANA and EarlyWatch Alert evidence, SAP authorisations and SoD, licence measurement and the read-only Cloud ALM bridge.
SAP integration and compliance
The regulatory requirements the SAP integration produces evidence for, the evidence each feature leaves behind, and the flags you need.