Content inventory
Crawling the old site lists every page, image, PDF and form. Search Console and analytics data flag the pages with the most visits and inbound links.
Service · Websites and web applications
CMS migration
Changing CMS is less a technical job than an inventory job. Picture a hypothetical Ankara architecture practice with twenty years behind it. Its site runs on a Joomla version that no longer gets updates and holds hundreds of project pages, competition results, press items and PDFs. Some project pages have earned links from architecture magazines and university sites. If even one of those addresses disappears in the move, those links hit an empty page, and search visibility built up over years can fall away overnight. A successful migration depends on knowing exactly what the old site contains and making sure every old address has a new home. The switch itself takes minutes; the preparation takes weeks.
Complete inventory
pages, images, documents and inbound links
URL mapping
a new destination for every old address
Scripted transfer
no copying and pasting by hand
Seamless switch
the old site stays live until the cut-over
What the work covers in practice
The old site stays online unchanged until the cut-over. All preparation happens in a test environment of the new system.
Choosing the target system
WordPress, a headless CMS such as Strapi or Directus, or a hosted platform. The choice depends on content types, the number of editors and whether the site feeds other channels.
Content model and transfer
Content types in the old system are mapped to fields in the new one. Transfer runs from the database or export files via scripts, so trial runs can be repeated as often as needed.
URL mapping and 301 redirects
A mapping table pairs every old address with its new one, including old URLs with Turkish characters or query parameters. Redirects are single-hop, never chained.
Link and image fixes
Internal links inside content are rewritten to the new addresses, image paths are corrected and stray formatting left by the old system is cleaned out.
Post-launch checks
After the switch every old URL is tested automatically, and crawl errors and indexing in Search Console are monitored for days.
How we approach the job, from first call to handover
The switch takes minutes, the groundwork several weeks, so we plan the timetable backwards from cut-over day.
01
Inventory and mapping
The full list of the old site is produced, and together we decide what moves, what is merged and what is retired.
02
Trial transfers
Content is moved into the test environment and you check sample pages. Errors are fixed in the scripts and the transfer is rerun.
03
Content freeze and final run
A few days before the switch, edits on the old site stop, the final transfer runs and the redirects are loaded.
04
Cut-over and monitoring
The domain is pointed to the new system, old URLs are tested and a new sitemap is submitted to Search Console. In the first weeks we watch crawl errors and organic traffic closely.
In migrations, the content most often lost is not text but PDFs. Older systems tend to keep documents in a separate folder, missing from menus and easily overlooked in an inventory. Yet they are often the very files with the most inbound links: price lists, technical sheets, press kits. We build the inventory from server files and backlink data as well as menus, and set a redirect for every document.
Frequently asked questions
Yes, most migrations come with a new design. To limit risk we suggest keeping the content structure close to the old one and leaving major structural changes until after the switch, so any problem is easier to trace.
A well-prepared migration may cause short-term fluctuation, but no lasting fall should be expected. Almost all permanent losses come from missing redirects and deleted content. With a complete mapping table, search engines adopt the new URLs within a few weeks.
Yes. Member accounts, form entries and comments can be transferred. Passwords often cannot be carried over in the same format, so users receive a reset link at first login. We also review with you, from a KVKK perspective, which personal records should no longer be kept.
Yes, although these builders offer limited export. Pages are generally captured by crawling and reworked into the new structure. Blog posts and products have partial export options, which we use.
Neighbouring services that often go with this one
Service
WordPress websites
Your own block theme, a lean set of extensions, licences owned by the business
Service
Shopify, ikas and other platforms
ikas, IdeaSoft, T-Soft, Ticimax, Shopify or WooCommerce, picked on evidence
Service
Brochure site and product catalogue
A compact site with a catalogue that collects quote requests instead of payments
Service
Corporate website
Clear, separate paths for customers, candidates, suppliers and journalists
Describe your migration
Tell us your current system, roughly how many pages you have and where you want to move. Within one working day we reply with an initial proposal for the inventory.
Availability
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Calls
By video, over Microsoft Teams or Google Meet
By video, over Microsoft Teams or Google Meet
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
- Filling the gaps. If we need more information to judge the job, we send questions by email or propose a quick Teams or Google Meet call.
- A written quote. It lists the scope, a euro price excluding VAT and a realistic start date. No hidden clauses, no items that appear later.
- Your decision. The quote arrives by email. Take whatever time you need, raise questions on any line, and decide when you are ready.