What Moves, What Transforms, What Gets Left Behind

A practical guide to categorizing your Tricentis Tosca assets before migration begins

Migrates directly
Test case logic
Scenarios, acceptance criteria, and coverage maps. Intent is platform-independent.
Test data
Parameterized inputs, data sets, and configurations. Format changes; data carries over.
Requirements traceability
Jira and Azure DevOps mappings re-established in Katalon Test Management.
Execution configs
Browser/device combinations, environments, and CI/CD schedules.
Transforms (rebuild)
Tosca modules and test cases
Proprietary format cannot import directly. Logic recreated via the Test Generation Agent or manual scripting.
Custom actions
Reusable Tosca modules rebuild as Katalon custom keywords. Logic transfers; implementation changes.
Reusable components
Tosca business parameters rebuild as Katalon test objects and keyword libraries.
Leave behind
Tosca Commander configs
Workspace settings, execution lists, and Tosca-specific integrations replaced by Katalon's native equivalents.
Model maintenance
Stop maintaining Tosca models entirely. Katalon's approach removes this overhead layer.
Outdated / redundant tests
Migration is an opportunity to retire tests that are stale, redundant, or no longer cover live features.