WEBGENCustom websites.

Migration

You already have a site. You don't have to start over.


The posts, the pages, the images and their addresses already exist. We bring all of it across — what's good stays, what has aged gets rebuilt.

What moves

What we bring from the old site

  • The posts

    With their text, images, categories and publication dates. Accented characters mangled over the years get repaired on the way.

  • The images

    The originals, not the resized copies. They're served in modern formats, at the size each screen actually needs.

  • The old addresses

    Every known address gets a redirect to its new home. Inbound links and search rankings aren't lost.

  • The structure

    Categories, menus, pages. What was organised stays organised.

What it looks like in practice

The first site we migrated brought across 582 posts published since 2012, with 585 redirects for the old addresses. None of it was typed by hand: the importer reads the old site's database directly and writes the content in the new format.

Whatever doesn't fit tells us so. The import produces a report of everything left out — a plugin shortcode, a chunk of HTML typed straight into a post — so we can decide together what's worth rebuilding and what can go. An import that reports no losses is lying.

The shop: two routes

If you sell online, this isn't a single decision.

The platform has a shop — physical products and downloadable files, paid through your own processor, with invoices still issued by you. The payment account stays yours: we don't stand between you and your money, and we don't become the merchant on your behalf.

But a shop that works doesn't get moved for the sake of moving. When you have hundreds of products with variants, or flows tuned over years, the switch can be made route by route, on the same domain: the brochure pages and the blog on the new platform, the cart and the payment where they already work. The visitor sees no seam, and checkout is left untouched.

Which route is yours gets decided by looking at your catalogue, not at principles.

What we don't move

Plugin code. Whatever a plugin did is either rebuilt as a component, if it earns its place, or it goes — and often nobody had noticed it was there. The import report lists every one of them, along with the content it touched, so the decision is yours.

And the styles written into the old theme, which usually don't even make it into the export. The design starts fresh — and that's the good part: it's the reason you wanted a new site.

Want to see what your site could look like?


We look at what you have now and tell you what can be migrated automatically and what is worth rebuilding. No strings attached.