Move Into BesTest With an Agent, Not an Import Wizard
Import wizards move rows. They rarely move meaning: folder trees flatten, links between requirements and tests vanish, and someone spends a week re-linking by hand. Handing the export to an agent keeps the meaning.
Everyone remembers their last migration
Export from the old tool. Fight the column mapping. Fix the encoding. Import, discover the folder hierarchy flattened, discover the links did not survive, and accept that traceability starts again from zero.
The links are the part that hurts: they were the actual value, and they are exactly what CSV import loses. That is why "set up my initial state" was one of the first things our beta users tried over MCP instead.
The wizard way
- Export CSVs from the old tool, one per entity type
- Map columns, fix encodings, re-run until it stops erroring
- Watch folder structure and cross-links get lost in translation
- Re-link requirements to test cases by hand, for weeks
The agent way
- Point your agent at the export, or paste the content straight in
- It creates folders, requirements, and test cases through the MCP
- It creates the links between them in the same pass
- Ask "what did you skip and why?" and get an honest answer
One prompt, start to finish
Here is our old tool’s export (test-cases.csv and stories.csv). Recreate the folder structure in BesTest, create the test cases with their steps, create requirements from the stories, and link each test case to its story.- 1
Reads your export, whatever shape it is in
CSV, spreadsheet, markdown, a wiki page you pasted: if your agent can read it, it can migrate it. No column mapping screen, because the agent understands the columns.
- 2
Builds your structure through the MCP
Folders first, then requirements and test cases with their steps, batched so a large library moves in waves you can watch and stop at any time.
- 3
Restores the links, which is the point
The story-to-test relationships in your export become real traceability links in BesTest, so coverage reporting works from day one instead of from "someday".
The result
One of our first beta users set up 20 requirements and 20 test cases, linked, in his first session, without reading a manual. Your starting state stops being a data-entry project and becomes a conversation.
Built by conversation in a first session, with no manual read of the docs.
More prompts to steal
Create our standard folder structure: one folder per product area, from this list.
Here are 15 user stories. Create them as requirements and draft one test case each.
Compare this spreadsheet against what is already in BesTest and import only the new rows.
Scoped to your permissions, granted per user
Your agent acts as you: everything it reads or writes stays inside your Jira permissions. The MCP is in closed beta while we harden it, with GA coming. The request form asks for a few details from BesTest’s Project Settings in your Jira, which is what lets us enable exactly your site and user.
Request beta accessFrequently asked questions
What formats can I migrate from?
Anything your agent can read: CSV and spreadsheet exports, markdown, Confluence or wiki content you paste in, even a plain list in a message. The agent does the interpreting; there is no fixed import template to conform to.
Can it migrate from Zephyr or Xray?
Yes: export from your current tool and hand the files to the agent. Steps, folders, and story links are the things teams most want to survive, and preserving them is exactly what this flow is for. If you are comparing tools first, see our Zephyr and Xray comparison pages.
What about really large libraries?
The agent works in batches, so big migrations move in reviewable waves instead of one blind bulk load, and you can stop, check, and continue at any point. You stay in the loop the whole way.
Will it overwrite what I already have?
Only if you ask it to. The safe pattern is additive: create what is missing, link what is new, and report anything ambiguous back to you instead of guessing. And everything runs under your permissions.
Ready to Get Complete
Testing Visibility?
Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!
Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.
Start Free on Marketplace