SAP Testing

Tosca Cloud Migration From Tosca Commander for SAP Testing Teams

A Tosca Cloud migration moves SAP test automation from Tosca Commander on company servers to the Tricentis-hosted SaaS version of Tosca. Teams can upgrade on-prem to Tosca 26.1 in about 10 to 14 weeks or migrate to Tosca Cloud in about 12 to 22 weeks. A phased plan triages the test library, runs DEX and Elastic Execution Grid in hybrid, assigns ownership, and connects results to release gates. Merito delivers this work as a Tricentis Certified Solution Partner.

By Chris CarpenterTricentis ToscaToscaTricentisSAP TestingSAP Test AutomationTest AutomationCI/CDMigration Testing
Back to insights

A Tosca Cloud upgrade moves an SAP testing program from Tosca Commander on company data center to the SaaS version of Tosca hosted by Tricentis. The move shifts execution, upgrades, and access control onto a managed platform, and it works best as a phased program that cleans up the test library in parallel, runs hybrid for a short period, and ties results to release decisions.

Tricentis Tosca 26.1 brings AI capability into Tosca, so many SAP organizations are choosing their path this year.

Two paths to Tosca AI in 2026

  • Upgrade Tosca on-prem to 26.1. Infrastructure stays where it is and AI features arrive through a connected cloud tenant. Plan on a 10 to 14 week project.
  • Migrate to Tosca Cloud. Tricentis runs the platform, updates arrive automatically, and execution scales on demand. Plan on 12 to 22 weeks.

Both ranges are estimated and account size and complexity set the real timeline. The Tosca 26.1 on-prem vs. cloud video walks through each path.

Questions leadership should answer first

SAP cloud release cycles push more change through regression testing every quarter. Before choosing a path, executive sponsors should be able to answer four questions.

  • Which order-to-cash, procure-to-pay, and record-to-report processes lack automated regression coverage?
  • Which go or no-go decisions still wait on manual evidence from business users?
  • Which interfaces could disrupt revenue, fulfillment, or the financial close?
  • How long does it take to validate a production-critical change today?

The answers help show where automation protects the most revenue and where a migration pays back first.

A four-phase Tosca Cloud migration plan

Phase 1. Triage the test library

Rank and score every test before it moves.

  • Business criticality and regulatory relevance
  • Defect detection history and run frequency
  • Data dependencies and maintenance cost
  • Duplicate coverage across teams
  • A named owner and a documented expected result

Tests that fail triage get retired, which cuts migration effort and future maintenance.

Phase 2. Run hybrid during the transition

Tosca 2026.1 supports a hybrid transition from DEX to Elastic Execution Grid. The Automation Object Service connects Tosca Server to Tosca Cloud, so existing TestEvents convert to ElasticExecutionGridEvents and run from Commander while new work starts in the cloud.

Plan agents by system type. According to Tricentis documentation, cloud agents run public web and API tests. Private SAP systems need team agents, which run on machines you provide and connect outbound to the Tosca Cloud tenant.

Phase 3. Set ownership and access

The 2026 Tosca Cloud releases added role assignment to SSO groups, workspace-level roles, shared asset libraries, and revision history with restore. Use them to make ownership explicit.

  • Business process owners set coverage priorities
  • Quality Engineering owns automation standards and asset health
  • DevOps owns pipeline integration and agent reliability
  • Release leaders own risk thresholds
  • Security and compliance own access and audit evidence

Phase 4. Connect results to release gates

Feed Tosca Cloud results into the delivery pipeline and weight them by business process risk. A failed procure-to-pay test should block a release, and a cosmetic failure should be logged for the next sprint. CI/CD with Tricentis Tosca covers the integration options.

Governing AI-generated tests

Tosca 26.1 can turn manual tests and Jira requirements into automation and repair scripts when the application changes. That speed holds up when four controls are in place.

  • Approved use cases and test data rules
  • Human review before a generated test can gate a release
  • Traceability from requirement to test to result
  • Training and enablement for QA, SAP, and DevOps teams

What we see in Merito migrations

Merito has delivered Tosca on-prem to Tosca Cloud migrations for enterprise SAP programs. Most often we see these three things:

  • Libraries carry more duplicate and orphaned tests than teams expect, so triage shortens the migration.
  • Private-network SAP systems are the most common surprise in execution planning.
  • Ownership gaps surface as soon as business users can see results in a browser.

Where Merito fits

Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Merito runs the readiness assessment, scopes the migration, and delivers the upgrade and migration work. If Tricentis quotes the engagement, you can ask for Merito as the delivery partner on Tricentis paper, or Merito can quote it directly.

Book a Tosca Cloud readiness consultation to map the right path for your SAP landscape.

About Tricentis Tosca

Tricentis Tosca licenses, renewals, upgrades and implementation are available through Merito, an authorized Tricentis reseller and services partner.

Frequently Asked Questions