How to use Everbase

A short guide for the marketing team that will edit, approve, and publish after a migration.

Getting started

The move, the weeks, and the handover

How to use Everbase A short guide for the marketing team that will edit, approve, and publish after a migration.
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 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 The repository, Studio, a handover doc, short recordings, and a live training session so your team can edit without Everbase in the room.

The Console

Overview, Ask, Work, and Reports

Overview The Console home. It opens on what needs you today, for your site only.
Ask Where you describe a change in your own words, then review the plan before anyone drafts it.
Work Every change you asked for, from the plan to live, in Inbox, History, and Activity.
Reports Traffic, search, and what shipped, side by side. The charts do not claim a change caused a number.
Approving and publishing Approve the draft you reviewed. Publishing is a separate step, and a paused site publishes nothing.

Integrations

Tools that stay connected

Integrations Forms, CRM, payments, and analytics stay. Each tool has its own guide under Integration guides.

The Everbase Stack

What you own, what it costs, and how you leave

What you own Your organization owns the Cloudflare, GitHub, and Sanity accounts. Everbase is granted access and is not the account owner.
Running costs The migration price and Continuous development are the figures on the cost page. You pay the hosts yourself.
How to leave Pause or cancel ongoing work any month. The site keeps running because the accounts and the code are already yours.

Manuals

Long guides

Manuals Long guides that teach one move. One manual is ready: Leaving Webflow.
Leaving Webflow What a Webflow export actually contains, what has to be rebuilt, and what you keep until hypercare ends.
What the export includes A code export is HTML, CSS, JavaScript, and assets. CMS content, forms, memberships, and ecommerce are not in it.
Content, forms, 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 Keep the Webflow plan through the 30 days of hypercare, and keep the staging URL up for at least two weeks.

This guide is the client view of an Everbase migration. It covers how the work runs, what the Console is for, which tools can stay, and what you own when the site is on The Everbase Stack (Astro or Next.js, with Sanity, on Cloudflare or Vercel). It is written for the people who edit and approve.

Longer teaching sits in Manuals. One manual is ready: Leaving Webflow. A topic with no page here is left out on purpose.