Site Import & Export to set up sandbox instances
Key Takeaway
Site Import & Export copies site data and configuration, but not code, from one instance to another. When you export for a sandbox, leave out "Users and Access Roles" so the import doesn't overwrite the sandbox's users, passwords and permissions. To bring Production data into a sandbox, make a local export on Production and use a remote import on the sandbox.
Site Import & Export is a Business Manager module that packages an instance's site data and configuration into one .zip file and loads that file into another instance. Developers use it to set up a new sandbox as a copy of an existing instance, so they don't have to configure every setting by hand. The module moves data and configuration only, so you handle code (cartridges) separately.
What Site Import & Export does
A site export copies database objects and static files into a single .zip file that you can download. A site import uploads that .zip file to another instance and loads it into the instance database. Both live at Administration > Site Development > Site Import & Export. To use them, you need an account with import/export privileges for the site.
Site Import & Export is meant for setting up identical sites (same names and IDs) and the same organization-level data across instances. Because it works like cloning an instance, Site Import & Export is most useful for initializing a developer's or tester's instance.
Site-specific data, such as job schedules, can be imported only into a site with the same name on another instance. You can't import it into a different site on the same instance.