Migrate from VivifyScrum

VivifyScrum is shutting down. We built a medium-effort importer so you don't lose your sprints.

This page is the walkthrough. The importer is real, tested against a real 51-item sprint, and respects the limits of what's actually in the VivifyScrum export. Read it through once before you start — there are a couple of things you'll want to know up front.

What gets imported

• Items: title, description, type, priority, points (as estimate), creation date.
• Labels: colour preserved, names mapped 1:1 into your Vibstr project's label dictionary.
• Parent/subtask hierarchy: preserved via Vibstr's parent_item_id field.
• Column → Vibstr status: configurable. Sensible defaults are below.
• Closed items: the original done_at timestamp is preserved.

What does NOT get imported (yet)

We'd rather be honest than oversell.

• Comments: most VivifyScrum exports we've seen have empty comments arrays. If yours has comments, file an issue and we'll bump comment import into the next polish release.
• Worklog entries: the worklog file is accepted by the importer but ignored in 1.18.8. It's a placeholder for future time-tracking work.
• Checklists, events, reviewers: mostly empty in real exports we've inspected. Same deal as comments — file an issue if yours uses them and we'll prioritise.
• Sprint hierarchy: one VivifyScrum sprint maps to one Vibstr project. Vibstr doesn't have a "sprint inside a project" concept — projects ARE the unit. If you've been using sprints as folders, the cleanest path is one project per active sprint.

The 5-step walkthrough

1. Export from VivifyScrum

In VivifyScrum, navigate to your sprint. Use the menu and pick "Export sprint columns" — you'll get a file named sprint_columns_YYYY-MM-DD_HH-MM-SS.json. Optionally export the worklog the same way.

If you also want your Backlog page, that's where it gets unclear — see the Backlog export note below.

2. Sign up for Vibstr

Start your 14-day trial. No credit card.

3. Create a project

In Vibstr: Settings → PROJECT → New project. Pick the Web app template — it gives you sensible categories, areas, and labels to start from. Name the project after your sprint or product.

If your sprint is large, do this on a clean project so the import doesn't tangle with existing items.

4. Upload your exports

Settings → PROJECT → Import from VivifyScrum.

• Upload sprint_columns_*.json. Required.
• Optionally upload the worklog file. Accepted but unused in 1.18.8.
• Hit "Dry run" first. You'll see a preview: how many items, how columns will map to status, how types will map to categories, what labels will be added to your project dictionary. No items are written during dry run.
• Adjust the mappings if the defaults aren't right for your workflow.
• When the preview looks right, hit "Import".

5. Review + adjust mappings

Default column mappings:

Why labels and not statuses? Vibstr keeps status to three values: open / checking / done. Workflow nuance lives in labels — that way the same item can be "in progress" AND "ready-for-test" if reality is messier than a single column allows. See Best practices for the longer argument.

Default type mappings: Task → task, Story → feature, Bug → bug, Defect → bug. Override per-type before you hit Import.

Backlog export

VivifyScrum's backlog export isn't obvious from the menu. We've seen teams unable to find it. If your UI doesn't surface a Backlog export option, here's the workaround:

Use the Vibstr Plan format. Paste a markdown plan describing your backlog items, click Parse, and Vibstr derives items deterministically. Zero AI cost. The format is intentionally minimal — - [ ] {type, area} description lines under a ## Tasks heading, one task per line.

It's not as fast as a JSON export but it gets you to the same place. And once your items are in Vibstr, the canonical plan format works for ongoing planning too — same artifact, same parser, no AI dependency.

Trust signals

We owe you these up front.

• Your data exports as JSON and CSV any time. Never locked in. If you decide Vibstr isn't for you, you walk out with everything.
• BYO Anthropic key. Bring your own API key and we never see your AI bill. Pay us for the workflow, pay Anthropic for the compute.
• 14-day free trial. No credit card.
• We're not VivifyScrum. Different team, different funding model. But here's the thing: we can't promise we'll never shut down either. What we CAN promise is your data exports cleanly. Always.

That last bullet is the differentiator. Every SaaS landing page promises forever. We'd rather promise the exit door stays unlocked.

Closing CTA

Ready? Start your 14-day trial → vibstr.app

Questions? The Quick start covers the first 10 minutes; Plans covers the canonical plan format; Best practices covers the labels-as-stages argument in full.