What Happens When Your Trial Ends
When a QAM Hub trial ends, your data stays. Every project, test case, checklist, run, report and attachment remains exactly where it is, and the workspace is held until the Organization Owner chooses a plan. Your test documentation also stays portable: test cases and checklists can be exported to CSV after the trial has ended, so the library you built is yours whatever you decide. Subscribing reopens the workspace in the state you left it, with the same users, projects and integrations.
What the trial is#
Every new organization starts on a 30-day free trial with no card required. The trial runs on the Advanced plan, so everything in the product is switched on while you evaluate it. If you arrived from a plan link on the pricing page, that plan is pre-selected for the moment the trial ends. It is a default rather than a commitment, and the Owner can change it in Billing at any point.
A trial workspace comes with allowances sized for an evaluation with real data: 10 users, 5 projects, 1,000 test cases and 5 GB of storage, with test-automation report attachments kept 14 days and AI included subject to fair use. All of them are shown against your current usage in Billing, under Usage. They lift when you subscribe: projects and test cases become unlimited, storage grows with every paid seat, and automation media is kept 30 days on Standard or 60 days on Advanced.
The countdown#
A banner at the top of every page counts the trial down from day one and is visible to every member. It reads "Trial ends in N days", turns amber in the last seven days, and becomes "Trial ends tomorrow" and then "Trial ends today". The Owner gets a Subscribe button on it, an admin with shared billing access gets View billing, and everyone else is pointed to the Organization Owner.
After the last day#
- Members see a lock screen headed Your workspace is locked, confirming that projects, test cases, runs and reports are safe and untouched.
- Everyone keeps their account and can still sign in. The workspace itself waits for a plan.
- Test cases and checklists can still be exported to CSV. Your test documentation does not become hostage to a billing decision.
- The Organization Owner can open Billing, choose a plan, subscribe through Stripe, or request a renewal from the QAM Hub team.
- As soon as the subscription is active, the workspace opens again with everything in place.
What the export carries is the test library: suites, cases, steps, expected results, custom field values, and your checklists with their columns. What it does not carry is execution evidence, which is the same limitation every CSV export in this category has. Run results, comments, attachments and history live in the workspace and come back with it when you subscribe. If you need those in a file, produce the reports while the trial is still running.
What to do in the last week of the trial#
Three decisions, in this order.
Count the seats you actually need. A paid seat is a person who creates or edits. Anyone who only reads results takes a free viewer seat, and you get one of those with every paid seat. Teams over-count here by including the product manager and the two developers who never open a test case.
Decide between Standard and Advanced. This is the decision the trial exists to answer, because you have been on Advanced the whole time. Look at what your team actually used. If you wrote cases, ran them, imported Playwright or Cypress results and filed bugs in a tracker, Standard covers it. If you leaned on Release Readiness, quality and coverage analytics, scheduled report delivery, publishing traceability into Jira, the knowledge base for AI context, SSO or audit logs, those live on Advanced. The full split, with current prices, is in Plans, Seats and What Each Plan Includes.
Finish the work that needs a live workspace. Imports run inside the workspace, so complete any migration from another tool while the trial is on. The same applies to reports: if someone in your team needs a PDF of coverage or execution results for a review, generate it before the last day. See Importing and Exporting Test Cases via CSV.
Subscribing#
The Owner subscribes from Billing in the organization settings: choose Standard or Advanced, choose monthly or yearly, set the seat count, and pay through Stripe. Billing starts at checkout and the trial allowances lift straight away, which is why most teams subscribe towards the end of the trial rather than at the start of it. If you need more evaluation time instead, the Owner can request a renewal from the same page and the QAM Hub team will get back to you, so it is worth asking a few days ahead.
Continuing on Standard#
Since the trial runs on Advanced, moving to Standard is worth a minute of planning. Everything you created is kept. Advanced-only capabilities are switched off rather than removed, and they come back exactly as they were if you move up later.
- Scheduled email reports. The schedules and their recipient lists are kept and paused, so upgrading later resumes delivery without rebuilding them. Saved report setups themselves stay available on Standard.
- Tracker integration. Creating and linking issues from a run, and refreshing issue status back from Jira, GitHub, GitLab and Linear, all work on Standard. What Advanced adds is the outbound direction: traceability and bug provenance published onto Jira issues, and test cases mirrored as GitHub issues. Your sync configuration is kept either way.
- Advanced analyses. Release Readiness snapshots you already saved stay readable on Standard. Quality and coverage analytics, audit logs and Agent Flows history are kept in place and become available again when you move to Advanced.
- Knowledge base documents. They are kept, including the files themselves, and they count towards your storage while they are there.
- Sign-in. Google SSO and organization-wide 2FA enforcement are Advanced features, so before moving to Standard make sure everyone has a working password sign-in and their own two-factor authentication set up.
Retention works in your favour on this move: automation videos and traces are kept 14 days during the trial and 30 days on Standard.
If you need more time to decide#
The workspace waits. There is no automatic cleanup and no deadline attached to your data: test cases, suites, checklists, runs, requirements, reports, manual attachments and library assets are kept until you come back, and test-automation videos and traces follow their normal retention schedule. Meanwhile your test documentation stays exportable, so a decision that slips a quarter costs you nothing. Whenever the Owner subscribes, the workspace opens again as it was.