CMS to CMS Website Migration

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

Migrating from One CMS to Another

CMS-to-CMS migration is primarily a data migration. Differences in schemas, fields, content types and media files require transformation, not simple copying.

Typical Migration Paths

From To Complexity
WordPress → Strapi Medium Similar CPT concepts
WordPress → Contentful High Different data models
Drupal → Craft CMS High PHP↔PHP, but different abstractions
Joomla → WordPress Medium Official tools exist
Contentful → Sanity Medium Both headless, API migration
Ghost → WordPress Low Ghost has XML export

Export Tools

WordPress — built-in XML Export or WP-CLI:

wp export --post_type=post,page,product --dir=/tmp/wp-export/

Drupal — Migrate API or CSV export:

drush migrate-import --all

Contentful — CMA SDK:

contentful space export --space-id $SPACE_ID --export-dir ./backup

Ghost — Ghost Admin → Settings → Export → Export your content (JSON).

Strapi — custom script via REST API.

Transformation Script

ETL pattern (Extract → Transform → Load):

// scripts/cms-migration.ts
interface MigrationConfig {
  source: 'wordpress' | 'contentful' | 'ghost';
  target: 'strapi' | 'contentful' | 'sanity';
  contentTypes: ContentTypeMapping[];
}

async function migrate(config: MigrationConfig) {
  const extractor = getExtractor(config.source);
  const transformer = getTransformer(config.source, config.target);
  const loader = getLoader(config.target);

  for (const mapping of config.contentTypes) {
    console.log(`Migrating: ${mapping.sourceName} → ${mapping.targetName}`);

    // Extract
    const items = await extractor.extract(mapping.sourceName);

    // Transform
    const transformed = items.map(item => transformer.transform(item, mapping));

    // Load (with batching)
    for (const batch of chunk(transformed, 50)) {
      await loader.load(mapping.targetName, batch);
      await delay(500);
    }
  }
}

Rich Text Migration

Most complex part — transforming Rich Text formats:

// WordPress HTML → Portable Text (Sanity)
import { htmlToPortableText } from '@portabletext/html';

function transformWpContent(html: string) {
  return htmlToPortableText(html, {
    rules: [
      {
        deserialize(el, next, block) {
          if (el.tagName === 'IMG') {
            return block({
              _type: 'image',
              _key: Math.random().toString(36).slice(2),
              src: el.getAttribute('src'),
              alt: el.getAttribute('alt'),
            });
          }
        },
      },
    ],
  });
}

URL Redirect Mapping

After migration, definitely set up 301 redirects:

// Generate mapping of old → new URLs
const redirects = oldPosts.map(old => ({
  source:      old.url,
  destination: newPosts.find(n => n.slug === old.slug)?.url ?? '/blog',
  permanent:   true,
}));

// next.config.ts
async redirects() {
  return redirects;
},

Migration between two headless CMS (1000–5000 items) — 2–4 weeks.