What you can export from Lucidchart and what stays behind
Per-document exports are available on every Lucidchart plan, and the formats cover most of what a renewal, pricing change or data residency review needs: PDF, PNG, JPEG, SVG, Visio (VSDX or VDX), JSON and CSV. Comments, notes and some other content do not come with those files, so a team preparing to leave should inventory what each document carries before exporting anything. The bulk export works differently. It produces a .LAF file that can restore documents only within Lucid. That protects against accidental loss inside Lucid, but it does not give you a copy you can open in another tool. Start by listing the diagrams, their owners and any content that lives outside the diagram canvas, then plan a separate capture for that material.
Treat the per-document files as your portable copy and test them before any deadline. Export a representative set of diagrams to VSDX, open them in Visio or draw.io, and compare shapes, connectors, text and layout against the originals. The JSON and CSV outputs are the closest thing to structured data you will get, so decide early whether shape data needs to be captured in those files. Record which files were exported, when, and from which account, because an auditor or a successor team will ask. Confirm with Lucid in writing what export options and retention commitments apply to your plan, since terms can change. Lucid's help center page on the EU Data Act sets out how the company addresses data portability, and it is worth reading alongside your contract.
Which Lucidchart data exports, by format and method
This table lists each Lucidchart export format and the bulk backup, with where each one runs and what it can restore. Read the per-document rows as files you can open outside Lucid, and the bulk row as a backup that only returns to Lucid. Confirm any size or count limit in Lucid's help center before planning a large export.
| Export format or method | Where it runs | What it keeps or restores | Notes for planning |
|---|---|---|---|
| PDF, per document | Lucidchart editor, per document | Rendered view of the diagram | Comments and notes are not part of the export; confirm this in Lucid's help center |
| PNG or JPEG, per document | Lucidchart editor, per document | Raster image of the diagram | Good for documentation, but shape data and links are lost |
| SVG, per document | Lucidchart editor, per document | Vector image of the diagram | Useful for wikis; check how text and fonts render in your target tool |
| Visio VSDX or VDX, per document | Lucidchart editor, per document | Editable diagram for Visio or draw.io import | Confirm how shapes and stencils map before a full migration |
| JSON, per document | Lucidchart editor, per document | Structured diagram data | Needs parsing work to reuse; not a direct import path into draw.io |
| CSV of shape data, per document | Lucidchart editor, per document | Shape data as rows and columns | Captures data fields, not the drawing itself |
| Bulk .LAF export | Lucid account-level export | Documents that restore only within Lucid | Not readable by draw.io or Visio; keep it only as a Lucid-side backup |
What does not come out with an export, and the workaround for each
Per-document exports keep the diagram, but several Lucid features stay behind. Each card names one gap, the workaround that captures it before the source is retired, and what to confirm in your own account. Assign an owner to each item in the cutover plan.
Comments and threads
Lucidchart's per-document exports to PNG, JPEG, SVG, PDF, Visio, JSON and CSV carry the diagram content, and comment threads, replies and resolution status are among the items the export leaves out. Before you retire a document, open its comment panel and copy each thread that matters into the decision log or the wiki page that owns the diagram. Record the author, the date and the shape each comment refers to, so the context survives. Confirm in your own account how many threads exist per document, since large review histories take longer to transcribe.
Notes attached to shapes
Notes that sit alongside shapes or pages are content that per-document exports do not reliably carry, so the explanation behind a diagram can disappear while the drawing survives. Open each exported file in a viewer and search for a sample of note text to test the output. Where a note is missing, move it into the shape label, a text box beside the diagram or a linked table in draw.io, so the explanation travels with the drawing. Confirm which note fields your Lucidchart version exposes and how each one appears in the output.
Data links to external sources
Data links, which tie shapes to rows in an external sheet or dataset, are a Lucid feature that exports do not keep as live connections. A shape-data CSV gives you the values but not the link that refreshes them. Export the CSV, store it beside the diagram with a stable shape ID column, and rebuild the mapping in draw.io or in the source sheet itself. Confirm in your Lucid account which link types you use and how each one refreshes, because the rebuild effort depends on that detail.
Shape data beyond the flat CSV
The shape-data CSV covers the values stored on each shape, but it is a flat table. Grouping, container relationships and styling applied in Lucid may not carry over with the values. Check a sample document by comparing several shapes in the CSV against the canvas. Keep the CSV as the record of values, and reapply grouping and styles in draw.io. Confirm the column layout your account produces, since it can differ between documents that use different shape libraries.
Interactivity and embedded images in Visio
If you move a diagram through Lucidchart's VSDX export into draw.io, expect some differences. The draw.io documentation warns that imported Visio diagrams may look different from the original, may lose interactive behavior and do not import embedded EMF images. Export a sample, open it in draw.io and compare it side by side with the original. Replace each EMF image with a PNG or SVG of the same content, and log every diagram that needed manual fixes so the effort is visible in the cutover plan.
Bulk .LAF backup restores only in Lucid
The bulk export produces a .LAF file, a format unique to Lucid that restores documents only within Lucid. A LAF archive therefore preserves your content for retention but cannot seed a draw.io workspace. Plan the move around per-document exports to VSDX or SVG plus shape-data CSV, and keep the LAF archive until your retention policy allows deletion. Confirm with your Lucid administrator who can run the bulk export and what scope it covers on your plan.
Choosing an export route for each document type
Diagrams that people will keep editing need an editable format. Lucidchart can export individual documents to Visio as VSDX or VDX, and these are the files your editors can reopen and continue working on. draw.io imports .vsdx files, so this route is the one to test first when you move diagrams into a self-hosted editor.
- Choose VSDX first: VSDX is the modern Visio format and the one draw.io documents as an import path, so use VDX only when a downstream tool requires it.
- Expect layout drift: draw.io warns that Visio imports may look different from the original, so check connectors, spacing and text wrapping on every page.
- Plan for interactive loss: interactive behavior may not survive the import, so list any hyperlinks, hover behavior or shape actions before you export.
- Check embedded images: draw.io does not import embedded EMF images, so re-insert those pictures or export them separately.
- Log comments and notes: the export does not carry comments or notes, so record them in a separate log for each document.
Before you move a complex diagram, open the exported file in draw.io and compare it side by side with the Lucidchart original.
Some diagrams are needed as fixed records for approval, review or archive. Lucidchart exports individual documents as PDF, PNG, JPEG and SVG, and each output keeps the visual appearance at the moment of export. These files are for reading and retention, so they do not give your team back the shapes, connectors or data links that make a diagram editable.
- PDF for approvals: a PDF gives reviewers a fixed page, but you cannot reopen the shapes from it, so keep the editable source alongside it.
- PNG for documents: PNG suits slides, wikis and tickets, and handles text in diagrams well, though it does not scale without losing sharpness.
- JPEG with caution: JPEG is a lossy format, so text and thin lines can degrade. Prefer PNG for any diagram that carries detailed labels.
- SVG for scalable copies: SVG keeps vector geometry, which suits web publishing, but test how your viewer renders fonts before you rely on it.
- Name files consistently: include the document identifier and an export date in each file name so reviewers can match a record to its source.
Ask the records owner or auditor which format they accept as the retained copy, and confirm the retention rule before you export a large set.
Many Lucidchart documents carry data in their shapes, such as owners, system names or process steps. Lucidchart exports this data per document as JSON and as a shape-data CSV, and both are available on every plan. These outputs suit migration into a database or a register, but they describe the content and not the drawing, so they do not replace a visual export.
- Shape data as CSV: the CSV gives you a flat table of the data linked to shapes, which opens in a spreadsheet and imports cleanly into most self-hosted databases.
- Structure in JSON: JSON describes the document in a machine-readable form that a developer can parse. Confirm the schema with Lucid before you build a pipeline on it.
- Layout stays out of the table: positions, colors and connector routes do not come through as usable diagram data, so pair the CSV with a visual export of the same document.
- Choose a key field: decide which shape-data field identifies each row in your target store so every record stays traceable to its source diagram.
- Test with one document: run a single document end to end and confirm that every linked field appears and that multi-line values survive the trip.
Confirm the exact field layout of both files with Lucid in writing before you plan a bulk migration around them.
Lucid offers a bulk export that produces a .LAF file. This format is unique to Lucid and restores documents only within Lucid, so it works as a vendor-side backup and not as a route out of the platform. For an exit, you need the per-document exports described in the other tabs.
- Restores only into Lucid: the .LAF file does not open in draw.io or Visio, so it cannot seed a self-hosted editor.
- Keep it as a fallback: if you may need to return to Lucid, the bulk file is the restore path there, so store it with that purpose in mind.
- Build the portable copy separately: take VSDX, SVG and CSV exports for each document, since those are the files that move to other tools.
- Inventory before you export: list every document, owner and folder, then check that each one has a matching export in each route you need.
- Protect the archive: a bulk file holds full document content, so apply the same access controls you use for the source system and confirm retention periods with your records team.
Review Lucid's EU Data Act guidance and confirm with Lucid which content the bulk export includes before you treat it as complete.
Running a complete export in the right order
This sequence turns a scattered set of Lucidchart documents into a dated archive you own, with editable and fixed copies, the comments and notes Lucid leaves out, and a checked sample that proves the files are usable before the Lucid account closes.
Inventory documents and their owners
Before exporting anything, list every Lucidchart document your organization needs to keep, with its owner, folder or team, and whether it is still in use. Include documents shared with you by people outside your team, because those files often sit under a personal account. Record the list in a spreadsheet that your records or IT team controls. The step is done when every document has a named owner and a keep, archive or discard decision, and someone outside the project has reviewed the list.
Run the bulk LAF export
Start with Lucid's bulk export, which produces a .LAF file. Treat this file as a Lucid-only archive: it is kept for record purposes and can restore documents inside Lucid, but draw.io cannot open it, so it does not replace the per-document exports in the next step. Store it in your own storage with a checksum and a note of the export date and account. The step is done when the file is saved outside Lucid and a second person has confirmed it opens in Lucid's restore path, if your plan still allows that check.
Export each document to editable and fixed formats
Export each inventoried document individually. For editable copies, use Visio (VSDX or VDX) for drawings that will continue in draw.io or Visio, and JSON or CSV where the data itself matters. For fixed copies, use PDF, PNG or SVG so that the appearance is preserved for audit and reference. Name files with the document ID, a version date and the format, and keep the two sets in separate folders. The step is done when every inventoried document has at least one editable and one fixed file.
Capture comments and notes separately
Lucid's per-document exports do not carry comments or notes, so record them by other means. Open each document with comments, export the discussion from the Lucid interface where your plan allows it, or copy the text into a dated review file. Keep the record next to the matching diagram file and note who wrote each comment and when. The step is done when every document flagged for comments has a companion record, and the owner confirms that no open decision lives only in a comment thread.
Store the files in your own storage
Move the LAF archive, the editable files, the fixed files and the comment records into storage your organization controls, such as an on-premises file server, a self-hosted Nextcloud instance or your own object store. Apply the access rules that the original documents had, and do not leave copies on personal devices. Verify that the folder structure matches the inventory from the first step. The step is done when the storage location, access group and retention owner are documented and the Lucid export folder is no longer the only copy.
Verify counts, layout and shape data
Compare the exported files against the Lucid originals. Check that the number of files matches the inventory, that page counts and layouts look right in the fixed exports, and that shape text and linked data are present in the JSON or CSV output. When you open a VSDX file in draw.io, expect some rendering differences, which the draw.io documentation describes for Visio imports. Log every mismatch against the document ID. The step is done when every mismatch is either fixed or accepted in writing by the document owner.
Sign off a sample with a named owner
Choose a sample of files that covers each document type, each owner and each export format, and ask a named owner to open them from your storage without Lucid. The owner checks that the diagram, comments and data are readable and that the file names and dates are correct. Record the sign-off with the owner's name, the date and the sample list. Ask the owner to confirm the sample size with the project lead before starting, and state the sampling method in the record. The step is done when the signed record is filed with the archive.
How to verify an export before you rely on it
Treat every export as unproven until you have opened it and compared it with the source. Before any Lucidchart document leaves your control, pick a representative set of diagrams, including one with multiple pages, one with dense shape clusters, one with custom shape libraries and one with text in grouped or nested containers. For each, export to the formats you plan to keep, then confirm that each file opens in its intended tool without errors. A file that opens in a viewer but fails in the editor you plan to use is not a usable copy. Record the Lucidchart document ID or title, the export format and the date next to each file so the set can be traced later.
Compare structure first, then content. Count the pages in the original and in the exported file, and confirm the number of shapes and connectors on each page matches what you see in Lucidchart. Check that text and labels survive, including line breaks, font sizes, and text inside shapes that are grouped or layered. Spot-check connector endpoints, because a diagram can look correct while its links to shapes are broken. For CSV exports, confirm that the shape-data columns contain the values you expect for a sample of rows. Where a count or label differs, note the difference and decide whether it is acceptable before you rely on the file.
Plan for comments and notes separately. Per-document exports do not carry comments or speaker notes, so capture them by another method, such as a written review log, screenshots of comment threads with their authors and timestamps, or a copy of the relevant text kept alongside the diagram. If you later move the diagram to draw.io through Visio, check the result against the draw.io Visio import differences documentation, which warns that rendering can change, interactive behavior may be lost and embedded EMF images are not imported. Confirm which of these apply to your diagrams before you delete the originals.
What to plan before the Lucidchart contract renews or ends
An export only works if the inventory, target and sign-off are settled before the access window closes. The cards below cover the decisions that connect the export itself to the renewal or exit date, and what to confirm in your own Lucid contract.
Start the export inventory early
List every Lucidchart document, folder and owner, then note which diagrams carry comments, speaker notes or shape data you need to keep. Count the documents per team so the export can be scheduled in batches. Start this well before the renewal date, because each document is exported one at a time from the editor and the work grows with the number of files.
Confirm your plan's export options
Ask Lucid in writing which export formats your plan and account type allow, and whether the bulk export is available to your admins. Individual documents export to PDF, PNG, JPEG, SVG, Visio, JSON and CSV, but comments and notes are not part of those files. Confirm also whether your contract or data processing terms give you a defined window to download data after the term ends.
Choose the target format and tool
Decide whether the diagrams will move to draw.io through Visio (VSDX) export or through copy and paste, and whether the output will be kept as editable diagrams or as static images. Visio imports can change layout and drop interactive behavior, so test a representative sample of your most complex diagrams before committing to one route for all documents.
Arrange storage and retention for exports
Exported files are copies that now sit outside Lucid, so they need a home with defined access rules, backups and retention. Decide where the files will live, such as a file share, a Nextcloud instance or the draw.io storage integration you choose, and set a retention period that matches your records policy. Make sure the storage location is inside your own infrastructure before the export starts.
Set the cutover and deletion sequence
Plan when users stop editing in Lucidchart, when the final export runs, and when draw.io takes over as the working copy. Keep Lucid access open until you have verified the exported files, then decide with Lucid how account and content deletion will be handled and confirm the dates in writing. Avoid deleting source documents until a sample has been reopened and checked in the target tool.
Agree sign-off and ownership
Name one owner for the export, one reviewer for each business area and one approver for the final handover. Security or compliance should approve where exported data is stored and who can access it, because exported diagrams can contain architecture or customer information. Record the sign-off in your change system so the export has an audit trail.
Questions buyers ask before exporting Lucidchart data
Can every Lucidchart plan export its diagrams to files?
Yes, individual Lucidchart documents can be exported on every plan, so your tier does not block per-document exports. Each document can be saved as PDF, PNG, JPEG, SVG, Visio (VSDX or VDX), JSON or CSV. The open question is the bulk route. Confirm with your Lucid administrator whether a full-account export is available on your plan, which roles can start it, and what it produces. That answer decides whether the work is a self-service task or a structured project, so get it in writing before you set a schedule.
Do comments and notes survive a Lucidchart export?
No, exports do not carry comments and notes, so the review history stays in Lucidchart. A diagram can export with its shapes intact while the decisions recorded in its comments are lost. If comments hold approvals, design decisions or audit context, inventory them before export and store them in your wiki or ticketing system, then link each exported diagram to its record. Confirm the full list of elements each format omits with Lucid, and test one representative document per format before you rely on the output.
Why can't a Lucid .LAF backup be opened in another tool?
The .LAF file is a Lucid-specific format, and Lucid's bulk export produces it to restore documents inside Lucid. Other diagramming tools, including draw.io, cannot read it. Treat the .LAF as a restore option for Lucid and keep it in your retention archive. For portability, export each document to a documented format such as VSDX or SVG, or to JSON for structured data. Lucid's help article on the EU Data Act describes the export options it provides, and your legal team should read it alongside your contract.
How long does a full Lucidchart export take, and what drives it?
No duration has been published for this, so get a figure from Lucid and from your own test run. The time depends on how many documents you hold, how large and image-heavy each diagram is, which formats you choose, whether shape data must be exported as CSV alongside each drawing, and how many documents need review afterward. Run a pilot on a sample of document types, time it per document, and scale from that measurement across your full inventory. Record the pilot results so the schedule has a basis you can defend.
What does our internal team need to provide for an export?
Your team supplies the access, the decisions and the review. Expect to provide:
- An administrator who can confirm export rights and run the bulk route, if your plan includes it
- A document inventory with owners, so each diagram has a named person who approves its export
- Decisions on target formats and the storage location where exports will live
- A review step for diagrams with comments, linked data or embedded images, which exports can alter or omit
- Sign-off on the final set, with a record of what was exported and what was left behind
Without named owners, reviews stall, so assign them before the export begins.
Can our own engineers export Lucidchart data without outside help?
Yes, a small set of documents can be exported by hand through the per-document export options, and engineers can script handling of JSON or CSV output if you need structured data. The work becomes heavier when you hold many documents, need consistent naming and folder structure, must verify shape data, or must prove what left the platform. Those tasks need a repeatable process, a test log and someone accountable for the result. Decide early whether your team has that capacity, because a half-finished export is harder to recover than a planned one.
What does outside help for a Lucidchart export cost, and what drives it?
DeployOpen works on fixed-scope engagements, with scope, deliverables and timelines agreed in writing before work starts. DeployOpen does not publish a price list, and a quote follows from that written scope. The main cost drivers are the number of documents, the formats required, the amount of shape data and linked content to verify, the storage target and retention rules, and the documentation handed over. Ask for a quote that separates the one-time export work from any optional ongoing retainer for support or later checks.
Which export format keeps diagrams usable if we move them to draw.io?
Visio VSDX is the format most likely to carry diagrams into draw.io, because draw.io imports .vsdx files directly. draw.io also documents a copy-and-paste route for Lucidchart diagrams in its online editor. Expect differences, though: draw.io warns that Visio imports may look different from the original, may lose interactive behavior and do not import embedded EMF images. Pick a sample of complex diagrams, convert them both ways, and compare the results before you choose a route for the full set. The draw.io import formats page lists what each route supports.
How DeployOpen works on this
DeployOpen plans and delivers the Lucidchart export as a fixed-scope engagement agreed in writing before work starts. The work covers the per-document export formats, a gap review of what exports leave out such as comments and notes, and the import path into self-hosted draw.io inside your own infrastructure.
How we scope
- The written scope lists which Lucidchart documents, folders and formats are included in the export.
- We record what the export omits, such as comments and notes, so you decide what to keep elsewhere.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- We run the export and check each document's format, layout and shape data against the original.
- We set up self-hosted draw.io from the official Docker image or desktop app in your environment.
- We test imports of Visio and Lucidchart diagrams and document where rendering or interactivity changes.
How we hand over
- You receive documentation of the export steps, import results and known differences from the originals.
- Diagrams are stored in the storage location you choose, with access and backup configured to your policy.
- We walk your team through the hand-over so owners can maintain the diagram library after delivery.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after hand-over.
- We can plan draw.io version upgrades in your environment and document each change for your records.
- Ask us to confirm any export capability against your own Lucidchart plan and account before scoping.
