All shapes disappear when exporting Lucid documents as a Visio export

Assume there hasn’t been a fix for this in a year because it still happens?

Hey ​@toddbass10,

Thanks for posting in the Lucid Community! Would you mind giving me a few more details about what you are seeing on your end? 

To learn more about exporting shape data please look at this article. You can export shape data as a CSV. The CSV of the shape data associated with your Lucidchart document includes shape names, shape library, text fields, and additional data.

I’m getting the same issue.

When exporting to VSDX or VDX, and then open the file in Visio, the file looses shapes, formatting and data across all the tabs.

This issue was reported 2 years ago, is there any resolution to this yet?

Hi ​@LucasCZ, thanks for adding to this thread and for providing that screenshot. Sorry that you’re having trouble here, but I’m happy to help.

There are a few specific things worth noting when working with exporting your document:

• Try the export in a Chrome Incognito browsing session. This often improves performance by clearing your cache and cookies and disabling your extensions.
• Sometimes issues like this can be related to internet connection speed or network security. Please try the export again on another network, ensuring that you are on a strong, stable connection.

If the issue persists, can you please send a screenshot of the associated Javascript Console output after reproducing the issue? You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).

Thanks for the guidance.

I’ve followed all the steps you suggested:

• Export attempted in Chrome Incognito (no extensions enabled)

• Export tested on a different, stable network

• Issue is 100% reproducible

Unfortunately, the problem persists.

When exporting to VSDX/VDX and opening the file in Visio, the diagram loses shapes, formatting, and embedded data across multiple tabs/pages. This is not a partial degradation — it materially affects the usability of the file.

As requested, I’m attaching the JavaScript Console output captured immediately after reproducing the issue.

This is becoming time-critical for us. We have a customer expecting a fully functional .vsdx file, and exporting to Visio is a documented Lucid feature that we are relying on for delivery. At the moment, the exported file does not meet that expectation.

Could you please advise:

1. Whether this is a known limitation or defect with VSDX/VDX export

2. If there is an ETA or workaround that preserves shapes, formatting, and data

3. Whether this can be escalated given the customer impact and delivery risk

We really need a practical resolution or a clear position on what is and isn’t supported, as this is directly affecting a live customer engagement.

Thanks in advance for your help — happy to provide any additional information if needed.

Hi ​@LucasCZ, thank you for getting back to me with this detailed information.

I believe you have identified a bug, and I have reported this to our development team. I apologize for any disruption and impact to your workflow. I will update this thread with any new information about a fix.

To help our teams take a closer look, could you share a temporary Document Support PIN for this document? This will help me take a closer look at what’s going on. This PIN is safe to post in this thread because it is only accessible by members of the Lucid support staff. You can find steps for generating a Support PIN in this Lucid Help Center article: Generate a Lucid Support PIN. 

Please follow along on this thread for updates, and post any additional questions or concerns below.