How to export your data from Make

Make lets you export individual automations (scenarios) as "blueprint" JSON files, one scenario at a time, directly from the scenario builder; there is no official one-click export of your whole workspace, connections, or data store contents.

Formats: JSONPlan: Any plan (blueprint export/import is a scenario builder feature, not gated by subscription tier in the docs)Role: Anyone with edit access to the scenario in the workspace

✓ Verified against Make's official documentation, September 2026

Step by step

1Open the scenario you want to export in the Make scenario builder.
2Make sure the scenario is saved and all modules are configured correctly.
3In the upper right corner of the scenario builder, click the three dots (...) menu.
4Choose 'Export blueprint'.
5The blueprint downloads to your device as a .json file, named after the scenario (e.g. 'New prospect notification.blueprint.json'), or after its modules if the scenario still has the default 'New scenario' name.
6Repeat for every scenario you want to back up or migrate — there is no bulk/workspace-wide export in the documented feature.
7Optionally, instead of downloading a file, click the three dots > 'Copy blueprint to clipboard' to copy the scenario as JSON text for pasting elsewhere.

What the export includes

✓Scenario modules and their order/flow
✓Module settings and configuration
✓Mapped values between modules

What it doesn't include

✗App connections/credentials — these are not exported and must be recreated manually after import
✗Scheduling settings — the docs indicate you reconfigure scheduling after importing a blueprint
✗Data store contents (records stored in Make Data Stores are not part of a scenario blueprint)
✗Execution history/logs
✗A single workspace-wide export of all scenarios, connections, and settings at once

Before you start

⚠Export/import is per scenario — there is no built-in bulk export for an entire workspace or all scenarios at once
⚠Imported blueprints must be under 2 MB; if the blueprint exceeds the scenario size limit you won't be able to save it and will see an error
⚠Importing a blueprint into a scenario you're already editing (with unsaved changes) will discard those unsaved changes — Make recommends creating a new scenario first
⚠After importing, you still have to manually re-create/select connections for each module before the scenario will run
⚠The exported file is auto-named after the scenario (or its modules if untitled), so rename files yourself if backing up many scenarios to keep track of them

Where to take your data

Free and cheaper tools that can take a Make export. See all Make alternatives →

n8n

Alternatives Make vs n8n

Make blueprints are proprietary JSON tied to Make's module/app IDs, so they can't be imported directly into n8n's workflow JSON format. You'll need to manually rebuild each automation's logic (triggers, steps, mappings) as an n8n workflow using the exported blueprint as a reference.

Pipedream

Same limitation as n8n: Pipedream doesn't accept Make's blueprint JSON as-is. Use the exported blueprint as a spec/checklist of modules and field mappings while rebuilding the flow as a Pipedream workflow.

Make Free

If you're just moving between Make accounts/organizations (not away from Make), blueprints import natively: open a new scenario, click the three dots > Import blueprint, select the .json file, then reconnect your app credentials.

Exporting from Make: common questions

Can I export my entire Make workspace in one go?+

No. Make's documented export feature works per scenario — you export each scenario individually as a blueprint JSON file; there's no single workspace-wide export button.

Does exporting a blueprint include my app connections/credentials?+

No. A blueprint contains modules, module settings, and mapped values, but not the underlying connections — you have to re-create those manually after importing it elsewhere.

What format is a Make scenario export in?+

Scenarios export as a JSON file called a 'blueprint,' downloadable from the scenario builder's three-dot menu, or copyable as JSON text to your clipboard.

Is there a size limit on Make blueprint files?+

Yes, imported blueprints must be under 2 MB; if a blueprint exceeds the scenario size limit you won't be able to save it and will get an error.

Can I import a Make blueprint directly into n8n or Pipedream?+

Not directly — Make's blueprint JSON uses Make-specific module and app IDs that other platforms don't recognize. You'd use the exported file as a reference to manually rebuild the automation logic in the new tool.

Does exporting a blueprint back up my Data Store records?+

No. A scenario blueprint captures the scenario's modules and settings, not the records stored in a connected Make Data Store; that data isn't part of the exported file.