Pro plan and above to publish
Change platforms without throwing away your design
Point us at your current website. We capture the real pages into the Builder, where you keep editing them visually or ask the built-in AI assistant for changes, and publish when you are ready. Nothing is re-designed unless you ask for it.
What it is
The usual migration story is 'rebuild everything and hope the result looks like you'. This is the other path.
Most clinics coming to a new website platform are not unhappy with how their site looks. They are unhappy with what is under it: no editing control, no booking, a designer who left. The rebuild path asks you to give up a design that works and gamble on a generated one. The clone path does not: we fetch the actual HTML and CSS of your existing page, strip out anything unsafe, and hand it to you in the Builder as your starting point.
From there it behaves like any ClinicSite site. You edit visually in the Builder, or describe changes and let the AI apply them; every save is versioned, and publishing runs under the same strict security policy as the rest of the platform. Captured pages have scripts and inline event handlers removed at capture, not preserved.
Editing in the Builder, and what publish does to it
The Builder is a full editor on the real site files, and publishing runs the platform's script policy on everything you ship.
It edits the site's files, not a copy
Ask the assistant in plain language
Review in a draft before it is live
Publish applies the script policy
What carries over, and what deliberately does not
Your layout, text, styling, and images carry over. Scripts do not: a captured page is stripped of its JavaScript before it ever becomes a draft, because running a foreign clinic’s, or your own abandoned vendor’s, unreviewed scripts on a healthcare site is exactly the kind of inheritance you are trying to escape. Widgets that depended on those scripts (third-party chat bubbles, trackers, embedded tools) will not function; the ClinicSite equivalents, where they exist, are added by the platform instead.
Forms on the captured page are inert, like every form on a published ClinicSite site: form-action ’none’ is part of the published site’s security policy, so captured contact forms do not silently start collecting patient data on a platform that was never designed to receive it. Contact runs through phone, email, and chat on qualifying plans.
Honest limits
| Capability | Status | What that means |
|---|---|---|
| Preserve your existing design | Built | Your real HTML and CSS are captured and opened in the Builder as the draft. |
| Visual editing after capture | Built | The captured pages open in the Builder at /editor/[siteId]: edit text and styles directly, open the HTML and CSS, save, and restore any previous save. |
| AI-assisted edits in plain language | Built | The built-in assistant changes the site's own files from a plain-language instruction, and you review the result in the draft preview before publishing. |
| Rehosting your images | Built | Images are copied to ClinicSite storage so nothing is hotlinked from your old host. |
| Carrying over your scripts and embedded widgets | Not yet | Scripts are stripped on purpose. Third-party widgets that need them will not function. |
| Publishing on a free plan | Not yet | Previewing and editing a clone is free; publishing it to your domain requires a paid plan (Pro or above). |
Cloning is one of the two ways to start. If you would rather have a new design built from your real details, that is the AI website builder. Current plans are on the pricing page.
Frequently asked questions
- Will my site look exactly the same?
- The goal is preservation, not re-design: we fetch the real HTML and CSS of the site you point us at, clean it, and open it in the Builder as-is. What you edit is what you had. Pages built heavily in JavaScript can be imperfect, because scripts are stripped for safety. What remains is your content and styling.
- What happens to my images?
- They are copied to our own storage and the page is rewritten to serve them from there. Your old site can go away without your new one breaking, and you are never hotlinking another server.
- How does the AI editing work?
- You describe the change in plain language, for example 'make the heading say we accept walk-ins', and the built-in assistant makes it on the site's own files. It works on the real files in the Builder rather than returning a rewritten copy, so nothing is regenerated behind your back. The change lands in the draft preview, where you see exactly what it did and can undo it before it reaches your live site.
- Is there a size limit?
- Yes. Extremely large pages are refused with a clear error instead of silently failing. It is a deliberate bound so an AI edit stays fast and reviewable; normal clinic pages are comfortably inside it.
- Can I undo a change?
- Every explicit save snapshots the site, and you can restore any previous snapshot from the revisions list. Restoring snapshots your current draft first, so an undo is itself undoable.
- What does it cost?
- Capturing and editing a clone is free while you are previewing. Publishing it, which means putting it on your domain as your live site, requires a paid plan (Pro or above). See the pricing page for current plans.
Keep reading
- AI website builderThe rebuild path: a new site generated from your real details, with nothing invented.
- How it worksFrom pasting your current website address to a published site on your domain.
- HIPAA-compliant website builderWhy published ClinicSite sites run under a strict security policy, and what that means for forms and data.
- Questions and answersPlans, publishing, domains, data, and what we deliberately do not build.
See what your clinic site could look like
Paste your current website address. You get a full generated replacement to look at, free, with no account and no card.
Free preview with no card. Previews are deleted after 7 days.