Hi everyone,
Our company is in the process of decommissioning Gliffy, so we need to migrate a large number of diagrams from Confluence to Miro. Because of this, finding a way to export diagrams in an editable format has become quite urgent.
According to the Gliffy documentation, the editor should support exporting diagrams as SVG (and in some cases as .gliffy), but in our environment I only see the following export options:
PDF
PNG
JPG
There is no option to export as SVG or Gliffy.
My questions are:
Is SVG export unavailable in certain versions of Gliffy or Confluence?
Is there an admin setting, configuration, or feature that enables SVG export?
Is there a compatible app or workaround that allows exporting diagrams in SVG or another editable format?
Has anyone successfully migrated Gliffy diagrams from Confluence to Miro while preserving editability?
If SVG export is not available, what would you recommend as the best approach for migrating hundreds of diagrams without having to recreate them manually?
Our goal is to preserve as much of the diagram structure as possible (shapes, connectors, text, etc.) rather than importing static images or PDFs.
I've attached a screenshot of the export options currently available in our environment.
Any advice, workarounds, or migration experiences would be greatly appreciated.
Thank you!
Some questions as SVG is supported.
Thanks for your response!
I'll first confirm whether we're running Confluence Cloud or Data Center/Server, as well as the version of the Gliffy app installed in our environment.
We only have PDF, PNG, and JPG available as export options, which is why I was wondering if SVG export had been disabled or wasn't supported in our setup.
I'll also contact Gliffy Support if everything looks up to date.
Thanks for pointing me in the right direction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Oscar — quick disclosure first: I work on diagram.now, one of the Confluence diagram apps, so please read the app mention below as coming from a vendor. The rest is general.
One thing that hasn't been covered yet: in Gliffy, PDF/PNG/JPG are the page-level export options (the "..." menu on the rendered diagram). SVG and .gliffy exports live inside the Gliffy editor itself — open the diagram to edit, then use File > Export there. Since your thread is tagged Confluence Cloud, that editor-level export is usually where SVG shows up. If it's still missing once you're in the editor, then it's down to your Gliffy edition/version, and the earlier advice to check that and contact Gliffy support is the right call.
On migrating hundreds while keeping them editable: Arek's draw.io route (Gliffy mass-import -> export -> into Miro) is a solid plan. The two places fidelity usually breaks are (1) connector routing and grouped shapes, and (2) text inside shapes vs. free-floating labels. I'd validate on your 5-10 most complex diagrams first, before committing the whole set, rather than on the simple ones.
If it turns out not everything is going to Miro and some diagrams stay documented in Confluence, any Gliffy-importing Confluence app can convert those in place and keep them editable — draw.io/diagrams.net does this, and so does diagram.now (imports Gliffy/Lucidchart/Visio, exports SVG/PNG/PDF): https://marketplace.atlassian.com/apps/523472243/diagram-now-flowchart-uml-bpmn-erd-mind-map?utm_source=community&utm_medium=answer . For the parts heading to Miro, though, the draw.io path above is likely your most direct bet.
Happy to help think through the validation step if it's useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Oscar Salas Cortés
I have a wild idea.
During the migration to the cloud, I switched on Draw.IO
If you temporarily have draw.io available in your Confluence instance, you can leverage its native Gliffy mass-import tool to convert entire spaces at once.
Take a small representative sample of Gliffy diagram, Export/download the Gliffy source diagram. Import it into draw.io / diagrams.net
Export from draw.io as VSDX.
Import the VSDX into Miro and validate how much structure is preserved.
If that's too hard then it will be the best to contact with Gliffy and Miro support, they can guide you
Best,
Arek 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arek,
I really appreciate you sharing this approach.
I'll discuss it with our Atlassian administrator to see if temporarily installing diagrams.net is a feasible option in our environment and whether it could help with the migration.
Thanks again for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or convert to draw.io and then use the draw.io plugin in miro, https://miro.com/marketplace/draw-io/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.