> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uplifter-curling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What does my website look like after the import?

> Pages, menu, media, home page, header and footer come across into the website builder on the Classic Club template at the original's measured sizes; at cutover your old site can be served as an exact copy until you switch to it.

<Note>
  **Must know**

  * Your site lands on the **Classic Club** template — "the look of your old CCM site": logo over the menu, a right-hand column, condensed type with a short rule under headings — with your colours, fonts and the sizes measured off the original.
  * **Every imported page is a draft.** Nobody publishes two dozen converted pages unseen; walk them under **Website → Club Pages** and press publish.
  * The builder version resembles the original; it is not a pixel copy. Where the two differ, the **From your CCM import** checklist says why.
  * At cutover the Uplifter team can serve your old site as a **frozen, exact copy** instead. The builder version then waits behind it, hidden, until you switch — see [Why is my club's site an exact copy of my old website?](/ccm/your-migration/why-is-my-site-an-exact-copy-of-my-old-website).
</Note>

## Two versions of your site

* **The frozen copy** — your old site exactly, captured from your live site at cutover, with its login, signup, calendar and event links pointing into the new system. Nothing in it can be edited.
* **The builder version** — what the import converted, described on this page. You edit it page by page.

If your site starts as the frozen copy, **Website → General** shows **Preview the builder version** and **Switch to the new website builder**; the steps below apply once you have switched.

## What comes across

* **Pages** — Joomla articles and menu items as club pages with blocks (text, pictures, tables, forms, tinted bands, tiles).
* **Menu** — as the **Site Menu**.
* **Media** — images copied into your media library, namespaced per club; a page whose image was missing shows a broken image rather than failing the import, and the report names the file.
* **The home page** — hero or slider strip, icon tiles, bands, in the club's own header and footer.
* **Header and footer** — arrangement (logo left or centred), band colours, up to four footer columns, the contact block.
* **Theme** — a preset plus the club's colour and font overrides.
* **Sizes** — nav, headings, module titles, logo width, container and rail widths, measured from the rendered original.
* **Sidebar** — the right-hand rail modules the club actually used; others are reported.
* **Events** as calendar listings (registration off), **sponsors** where the data holds name, logo and link, **documents** where the file was under the club's web root.

## What to do once you are on the builder

<Steps>
  <Step title="Read the checklist">
    **Website → General → From your CCM import.** Fix what has a setting, tick what you accept.
  </Step>

  <Step title="Publish the pages">
    **Website → Club Pages** — open each draft, glance, publish. The plan's needs-review list is where to start.
  </Step>

  <Step title="Look at the home page and header">
    **Website → Header & Home** — arrangement, band, tiles. **Back to our standard** returns fonts and sizes to the theme's if the measured ones look wrong.
  </Step>

  <Step title="Consider a modern template">
    **Website → Templates** — preview Open Ice, Editorial or Community Board on your own content; switch back any time.
  </Step>
</Steps>

**Related:** [What is the "From your CCM import" checklist?](/ccm/your-migration/import-checklist) · [What are the Classic Club template and the modern templates?](/ccm/your-migration/site-templates-classic-club) · [What does the import not carry?](/ccm/your-migration/what-the-import-does-not-bring) · [How do I switch from the frozen copy to the website builder?](/club/website/how-do-i-switch-from-the-frozen-copy-to-the-website-builder)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.