Content migration — from WordPress, Drupal, legacy CMS

Supported sources

• WordPress (any version, including VIP)
• Drupal (7, 8, 9, 10)
• Adobe Experience Manager
• Custom CMS via XML, JSON, or CSV export
• Standard XML newsfeed (NewsML, RSS, Atom)

How migration works

1. Export your existing CMS content (we provide guidance per source CMS).
2. Upload the export to Journalify's migration tool.
3. Pre-migration analysis runs: counts articles, identifies broken links, flags missing media, validates dates and authors.
4. Review the pre-migration report. Decide what to fix in the source vs accept and clean up post-migration.
5. Run the migration. Articles import in batches; a 50,000-article migration typically takes 4–8 hours.
6. URL preservation: every old URL becomes a 301 redirect to the corresponding Journalify URL automatically.

SEO preservation

The migration tool preserves: article URLs (via 301 redirects), publication dates, author attribution, meta descriptions, focus keywords, and OG images. Google typically reindexes within 1–2 weeks with no ranking loss.

Media migration

All images, videos, and documents are copied into Journalify's DAM with EXIF preserved. Image references in article bodies are rewritten automatically to point at the new locations.

Zero-downtime migration

The standard pattern: keep the old CMS running while Journalify imports content in parallel. When ready, swap your DNS to point at Journalify; the old CMS stays running for a week as fallback before being decommissioned.