What happens to our diagrams if we end the Gliffy license?

[Jonathan Van Schoick]

If we end our Gliffy license, what happens to the diagrams that we've created so far?

Do they switch to a read-only state? Do we lose the data?

[Daniel Eads · Accepted solution]

Updated answer, September 2020

Gliffy in Confluence Cloud now switches over to a read-only state when the Gliffy license is no longer current. An information box appears at the top of your diagrams:

On hovering over the diagram, you'll see that the toolbar on the digram macro only offers fullscreen and embed options:

Creating new diagrams isn't possible with an expired Gliffy subscription in Cloud.

______________________________________________

In Confluence Server, you can still interact with Gliffy as the Server version runs locally. Existing diagrams would still be editable, and you could create new diagrams as well. However, you won't have access to app updates or support from Gliffy without renewing the app's support maintenance license.

Cheers,
Daniel | Atlassian Support

[Jonathan Van Schoick]

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.

[Connie Taylor]

So the answer given is not clear if this true for Cloud

[Daniel Eads {unmonitored account}]

Ah gotcha - I wasn't sure if you meant Cloud or Server and just mistakenly assumed Server. See answer in comment above!

[Mark_Holdread]

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...

[David Benson _draw_io_]

Convert the gliffy diagrams to draw.io and leave draw.io unlicensed. That still gives you the ability to view the diagrams, just not edit them. You can take those and use them in the free online version, if you wished.

[Thomas Guthmann]

@David Benson _draw_io_Can you convert Gliffy to draw.io on Confluence Cloud? I read it's only true for Confluence server version. Can you confirm?

Cheers,
Thomas

[David Benson _draw_io_]

Yes, draw.io cloud has the mass Gliffy import function, as well. If you leave it unlicensed it will act as a viewer the same way server does.

[Thomas Guthmann]

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:

1. Buy draw.io licenses
2. Mass import Gliffy to draw.io
3. Cancel gliffy licenses
4. Cross fingers that nothing is lost.

Right?

[David Benson _draw_io_]

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 support@draw.io.

[Daniel Eads {unmonitored account}]

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.

Cheers,
Daniel

[Connie Taylor]

Is this also true for Confluence Cloud?  Will you lose the diagrams there?

[Daniel Eads {unmonitored account}]

Hi Connie,

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.

[Nisha Bansal]

 What if current documents have gliffy on Confluence and we are migrating to Data Center from JIRA Server/Confluence Server without gliffy on Data Center, post migration what would be the impact on those documents.

[Samie Kaufman - Your Gal at Gliffy]

Hi Nisha! The answer here is similar — as long as you migrate your attachments from server to DC, you should be able to see the diagrams as .png files but not make any edits.

[Nisha Bansal]

But the question here is that we won't be having gliffy in Data Center after migration, so in that case we want to know what will happen to those docs that have gliffy attachments/diagrams in the server currently. 

[Samie Kaufman - Your Gal at Gliffy]

Yes, I see your distinction! If you migrate from Server into an instance that doesn't have Gliffy and choose to migrate the attachments on all your pages, the image attachments would still be accessible. 

Gliffy attaches an image file (.png) and a .Gliffy file for every diagram you add on the page. By including page attachments when you migrate, both files would come to your DC environment. Without Gliffy, you can still see the .png versions of those files. You would not be able to make changes to the files without adding Gliffy. I hope this is a clearer answer!

It sounds like you've decided not to continue using Gliffy already, but if there's anything we can do to keep your business or any feedback you'd like to share about why you plan to stop using Gliffy, please let us know by emailing abryl@perforce.com.

[Nisha Bansal]

Thanks Samie..Yes, that's a clear answer.

Thanks for your help. It's a business decision.