Migrating to the new TestOps FAQ - for Non-TestOps customer
This document addresses key questions regarding the migration to the latest version of Katalon TestOps for Non-TestOps customer.
You are considered a Non-TestOps customer if you are using Katalon Runtime Engine (KRE), Katalon Studio Enterprise (KSE), and/or TestCloud, and only use TestOps to manage licenses and users — not for test execution, analytics, or integrations.
Why is Katalon TestOps moving to a new version?
Katalon TestOps is evolving from basic test scheduling and reporting into a full platform that supports quality management across the entire testing lifecycle—covering planning, execution, collaboration, traceability, and release readiness. This is not a change to the core product, but a shift to better support how modern teams scale and collaborate.
To support this, we’re moving to a user-based licensing model that:
- Allows teams to collaborate without quota limits
- Matches how TestOps is used day-to-day
- Simplifies budgeting and scaling as teams grow
- Offers improved role-based access and audit tracking
- Prepares your investment for future features
This update is designed to help your team scale, collaborate, manage quality more effectively, and unlocks more value as TestOps expands its capabilities.
I only use KSE, KRE, or TestCloud (Non-TestOps customer)—what does this mean for me?
Katalon TestOps is no longer available for free. However, if you're only using Katalon Studio Enterprise (KSE), Katalon Runtime Engine (KRE), or TestCloud, you will still need to access the TestOps portal to manage your licenses and users for these products.
To support this, Katalon provides one (1) complimentary Katalon Account Manager access. This allows limited access to essential license and user management features—without requiring a full TestOps subscription.
This applies to:
- Organizations that only purchase KSE, KRE, or TestCloud
- Organizations that are currently using only these products
What is exactly Katalon Account Manager?
The Katalon Account Manager is a default administrative access automatically assigned to certain users in organizations that do not have a full TestOps subscription but still use Katalon products such as Katalon Studio Enterprise (KSE), Katalon Runtime Engine (KRE), or TestCloud.
-
This access is provided only to licensed users of KSE, KRE, or TestCloud who do not have a full TestOps subscription.
-
It allows access exclusively to license and user management within the TestOps portal—not to test execution, reporting, or analytics features.
What can the Katalon Account Manager do?
The Account Manager has access to the following account and workspace setup features:
- Manage the Account: Update account information, branding, and contact details.
- Structure the Organization: Create Organizations and Sub-Organizations.
- Manage Licenses: Assign, reassign, and monitor license usage across users and workspaces.
- Add and Manage Users: Invite users, assign product access, and define business domains.
- Configure AI Services: Enable and manage AI-based capabilities where supported.
- Manage Select Katalon Studio (KS) Settings: Access and configure certain KS-related options, though not all KS features are within their control.
- Configure Platform Settings: Set up IP whitelisting, custom domains, authentication options, and other workspace-level configurations.
This access ensures the customer can operate and manage user-level functions for Katalon Studio Enterprise and related tools without a TestOps subscription.
Can this Katalon Account Manager access everything a TestOps Admin can?
No, the Katalon Account Manager does not have the same access as a TestOps Admin. Their permissions are limited to managing account-wide settings (such as organization/user management, billing, and licensing management). They cannot access TestOps projects, dashboards, test results, or system integrations.
Can the Katalon Account Manager access project-related features in TestOps?
No, the Katalon Account Manager cannot access or manage features related to test activities in TestOps. Their access is limited to account-level settings such as organization/user management, billing, and licensing management . TestOps-specific functions—like test planning, execution, result analysis, or integrations—are not part of the Account Manager’s permissions.
How is the Account Manager selected?
By default, this access is granted to one of the active KSE licensed users in the account. It is automatically assigned during the initial setup phase or licensing assignment.
Can this access be transferred to someone else?
Yes. However, this change must be made by our Support team. Please contact our Support team at: support@katalon.com with the name and email of the new user you wish to designate.
What will happen to my Account Manager access if I later purchase Full TestOps?
Once you purchase Full TestOps, the Account Manager role will no longer be used to manage users, organizations, or licenses. Instead, administrative task, such as managing user roles, system settings, etc, will be handled through the TestOps Admin module.
What features will definitely change in the new version?
The table below outlines the features and functions that will either change in the new version or are not currently planned for future development.
| Licensing & Roles | Legacy | Current (New version) |
|---|---|---|
| License model | Quota-based | Seat-based |
| User roles & Permissions | Account Owner, Account Admin, Account Billing Manager, Org Owner, Org Admin | Account Admin |
| Project Owner | Project Admin | |
| Project Admin | Project Admin, Test Lead | |
| Account Member, Org Member | User (can only see their own profile) | |
| Admin, Member | Test Lead |
| Integrations Note: Integrations are no longer available for free on the new version. A Full TestOps license is required to access all integration-related features. | Legacy | Current (New version) |
|---|---|---|
| Integration Scope | Project-level (each project can define its own GitHub connection) | Account-level (one connection per GitHub instance shared across projects) |
| Connections | Allows multiple connections to the same GitHub URL per project | One connection per GitHub base URL, usable across branches |
| WebHooks | Not used | Required – auto-created per project in Gen3 |
| Katalon Recorder Backup | Yes | No |
| AWS CodeCommit Integration | Yes | No |
| Reporting | Legacy | Current (New version) |
|---|---|---|
| [Widget] Run Frequency | Yes | No |
| Test runs comparison | Yes | No |
Is there a price different between the two versions?
Pricing depends on your team’s usage. The new seat-based model replaces usage-based pricing to better support growing teams with added control, security, and collaboration. It also helps reduce quality management efforts by automating test case generation with built-in AI, improving coverage and traceability while saving time on test creation and maintenance.
Costs vary but are designed to be fair and scalable, with generous migration terms to ease the transition.
Please reach out to us at: success@katalon.com if you have any questions or concerns regarding our pricing policies.
Will I be forced to upgrade to the latest version now?
No, but eventually, upgrading depends on your account’s technical readiness and your team’s needs. Migration will be recommended by your success manager only once all the features you currently rely on are available in the new version.
We aim to ensure the transition won’t disrupt your existing workflows. That’s why migration will only proceed when your essential features are fully supported. The team is actively working to close any gaps, and your success manager will keep you informed throughout the process.
How will our Success Manager assess migration readiness?
Ensuring Technical Compatibility
Before migration, we’ll ensure that the new TestOps platform supports everything your team relies on in Legacy TestOps:
- Feature Compatibility: We’ll review your current usage to confirm there are no dependencies on features not yet available in the new TestOps.
- Custom Domain: If your team uses a custom domain, we’ll validate its uniqueness and ensure it’s available for your new TestOps workspace.
Reviewing Licensing and Contracts
To ensure a smooth transition:
- License Conversion: Our team will assist in updating your Legacy TestOps licenses to the new seat-based model.
- Contract Review: We’ll review any existing contracts to determine whether they need to be consolidated or adjusted, including aligning license end dates as appropriate.
- License Type Audit: Any outdated license types (such as Legacy TestCloud) will be identified and updated as necessary.
Final Checks and Scheduling
Once all prerequisites are met:
- Migration Window: We’ll coordinate with you to select a preferred migration time and reserve it on our internal calendar.
- Time Zone Coordination: Your time zone will be noted to ensure proper coordination with our teams.
- Formal Request Submission: We’ll manage the internal submission process to officially initiate your migration.
Preparing Your Team
We’ll ensure your team is fully prepared for a successful transition:
- Pre-Migration Training: Your Customer Success Manager (CSM) will provide guidance, training, and documentation to help your team understand what to expect.
- Team Coordination: We’ll inform our support, engineering, and product teams so they’re aligned and ready to assist throughout the process.
Executing the Migration
When migration begins:
- Setup: We’ll update licenses, migrate user and integration configurations, apply authentication settings, and complete any other necessary setup steps.
- Verification: Our internal team will test and validate your new TestOps environment to ensure everything works as expected.
- Onboarding Support: Your CSM will walk you through your new TestOps workspace, ensuring a smooth and confident transition.
My company owns several accounts and multiple organizations, what will happen to them when I migrate?
- If you have only one account:
- Your existing organizations will remain as they are. All existing organizations, users, and licenses will stay intact within that same account.
- If you have multiple Accounts, you have two options:
- Option 1: You can merge your existing all Legacy Accounts into a single new Account
- Option 2: You may choose to keep your all your Accounts separate. In this case:
- Each Legacy Account will be migrated to its own independent new Account.
- These new Accounts will operate entirely independently — no shared data, licenses, or centralized administration.
How does the new version support SSO and why does it matter for EU customers and small teams?
Katalon does not provide built-in MFA directly. However, once SSO is enabled, customers can enforce MFA through their own Identity Provider (IdP) (such as Okta, Azure AD, etc.).
In the new version, SSO (Single Sign-On) is supported for all paid customers, including:
- ✅ TestOps customers (even with just 1 TestOps license).
- ✅ Non-TestOps customers (such as KSE, KRE, or TestCloud customers)
Many EU customers and small organizations need MFA for regulatory compliance (e.g., GDPR).
In the new version, even small customers without Ultimate plans can achieve MFA by:
- Enabling SSO (available for all paid accounts).
- Enforcing MFA at their SSO/IdP level.
This allows small EU teams to meet compliance requirements without needing to upgrade to Ultimate.
Our team is interested, can I sign up for this migration?
If your team is interested in migrating, please contact us at: success@katalon.com. We’ll review your account to ensure eligibility and confirm that the migration won't disrupt your workflow. Once confirmed, we’ll guide you through the next steps. Migration can’t proceed until eligibility is verified.