Content inventory
A list of every page, file, image, form and user, not just what appears in the menu. We use the sitemap, a server scan, analytics and backlink data.
A migration is a project whose success is invisible: if all goes well, visitors notice nothing except the new look. If it goes wrong, pages that brought traffic for years vanish, links in old emails hit errors and search engines start from scratch. Take an architecture practice in Kranj with a site on an old Joomla install: a hundred projects, three languages and a pile of PDFs. It wants to move to WordPress without losing the project pages clients find through search. The key is a complete inventory and a redirect map drawn up before the switch, not after it.
We migrate between WordPress, Joomla, Drupal, Wix, older in-house systems and custom builds. First we establish what data the old system can actually export.
A list of every page, file, image, form and user, not just what appears in the menu. We use the sitemap, a server scan, analytics and backlink data.
Together we decide what to move, what to merge and what to retire. Old, irrelevant content need not migrate, but retired pages still get a redirect.
Wherever possible content is moved by script rather than by hand, so the import can be rerun after a fix without losing days.
Every old URL is mapped to a new URL or the closest relevant page. The map is checked before the site goes live.
User accounts, form submissions and comments where they need to be kept. Along the way we check which personal data should still be held at all under GDPR.
Domain switch, a new sitemap in Search Console and tracking of errors and search traffic for several weeks afterwards.
A migration runs in rounds. Content is moved several times until the result is good, then frozen for a short spell.
We compile the full inventory and agree with you what moves, merges or goes.
Content is imported into staging, you review sample pages, we fix the scripts and rerun the import.
A few days before the switch, edits on the old site stop, the final import runs and the redirects are loaded.
The domain is pointed at the new system, old URLs are tested and a new sitemap is submitted. For the first weeks we watch errors and traffic closely.
What gets lost most often in migrations is PDFs, not pages. Documents in old systems tend to sit in a separate folder, outside the menu, and the inventory misses them. Yet these are often the files with the most inbound links: price lists, data sheets, press packs. We therefore build the inventory from the files on the server and from backlink data too, and give every document a redirect.
Yes, most migrations come with a new look. We recommend keeping the content structure close to the old one and making big structural changes after the switch, so any problem is easier to trace.
A well-prepared migration may cause brief fluctuations, but we do not expect a lasting fall. Lasting losses almost always come from missing redirects and removed content.
Yes, though Wix offers only limited content export. Pages are usually captured by crawling and rebuilt by hand in the new structure; for blog posts and products we use whatever exports are available.
Yes, user accounts and their data can be moved. Passwords often cannot be carried over in the same form, so users get a reset link the first time they sign in.
Let us know which system your site runs on today, roughly how many pages it has and which system you want to move to. We reply within one working day with a suggested inventory approach.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.