# Everbase guide

> How to use Everbase after a migration: the move, the Console, integrations, and The Everbase Stack. Written for the team that edits and approves.

## Pages

- [How to use Everbase](https://everbase.studio/guide/): A short guide for the marketing team that will edit, approve, and publish after a migration.
- [How a migration works](https://everbase.studio/guide/how-a-migration-works/): A fixed-price rebuild onto The Everbase Stack, scoped before work starts, with 30 days of care after launch.
- [The 4–6 week timeline](https://everbase.studio/guide/timeline/): Every platform fits 4–6 weeks. The launch date is set after discovery, and hypercare is 30 days either way.
- [What you get at handover](https://everbase.studio/guide/handover/): The repository, Studio, a handover doc, short recordings, and a live training session so your team can edit without Everbase in the room.
- [Overview](https://everbase.studio/guide/console/): The Console home. It opens on what needs you today, for your site only.
- [Ask](https://everbase.studio/guide/console/ask/): Where you describe a change in your own words, then review the plan before anyone drafts it.
- [Work](https://everbase.studio/guide/console/work/): Every change you asked for, from the plan to live, in Inbox, History, and Activity.
- [Reports](https://everbase.studio/guide/console/reports/): Traffic, search, and what shipped, side by side. The charts do not claim a change caused a number.
- [Approving and publishing](https://everbase.studio/guide/console/publishing/): Approve the draft you reviewed. Publishing is a separate step, and a paused site publishes nothing.
- [Integrations](https://everbase.studio/guide/integrations/): Forms, CRM, payments, and analytics stay. Each tool has its own guide under Integration guides.
- [What you own](https://everbase.studio/guide/what-you-own/): Your organization owns the Cloudflare, GitHub, and Sanity accounts. Everbase is granted access and is not the account owner.
- [Running costs](https://everbase.studio/guide/running-costs/): The migration price and Continuous development are the figures on the cost page. You pay the hosts yourself.
- [How to leave](https://everbase.studio/guide/how-to-leave/): Pause or cancel ongoing work any month. The site keeps running because the accounts and the code are already yours.
- [Leaving Webflow](https://everbase.studio/guide/manuals/leaving-webflow/): What a Webflow export actually contains, what has to be rebuilt, and what you keep until hypercare ends.
- [What the export includes](https://everbase.studio/guide/manuals/leaving-webflow/export/): A code export is HTML, CSS, JavaScript, and assets. CMS content, forms, memberships, and ecommerce are not in it.
- [Content, forms, and URLs](https://everbase.studio/guide/manuals/leaving-webflow/content-and-urls/): Keep the collection prefix in your URLs. Form destinations are not in the export, so they are written down by hand.
- [After launch](https://everbase.studio/guide/manuals/leaving-webflow/after-launch/): Keep the Webflow plan through the 30 days of hypercare, and keep the staging URL up for at least two weeks.

## Manuals

- [Leaving Webflow](https://everbase.studio/guide/manuals/leaving-webflow/): What a Webflow export actually contains, what has to be rebuilt, and what you keep until hypercare ends.

A markdown copy of each page is linked from that page. This file is https://everbase.studio/guide/llms.txt.