Migrate to S4HANA, Archive to cloud datalake with API access, or traditional Cold Storage. For decision about your data destination, select add your master and transaction objects, move the sliders, get a live recommendation. Cloud archive is the default - you keep AI/ML access without carrying HANA storage.
Every business object lands in one of three places after cutover. The tool matches each object to its right home based on what you tell it.
Add a data object, adjust the sliders, and watch the verdict update live. Your lists are save locally in your browser - come back anytime.
Straight answers on placement, retrieval, and what happens after scoring.
Wherever your data platform is. Microsoft Fabric / OneLake, Databricks, Snowflake, BigQuery, Redshift, or plain object storage (S3, ADLS, GCS) with a query engine on top. uMigrate streams SAP data into whichever target you already run - with the semantic layer intact - so archived data stays queryable by BI tools and AI agents, not just retrievable as blobs.
Cold archive is retrieval-only: designed to prove compliance, not to answer questions. You can pull a document, but you cannot join it, filter it, or train a model on it without extracting and reprocessing. Cloud archive is live-queryable: same governance and retention, but the data is available to analytics and AI in the tools where operators and data teams already work. Cold archive is cheapest; cloud archive costs slightly more but preserves optionality.
Yes. Cloud archive is not offline. A federated query from S/4HANA (or from Excel, Power BI, Fabric) can retrieve individual records without a formal restore process. This is why cloud archive works as the default - you retain access without paying to keep the data inside S/4HANA storage.
Because "migrate just in case" is the single biggest driver of S/4HANA scope creep, timeline slippage, and permanent HANA storage cost. Cloud archive preserves access at roughly 10–15% of the cost of migration, meets most compliance rules, and keeps the data queryable for AI/ML. The tool only recommends migration when the inputs show real operational or statutory need.
Use your best estimate on the slider. The recommendation updates live as you change it, so you can see how sensitive the answer is to your input. When you run this inside a uMigrate project, the tool draws actual query-log evidence from your source system instead of a slider - so you replace guesses with actuals before final sign-off.
Placement is overridden to Retain. This is not archive and not migrate - it routes to a separate track that requires legal and audit review before any decision. Legal hold is a specific status with retention obligations that vary by matter; the tool never auto-decides for it.
Nothing leaves your browser until you request the executive summary. Your scoping session is saved in your browser's local storage so you can come back to it later. When you request the summary, we ask for a work email to send you a copy; that is the only point of network transmission.
The output of this tool is your scope register: the ranked list of objects with placement decisions and reasoning. Inside a uMigrate project, that register drives the LTMC load plan, the archive extraction, and the sign-off record. Same decisions, same reasoning - with your live record counts, query logs, and statutory retention tables filled in instead of guessed.
Yes. After you request the summary, you can download the full scope decision as CSV - ready for your blueprint workshop, RASCI sign-off, or handover to the SI.
This tool works standalone for scoping conversations. Inside uMigrate, the same decision runs against actual query logs, live record counts, and statutory retention tables from your source system - replacing guesses with actuals.
Enter a work email to see the full report - placement, reasoning, and cost band per object. We use this to send you a copy for reference and follow up only if you request it.
| Object | Records | Placement | Migrate cost | Cloud cost | Cold cost |
|---|
Export as CSV for your blueprint workshop, or run this decision inside your uMigrate project with actual query logs, statutory tables, and record counts pulled live from your source system.