Hi Jonathan, welcome to the Community!
For Gliffy and all other add-ons that follow Atlassian's licensing model, licensing entitles you to support and updates. Your existing diagrams and the ability to create new diagrams will still work even if you let your license expire.
However, new versions of Confluence might not be compatible with your now-older version of Gliffy. That's where you really need to be in support!
Theoretically, you could stop paying for everything right now and it would all keep working. For a while. Until browser updates make the older versions not work the way you want, or users start complaining that they're missing features. Then when you go to upgrade Confluence, all your plugins need to be in support as well to entitle you to the latest versions compatible with the latest Confluence.
Personally I think it's less of a headache to just stay up to date on your licensing, but are not forced to stay up to date if you feel like you have a strong enough case not to be.
I installed Gliffy on a Cloud instance, created a diagram, then un-licensed it to see what would happen.
My expectation (based on several years of Server use) is that the .png file Gliffy attaches to the page would be usable even if the Gliffy diagram were not. Here's what I got on the page after de-licensing:
When I checked the page's attachments, I still saw the .png attached, but when I opened it, the file was just a blank image. If on your own instance, you find those .png files actually have content, they should still be accessible even if your license runs out. But for whatever reason (latest version has a bug, can't generate .pngs during a trial evaluation, purposeful removal of the feature from Cloud, etc.) I was unable to see actual content in the .pngs either before or after unlicensing.
The editor definitely stops. Your milage may vary on the .png files.
Yup - that's really my main question, too. :) We're on the Cloud version of Confluence and we're considering switching from licensing Gliffy to a different tool. I want to be sure we're only losing our ability to edit our old diagrams and not losing access to view them in the future.
So for Cloud instances, Gliffy diagrams cannot be archived? We're done with our need for this tool and would like to shut if off. It's almost as expensive as the Confluence license itself. It's the third highest line item on our invoice in terms of price, right after JIRA and Confluence.
We need to stop paying for something we're no longer using. We need to archive our diagrams somehow...
By "if leave it unlicensed" you mean the "Gliffy Confluence Cloud plugin"
To summarize, the steps to migrate from Gliffy to draw.io in Confluence Cloud would be:
I mean Gliffy unlicensed, yes.
The steps are fine, but 1 is "start trial", you don't have to buy it just yet.
As long as all the Gliffy data is stored on the Confluence instances, nothing can be lost. It's just a case of converting it all over. Worst case a diagram doesn't converted, contact firstname.lastname@example.org.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs