Code export needs a Workspace plan. Confirm the plan at kickoff. The export gives HTML, CSS, JavaScript, and assets. It does not include CMS content, user accounts, ecommerce, localization beyond the primary locale, password protection, form processing, reCAPTCHA, site search, or code components. CMS lists come out empty.

CMS content is a second export

Collection items come from the Data API or from a CSV per collection. CSV turns references into plain text, so the API is the better export when you can use it. The Pages API returns slugs, SEO titles and descriptions, and the no-index flag. That list is the spine of the inventory.

The asset API misses images that live inside CMS rich text. Those still have to be collected.

What to hand over at kickoff

Invite Everbase to the Workspace or the site as an Editor or a Designer. Do not share a login.

Also export the 301 redirects from Site settings, SEO, 301 redirects. That file is a CSV. Folding it into the new map is what stops a chain of old redirects.

Custom code is in more than one place: site head and footer, page head and footer, embed elements, and embeds inside rich text. Native Google Analytics and Meta Pixel integrations, and marketplace apps, do not appear in the custom-code API. Check Site settings, Integrations, by hand.