Import your Miro tree into Outcomify with a screenshot

You've decided to move your Opportunity Solution Tree out of Miro and into a purpose-built tool. The catch: there's no clean export. Miro gives you an image, not a structured tree — so the obvious path is retyping every node by hand.

There's a faster way. Take a screenshot, hand it to an AI assistant, and let it rebuild the tree in Outcomify for you through the MCP server. A multimodal model like Claude can read the structure straight off the picture and recreate it node by node.

What you'll need

• Your Miro OST open, and a screenshot of it (legible — see the tips below).
• Outcomify connected to a multimodal assistant via the MCP server. The setup guide takes about two minutes. For an import you'll want to grant write access — or let the assistant create drafts you approve.
• An empty tree in Outcomify to import into (or let the assistant create the nodes under one you point it at).

Step by step

1. Capture the board. Screenshot your OST so the hierarchy and the text on each node are readable. For a big board, take a few overlapping screenshots rather than one zoomed-out blur.

2. Connect and point at a tree. With the MCP server connected, tell the assistant which Outcomify tree to build into.

3. Hand over the screenshot and ask:

"Here's a screenshot of our Opportunity Solution Tree from Miro. Recreate it in Outcomify under the Activation tree, preserving the outcome → opportunity → solution → assumption hierarchy and the labels."

The assistant reads the image, works out the structure, and calls the MCP tools to build it — creating the outcome, hanging opportunities beneath it, solutions under those, and assumptions at the leaves. Because Outcomify enforces the hierarchy, the result is a real tree, not a pile of sticky notes.

4. Review and tidy. AI gets you most of the way; you do the last mile. Check the node types are right (the occasional opportunity reads like a solution), fix any labels the screenshot rendered fuzzily, and add the structure a picture can't carry — status, owners, evidence.

5. Keep the original as a reference. Attach the Miro screenshot to the outcome node so there's a record of where the tree came from.

Tips for a clean import

• Legibility beats completeness in one shot. Three readable screenshots import better than one unreadable one.
• Prefer drafts for big trees. Grant read-only and let the assistant propose nodes as drafts — then approve the whole import in one review pass instead of undoing mistakes.
• Go branch by branch if your board is enormous — import one outcome's subtree at a time and check each.
• Trim as you go. Migration is a good moment to drop the stale opportunities every long-lived Miro board accumulates.

Why bother

A tree stuck in Miro is a picture. The same tree in Outcomify is something your team can maintain continuously — track assumptions, see version history, search across trees, and get AI summaries of what changed. The screenshot is just the on-ramp.

Start a free tree, connect your assistant, and bring your Miro board across.