Pro can package a Canvas setup into a file and load it onto another install. This is built for agencies and anyone moving a configuration between sites.
What you can select
Export is per item, not all-or-nothing. The export screen lists every item as a checkbox: your header, footer, head and body code, each snippet, each template, each header and footer set with its rules, each injection with its group membership and load order, and each custom post type definition. Check what you want to move and leave the rest. Import works the same way: the review screen shows what is in the file, and you pick what to bring in.
What the file contains
A selected export bundles everything you checked into a single file. Injections travel with their group membership and load order intact, so a grouped feature arrives on the new site already wired together. Custom post type definitions, including fields and HTML templates, travel too. What the file does not include: version history, media files, posts, pages, or any content that lives in WordPress itself rather than in Canvas.
The import review step
On import, Pro shows you what is in the file before writing anything. You see each item listed as a checkbox, the same way the export screen works, so you can decide item by item what to bring in. Nothing is written until you confirm.
It pairs with version history: export captures a configuration to move it, and version history tracks how that configuration changes over time on each site. For a full walkthrough of what version history covers, see Version History.
