Sharing & Verification

What exports contain

Data Map Studio can export a map as a .datamap.json file so you can share the structure of a schema with a colleague. Exports contain structure and metadata — they do not contain your data.

• Data Map exports contain structure, not credentials.
• Exports do not include database passwords.
• Exports do not include private signing keys.

dbt project export

In Full, a saved Data Map can also be exported as a dbt project ZIP. The export generates dbt project files from the saved map structure, including sources, staging models, relationship tests, and join models where the relationships can be represented within one dbt target.

dbt exports do not include database credentials or local connection details. Add your own dbt profile before running dbt parse, dbt compile, or dbt build. Cross-source relationships may require staging or mirroring before dbt can join them.

Export Identity

Your Export Identity signs the file. Anyone who receives the file can check the signature to confirm it came from that identity and was not modified in transit.

Trust Codes and Trusted Senders

A Trust Code helps verify that a file was signed by that Export Identity. It does not prove a legal or organizational identity. Compare the Trust Code through a second channel — a call, a video meeting, or another message — before you rely on it.

Trusted Sender means the app recognizes a known identity, so files from that identity are marked as familiar rather than unknown.