Import & export
Two formats
Your whole project moves between sites as a single file. There are two kinds:
| Format | Contains | Use it when |
|---|---|---|
.json |
The project — sitemap, pages, global classes, components, style settings, code snippets | The target site already has the images |
.zip |
All of the above plus every image and upload | Handing over to a client, or moving to a fresh site |
The .zip is the safe default. The .json is smaller and useful for moving structure between sites that share a media library.
Export
Open the Projects panel and choose the export you want. The file downloads to your machine.
Everything that makes the site look the way it does travels together — you're not exporting styles, classes and pages as three separate jobs and hoping they line up.
Import
- On the new site, install Brickser and activate the licence.
- Open the Projects panel and select Import project.
- Choose your file.
With a .zip, images are re-uploaded into the new site's media library and every reference is rewritten to point at the new IDs. You don't get a site full of broken images pointing back at the old domain.
What to check afterwards
- Custom code is off. Imported snippets always arrive disabled. Turn on the ones you want — Custom code explains why.
- Install the design system if the new site doesn't have it yet, or sections will render unstyled.
- Add an AI provider key. Keys are never exported.
SVG uploads are sanitised on the way in, so a project file from someone else can't smuggle a script into your site through an image.
Re-importing over an existing project
Importing replaces the current project on that site — remember, one project per site. Export the existing one first if you might want it back.
