a•abacadigital

WEBSITE SERVICES / CONTENT MIGRATION

Move your website.
Keep useful content working.

Bring eligible pages, text and images from your existing website into an editable CMS and a new design. Review what moves, check the important addresses and agree the switch-over before changing your live website.

Tell us about your existing website ↗

Start with the content
you already have.

Your website may still contain useful service information, project descriptions and articles, even when its design or editing tools need replacing. We assess what should move, what needs updating and what can be left behind.

Send your current address, confirm permission to reuse the content and describe what needs to work on the replacement website. Choose a supported design or discuss a bespoke build where the brief needs more.

Know what is being moved.

This service concerns website content and its presentation. It can prepare eligible public information as CMS drafts; it does not recreate the code or business processes behind the old website.

If you need to upgrade an ASP.NET application, move framework versions or retain a custom booking workflow, we review that work separately.

Looking for .NET application migration? ↗

FROM SOURCE WEBSITE TO REVIEWABLE DRAFTS

A move you can check
at each stage.

1. Discover and select the pages

The scanner follows eligible public links and sitemaps, respecting the source website’s robots.txt rules. Review the discovered addresses and select the pages you want. Add specific URLs when important pages are not linked from a menu or sitemap.

2. Prepare content for the new design

Extracted content is mapped into editable components. Where suitable, AI can help choose a presentation such as image and text, process steps or FAQ. This planning step selects layouts rather than rewriting your source wording. Standard mapping remains available when AI cannot help.

3. Review the preview and addresses

Check headings, images, article types, categories and internal links. Compare proposed destination URLs with important existing addresses. The importer flags uncertain content and problems, so you can correct the result before launch.

4. Save drafts, then plan publication

Imported pages are saved as CMS drafts. Check the design, navigation, forms and content before publishing the agreed pages. Domain changes and redirects need their own launch steps; importing drafts does not switch the existing website over.

RETURN WHEN YOU ARE READY

Move in stages.
Keep the edits you have made.

Import history records which source pages became CMS pages, with their status and destination.

After an import, use “Import more pages” to scan for remaining or newly added content. The importer checks earlier successful imports into the same CMS website and skips recreating pages that are still there.

This keeps your team’s CMS edits intact, including when a page has moved to a different CMS address. Failed or previously excluded pages can be considered later. Source pages may still be scanned to discover new links.

For a larger site, agree priority sections and batches first. Scan and download limits apply, so additional URLs or a scan of a specific section may be needed. Edit imported content in the CMS rather than expecting a later scan to replace it.

Agree what can move,
and what needs rebuilding.

Content we can assess for import

  • Public company, service and information pages.
  • Eligible news, blog and other article content.
  • Supported images you have permission to reuse.
  • Page headings, descriptions and links.
  • Language versions where the source structure can be identified and reviewed.

The result depends on the source structure, available content and selected template. We review representative pages before agreeing the scope.

Functionality needing separate work

  • Bookings, checkout, payments and customer accounts.
  • Content behind logins or blocked from scanning.
  • Application code, plugins and third-party integrations.
  • Interactive tools or content available only after JavaScript runs.
  • Designs outside the supported components.

Property and other structured listings need a review of fields, media and presentation. A content scan does not transfer the old application or its hosting configuration.

IMPORTANT DETAILS AT LAUNCH

Check the journey,
including the old links.

Map URLs and review redirects

List important current pages and their destinations. Where an address changes, review the appropriate redirect rather than sending every old URL to the homepage. Check internal links, titles, descriptions, indexing settings and the new sitemap.

Agree where redirects will be hosted and which domain and hosting changes are needed. Some changes depend on access to the existing setup.

Test, switch over and monitor

Review representative pages on desktop and mobile, test enquiry delivery and check navigation before launch. Agree responsibilities, switch-over steps and a recovery approach appropriate to the website.

After launch, check important old addresses and monitor indexing, crawl errors and search traffic where access is available. Search visibility can change during a move; we do not promise unchanged rankings.

Google’s site-move guidance covers preparation, URL mapping, redirects and monitoring. The checks for your website depend on what is changing.

AFTER THE MOVE

Keep managing
the website yourself.

Edit pages, organise media, maintain articles and staff profiles, and manage language versions. We provide a handover for the agreed website and can discuss support and further development.

See what your team can manage ↗

WEBSITE EXPERIENCE

Content management
with a long working life.

Our Synergy Estate project covers multilingual website design and CMS development, with ongoing support. Our involvement in Isle of Man Rent a Car began in 2010 through another agency, covering the CMS, booking system and database.

These projects demonstrate development and support experience. The current import tool was not used to build those earlier websites.

QUESTIONS ABOUT MOVING A WEBSITE

Before we start

Can you import a WordPress, Wix or Squarespace website?+

We can assess eligible public content from different platforms. Results depend on how each site presents its pages and images. A scan does not transfer platform accounts, plugins, checkout or other underlying functionality. Send the URL so we can check a representative sample.

Will the new website look exactly like the old one?+

Content is presented using the selected template and components. The importer does not copy the original stylesheets or scripts. If you want to retain a specific design, we assess and quote that implementation separately.

Can we import some pages now and the rest later?+

Yes. Select pages for the first import, then return to import more. History identifies pages already imported into that CMS website and preserves their content. Larger websites may need additional URLs or section scans to work within scan limits.

Will the importer overwrite our CMS changes?+

Repeat imports skip source pages already successfully imported and still present in the CMS. Unrelated existing pages are protected by URL conflict checks. Updating an existing destination through the import workflow requires an explicit choice. Normal editing belongs in the CMS.

Does the small business plan include a website move?+

The plan can cover eligible content on up to 20 standard pages using a ready-made design. Extra pages, bespoke work and application functionality need separate agreement. Read the plan details and terms; we confirm the scope before starting.

What do you need from us?+

Your current URL, permission to reuse the content and images, important pages and functions, and any timing constraints. Mention bookings, payments, logins, languages or integrations. We arrange access separately; do not include passwords or private customer records in the initial form.

What should your
new website carry forward?

Send the current URL and tell us what you want to keep, improve or replace.

Discuss your website move ↗