Bringing Your WordPress Content Along
You have years of content in WordPress: pages, blog posts, pictures. Nobody wants to type that again, and you do not have to. The AI can read a website the way a visitor does, so the move is one request: take the content from my old site. It does not even have to be WordPress. And while you are at it, you can say where the design should come from.
Goal
By the end of this chapter you will have:
- your pages, posts and pictures in your ForgeCMS content repo,
- a design you chose,
- the old addresses leading to the new pages, so links and search engines keep working.
Step 1: Make a list
Before you start, look at your old site for ten minutes and write down:
- the menu: which pages, in which order,
- the plugins you use and what for: contact form, calendar, shop, gallery. For each, Step 4 asks which ForgeCMS module or plugin takes over.
Step 2: The move
While your old site is still online, ask:
Please rebuild my website https://old-site.example with ForgeCMS:
take all pages, all blog posts (with date and picture) and all pictures,
keep the menu, and put everything into my content repo.
For the design, take https://a-site-i-like.example as the model.
Tell me what you could not take over.
That is the whole import. The AI goes through the old site page by page, writes every page as SML and Markdown, every post as a Post in blog.sml, downloads the pictures into static/ in a sensible size, and builds a theme after the model you named. We have moved several sites this way, from WordPress and from other systems.
"Content from one site, design from another" is the general recipe, and it works in any combination:
- your own old site for the content, a site you like for the look,
- your old site for both, just without WordPress underneath,
- a printed flyer or a Word file for the content, and a short description for the design: "calm, lots of white, one warm colour".
One rule: the content must be yours. Your texts, your pictures, your products. Another site may inspire the design, the colours, the order of things; its texts, photos and logo belong to its owner and stay there.
The other way: the export file
Sometimes the old site is already offline, or you want things a visitor cannot see: drafts, every old post of ten years, the categories exactly as they were. Then give the AI the WordPress export instead. In WordPress, Tools → Export → All content → Download Export File gives you an XML file with all pages and posts. The pictures are in the folder wp-content/uploads of your old hosting (download it via FTP or the hosting's file manager). Copy both to your server and say:
Here is the WordPress export of my old site: /root/wordpress-export.xml,
the pictures are in /root/uploads. Please move everything into my content repo:
pages, published posts with date, categories as rubrics and featured image,
and the pictures. Tell me which shortcodes you found.
Keep the export file anyway. It is your content, independent of any hosting company.
What needs a decision
The AI gives you a list of what it could not take over one to one. Take your time with it.
Shortcodes are the bits in square brackets in WordPress texts: [contact-form-7 id="12"], [gallery ids="1,2,3"]. They belong to plugins and mean nothing outside WordPress. Each one is replaced by something ForgeCMS has: a ContactForm, pictures in Markdown, a plugin.
Page builders (Elementor, Divi, WPBakery) put their own layout around the text. The AI keeps the text and the pictures and rebuilds the layout with SML elements, usually simpler than before.
Step 3: Look at everything
Open the new site and go through it page by page, best with the old site open next to it. Typical things to fix:
- texts with leftover formatting, empty lines, odd characters,
- pictures that are too big or missing,
- links inside texts that still point to the old addresses.
For each, tell the AI what you see. For the links: "Please change all links in my texts from the old WordPress addresses to the new ones."
Step 4: Replace the plugins
Go through your list from Step 1:
| WordPress plugin for … | In ForgeCMS |
|---|---|
| contact forms (Contact Form 7, WPForms) | contact form module (chapter 10) |
| newsletter (MailPoet, Mailchimp) | newsletter module (chapter 10) |
| events (The Events Calendar) | events module (chapter 11) |
| shop (WooCommerce) | shop module (chapters 13 and 14) |
| courses (LearnDash, Tutor) | courses module (chapter 15) |
| SEO, caching, security | not needed: ForgeCMS sends fast, clean pages and has no admin area to attack |
| anything else | a plugin (chapter 17), or a feature request on crowdware.info |
Newsletter addresses can be moved too, but only those who confirmed. Ask the AI; the addresses go into the newsletter's list on the server.
Step 5: Keep the old addresses
Your old pages have addresses that other sites link to and that search engines know: /about-us/, /2024/05/our-new-oven/. If they suddenly lead nowhere, you lose visitors.
For pages, the easiest way is to keep the address exactly, including the slash at the end that WordPress uses: in site.sml, a Route can have any path.
Route { path: "/about-us/" page: "about-us.sml" }
/about-us/ and /about-us are two different addresses for ForgeCMS, so copy the old ones exactly as they are.
For blog posts, the address changes (WordPress uses dates in it, ForgeCMS uses /blog/<id>). Here Caddy, the program in front of ForgeCMS that handles HTTPS, can redirect:
Please add permanent redirects in Caddy from all old WordPress post
addresses in the export to the new /blog/... addresses.
A permanent redirect tells browsers and search engines: "this has moved for good". After a few weeks, search engines show the new addresses.
Step 6: Switch over
When everything is ready:
- Point your domain's A record to the new server (chapter 3).
- Wait until the new site is reachable under your domain, and check HTTPS.
- Keep the old hosting a few more weeks, just in case. Then cancel it.
Pitfalls
- Big sites: with thousands of posts the move takes the AI longer. Ask it to do one year or one section at a time.
- Comments: WordPress comments are in the export, but ForgeCMS has no comments yet. Decide whether to keep the best ones as text in the posts, or to let them go.
- Pictures from the media library used nowhere: the AI can leave unused pictures out. Your site gets smaller.
- Logins and members: user accounts cannot be moved; passwords are not in the export. Members of a course log in again by email.
What you learned
- The move is one request: content from your old site, design from a site you like (or from your own words). The content must be yours.
- For drafts, a complete archive or a site that is already offline, the WordPress export file does the same.
- Shortcodes and page builders need a decision each; each WordPress plugin is replaced by a module, a plugin, or nothing at all.
- Pages can keep their old addresses; blog posts get permanent redirects in Caddy.
