A process map's job is to travel. It ends up in a steering committee deck, in a spreadsheet somebody in finance is modelling against, in a PDF attached to an audit response, and in a link pasted into a ticket. A tool that only renders well inside its own canvas has solved the easy half, because most of the people who need to see a process will never open the application it lives in.
Sapeum exports five ways from one dialog. PDF for documents that leave the building, with a configurable header and a logo footer. SVG for vector artwork that drops into a deck and stays sharp at any size. JPG when somebody just needs a picture. Excel for the process as data. And Raw, for lifting a section out of one process and pasting it into another, which is how a reusable library gets built: map customer onboarding properly once, then paste it into every engagement that needs it.
Five formats, one dialog. Which one you want depends entirely on who is receiving it.
The Excel export is the one that surprises people. It writes one row per step and spreads the hierarchy across columns, so a phase and the steps inside it sit in Level 1 and Level 2 rather than being flattened into a single list. Each row carries that step's executors, its full description, and whether it is a decision point. That is a process you can sort, filter and pivot, and hand to a finance team or an auditor who is never going to look at a diagram.
The same map as rows. The hierarchy survives as columns, so nothing is flattened away.
Comparisons export as a single document holding both versions with the change labels intact, and any drilled-in view of a diagram has a URL that opens at the same place, so a deep link counts as a delivery format too. The pattern worth noticing: the artifact your audience receives should be chosen by what they need to do with it, not by what your tool happens to emit.
Sapeum makes a process map something you can hand to a client, a regulator or a spreadsheet. Try Sapeum.
