The short version
One codebase serves all four sites, hosted on your own Cloudflare account. Baserow becomes the single place your website’s data lives from day one — content and inventory — so nothing on the website changes when the rest of Airtable follows. The main site goes live by the end of September, the other three the week after, and the admissions base comes over last, one connection at a time, with no big switch.
Where things stand
All four share the same eighteen content collections and carry roughly the same 550 images each. The prototype you looked at is the proof that the port works: the Explore page and a program page, built from the live site’s own styles and reading the Slots table live, next to a leaner take on the same pages.
What changes
Phase 1
The main site 55 to 70 hours · two to three weeks from the Figma files
Port the site as it is
15–20 hThe current site is the spec. Its styles and markup carry over unchanged, template by template and page by page, the images move off Webflow’s servers, and the forms get their new handler with the per-page source Hannah needs. Everything is checked at desktop and phone widths before the switch.
The refresh pages
10–15 hThe five or six pages from the brand firm’s Figma files, built straight into the new system instead of into Webflow first.
Content into Baserow
6–10 hPrograms, campuses, team, testimonials, FAQs, press and the PDF pages become Baserow tables that you and Hannah edit directly. I set up the tables and import everything from Webflow.
Inventory, the live copy
4–6 hA small sync keeps a Slots table in Baserow current from Airtable, so the website only ever talks to Baserow. This is the first step of Phase 3, not a detour.
Your own Claude setup
15–20 hThe documentation and conventions your Claude sessions work from, a preview link for every change, a protected path to production so nothing goes live by accident, playbooks for the changes you actually make — copy edits, a new program or campus page, a blog post, a testimonial, a form or pop-up — and a first round of supervised edits with both of you.
The switch-over
end of SeptemberWebflow keeps running until the new site has been checked; then the domain moves. If the Figma files arrive next week, the main site is live by the end of September.
Your answer · Phase 1
Phase 2
Business, Law and Abroad 4 to 5 hours each · the week after Phase 1
Each site is a copy of the main one, so each gets its content pulled over, its colours and domain set, a check at both widths and its own switch-over. Abroad has its own inventory base and program pages, which is why it sits at the top of that range. Once they are on the shared codebase, a change to a shared page is made once instead of four times.
Your answer · Phase 2
Phase 3
The admissions base moves to Baserow scoped with Liam after a discovery session
Phases 1 and 2 leave the admissions base in Airtable, untouched. This phase finishes the move off Airtable. The base is where applications, payments, contracts, interviews and offers are written: Fillout, Finix, Xodo and Cal each feed it through their own connection, the ActiveCampaign sync reads from it, and your team works in its views every day.
The way to do it without a risky switch is one connection at a time. The live copy from Phase 1 is step one; each connection then moves over to Baserow and is checked; when the last one has moved, the copy is switched off and Airtable is archived. Baserow can import the tables and rows directly, which covers the data — the formulas, views and connections are the work. Timing follows the O27 admissions cycle, so a quiet window matters more than speed.
Liam and I will walk through those connections together first, and I will add the hours for this phase then. From what I know today it is a small addition to the plan rather than a second project.
Your answer · Phase 3
What goes away, what stays
Goes away
- Webflow hosting and its CMS, for all four sites
- The four inventory sync programs
- Webflow’s form pipeline and its three destinations
- The speed workarounds the Webflow site needed
- Airtable’s automations and views — in Phase 3
Stays
- Your tracking as it is: Google Tag Manager, the ad pixels, the cookie banner, Trustpilot, Wistia
- Brevo, receiving leads with their page source
- Fillout, Finix, Xodo, Cal and the apply site — pointed at Baserow in Phase 3
- Airtable, read-only, until Phase 3 is done
How you’ll make changes afterwards
Content lives in Baserow: change a program’s description or a team member’s photo there and it is on the site within a minute. Pages and templates change through your own Claude sessions, working from the documentation I set up: you describe the change, it is built on a preview link, you look at it on your phone or laptop, and only then does it go live. Two people can work at the same time without stepping on each other, because every change sits on its own preview until it is approved. Undo is one step.
Built so it can’t break
- Webflow stays live until the new site has been checked, on every domain.
- Every change has a preview before it goes live.
- Production is protected: nothing publishes without an approval step.
- The admissions base is untouched in Phases 1 and 2; the live copy only reads from it.
- Any change can be undone in one step.
Next step
The 20 hours already paid cover the first week of Phase 1. Send me your answers here, or reply to my email with a yes, and I start on the port and the working setup the same day.
Anything else