Taking it with you

Your code

Your GitHub repository is the only working way out of MaShop. Clone it and you hold everything that runs your site.

Take a copy

Open the GitHub Sync panel in the workspace. When your account is connected, the arrow at the top right opens your repository on github.com. From there:

git clone https://github.com/<your-account>/mashop-<slug>.git
cd mashop-<slug>
pnpm install
cp apps/storefront/.env.local.example apps/storefront/.env.local
cp apps/admin/.env.local.example apps/admin/.env.local
pnpm dev

Fill both env files with the Supabase URL, the anon key and the service role key from your Supabase dashboard. The repository then runs with no dependency on MaShop at all.

The exits that do not work today

Three ways out are visible somewhere in the product. None of the three produces a file.

• Download ZIP. The button is coded but never displayed, because the panel that carries it is no longer mounted. There is no archive download.
• Download session.md, for Claude Code. It fails every time: the interface calls the route with POST while the route only answers GET, so the reply is a 405 and the screen shows an export failure. The modal has no button either, it opens only with Ctrl or Cmd and E.
• A copyable repository address. No screen shows one. The arrow in the GitHub panel is the only path.

Reconnect GitHub before you plan to leave. With that account disconnected, no other export exists.

Transfer of ownership, and what it really moves

The transfer sends an email invitation valid for seven days. The recipient must be signed in with the invited address. It is refused while a generation is running, since that generation is billed to whoever started it.

On acceptance, one thing changes: the project owner inside MaShop. The GitHub repository, both Netlify sites and the Supabase project stay on the previous owner's accounts, whatever the confirmation screen announces about repository ownership, deployment and database. The previous owner also loses all access at once, and is not kept as a collaborator.

There is a defect in the path itself. The link in the email points at an address the application does not serve, so the recipient lands on a missing page. The route that would accept the transfer sits elsewhere, and nothing sends the recipient to it. No project changes hands this way today.

To hand a project over, move each piece in its own provider: transfer the GitHub repository from GitHub settings, the sites from Netlify, the project from Supabase. Then have the new owner create their own MaShop project if they want to keep building there.

Archiving

Archiving writes a date on the project. Its only real effect is that the project stops counting against your plan's project cap, which lets a Free account create another one.

Despite the wording on screen, the project stays visible in the project picker and stays openable, and no screen sends the reverse request. Treat archiving as one way.

Permanent deletion

Deleting asks you to retype the project name. It then does exactly this:

• Deletes your GitHub repository, with your own token.
• Deletes the Netlify site of the public site, with your own token.
• Deletes the MaShop project row and everything attached: files, versions, conversations, memory.

Those first two steps need the matching account to still be connected. When a token is missing, the repository or the site survives, and the deletion reports it as a warning rather than stopping.

And this is what deletion does not do, whatever the confirmation list says:

• Your Supabase project survives, with your orders, your customers, your products and your storage buckets. It also keeps being billed by Supabase until you delete it yourself.
• The second Netlify site, the back office, stays online with its environment variables.
• Credits already spent are not refunded.

Leaving cleanly, in order

1. Clone the repository and keep the copy somewhere safe.
2. In Supabase, reset the database password if you want direct access, and export what you need.
3. In Netlify, deal with both sites yourself: mashop-<slug> and mashop-<slug>-admin.
4. Delete the project in MaShop, knowing that step removes the GitHub repository.
5. Keep or delete the Supabase project from the Supabase dashboard, as you prefer.