What a blueprint contains, and what it leaves behind
Make describes a blueprint as a reusable version of a scenario that includes the scenario's modules, module settings and mapped values. You can use it to back up a scenario, reuse it, share it with other Make users, or paste it into other scenarios or tools. [1] It downloads as a .json file named after the scenario, or after its modules if the scenario still has the default name. [1]
What it does not carry is just as important. Make says users must create connections for their own accounts after importing. [1] The blueprint page does not say whether webhooks, data stores, keys or data structures travel with it. [1] Treat them as things to recreate, because each lives in its own part of Make: webhooks have their own queue and URL, and data stores hold data that can pass between scenarios or scenario runs. [3] [4]
| Item | In the blueprint? | What to do |
|---|---|---|
| Modules and their order | Yes [1] | Nothing |
| Module settings and mapped values | Yes [1] | Review after reconnecting, since a new connection may not see the same items [2] |
| App connections | No [1] | Create in the target account |
| Webhook setup | Not stated [1] | Create a new webhook and update whatever sends to it |
| Data store records | Not stated; backed up separately [4] | Copy with a scenario or the Make API |
| Schedule | Set after import [1] | Re-enter the schedule, then save |
Export and import, step by step
To export, open the scenario, confirm its modules are configured, click the three dots in the upper-right corner of the Scenario Builder and choose Export blueprint. [1] For a quick copy without a file, Copy blueprint to clipboard puts the JSON on your clipboard; you then right-click the canvas of another scenario and choose Paste. [1]
To import, create a new scenario first; Make recommends this because importing over an unsaved scenario discards its unsaved changes. Then use the three dots, Import blueprint, Choose File, and Save. [1] After that, configure your own connections, make any edits, set the schedule and save again. [1] The file must be under 2 MB or the scenario cannot be saved. [1]
Clone, blueprint or version history?
Make has three ways to copy or roll back a scenario, and they suit different jobs. Cloning copies a scenario within the same organization, either in the same team or to another team, with all module settings. Within the same team it keeps the original connections; in another team you select connections from the target team or create new ones, and create a webhook that replaces the original. [2] Version history lets you save versions, with an optional description, and restore one; Make keeps each saved version for 60 days, except the latest, which it keeps until you save a newer one. Restoring does not save automatically, so click Save afterwards. [5]
Blueprints are the only one of the three that leaves Make as a file. That makes them the right tool for moving between organizations and for backups you control.
| Job | Tool to use | Why |
|---|---|---|
| Copy to another team in the same organization | Clone [2] | Keeps settings, lets you pick connections and webhooks |
| Undo a bad edit from last week | Version history [5] | Saved versions kept 60 days |
| Move to a different organization or region | Blueprint [1] [7] | Clone works only inside one organization |
| Share with another Make user | Blueprint [1] | Portable .json file |
| Offline backup before big changes | Blueprint [1] | Survives beyond the 60-day window |
Moving accounts or regions: what to reconnect
Make asks you to choose a US or EU data center when you create an organization and says you cannot change it afterwards. [7] So moving a scenario between regions, or to a client's own organization, means a blueprint import into the other organization followed by a full reconnection.
Webhooks need special care. A webhook URL triggers a scenario, and Make deactivates a webhook that is not connected to any scenario after 120 hours, after which it returns 410 Gone. [3] When you move, create the new webhook, update the sending app to the new URL, and confirm the new scenario receives data before switching the old one off. Data store contents also stay behind: Make documents backing up a data store with a scenario that copies records into a backup store, or through the Make API, and deleted records cannot be rolled back. [4]
A backup routine before big edits
Version history covers recent edits, but only for 60 days. [5] Deleted scenarios sit in Trash for 30 days before permanent deletion. [6] For anything that runs your business, keep your own copies as well.
- Before a major edit, save a named version in Version history and export a blueprint. [5] [1]
- Store blueprints with the date and scenario name, for example 2026-10-30-invoice-reminders.json.
- Keep a short text note of which connections, webhooks and data stores the scenario uses.
- Back up data stores the scenario writes to, with a copy scenario or the API. [4]
- After restoring or importing, reconnect webhooks before running the scenario. [6]
- Delete old blueprint files that contain mapped values you no longer want stored.
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
Does a Make blueprint include my connections?
No. Make's blueprint page says users still need to create connections for their accounts after importing a blueprint. Plan to re-authorize every app in the target account.
Is there a size limit on blueprint imports?
Yes. Make says the imported blueprint must be below 2 MB, and if it exceeds the scenario size limit the scenario cannot be saved and an error appears.
Should I clone or export a blueprint?
Clone when the copy stays in the same organization: Make can clone to another team there and lets you pick connections and webhooks. Use a blueprint to move between organizations or to keep an offline backup.
Can I move a scenario from Make's EU data center to the US one?
Not by changing the organization: Make says you cannot change the data center location after you create an organization. You would create a new organization in the other region and import the scenario there as a blueprint.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make Help Center: Scenario blueprints Accessed 30 Oct 2026
- Make Help Center: Clone a scenario Accessed 30 Oct 2026
- Make Help Center: Webhooks Accessed 30 Oct 2026
- Make Help Center: Data stores Accessed 30 Oct 2026
- Make Help Center: Scenario version control Accessed 30 Oct 2026
- Make Help Center: Delete a scenario Accessed 30 Oct 2026
- Make Help Center: Organizations Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.