Cargo portfolios and websites
Move your Cargo website to Staticbot
Bring the Cargo content, originals, code and backups you already have. Staticbot will inventory the package and help plan the independent website; you do not need to rebuild it first.
Platform instructions checked October 16, 2026. Controls and plan availability can change.
No site export · rebuild required
What you can bring across
Your own text, images, files and page inventory, assembled manually. There is no Cargo website ZIP to upload to Staticbot.
Bring the files you have in one ZIP, or use your existing Git repository. Staticbot will inspect the inputs and request a review. You do not need to rebuild the website before submitting it.
Before you start
- Access to your Cargo editor and the original photos, artwork, video and project descriptions you own.
- A list of project URLs, galleries, pinned pages, overlays, menus and any commerce or contact features.
Bring the files you already have
Start with the material you already have
Cargo does not offer a site export. Gather available original photos, artwork, video, project text, downloads and any saved pages or backups. Include what you have rather than rebuilding the portfolio first.
Include the site address and project notes
Add a short text file with the current Cargo URL, important project pages, and any forms, commerce, galleries or effects you want to keep. Tell us if content or account access is missing.
Add any existing code or page captures
If you already have custom code, page-content HTML from Code View, or screenshots, include them. Code View is a reference for page content, not a complete portable Cargo engine. You do not need to reconstruct that engine yourself.
Put everything into one ZIP or Git repository
ZIP the content folder together with any existing archives. Alternatively, add the available material to your existing repository. Keep ownership and licence information for assets with the package.
Submit it for review in Staticbot
Upload your ZIP using Upload your project, or use the Git import form. Staticbot inventories the inputs, detects available platform signals and requests a review. We will help identify missing material and prepare the next steps inside Staticbot.
Features to review before moving
- Cargo explicitly states that it does not currently offer site export.
- Duplicating a Cargo site or copying a Cargo page within its editor is not an independent hosting export.
- Review font and template licensing, native commerce, forms and Cargo-specific visual effects before rebuilding.
Check the preview before changing DNS
Walk through every project from the thumbnail index, test overlays and mobile navigation, and open media downloads. Check that images and video still work without relying on the old Cargo site.
Keep the old account and your backups until the replacement works. You can connect a custom domain you control after testing; the provider’s own subdomain stays with the original platform.
Next: bring your files to Staticbot
Choose the separate ZIP upload or Git import form. Staticbot keeps the package and its inventory for review. Once the website is prepared, the existing hosting guides explain previewing and deployment.
Upload or import your files