One hub, 1,332 routes: MigrateMe Universal and the Open Migration Package

Description and use

Content migration across 37 platforms is achieved via a single Universal hub, replacing 1,332 pair‑to‑pair converters, while the Open Migration Package provides a unified import/export format.

Problem

Migrating content between many CMS and builder platforms requires numerous pair‑to‑pair converters, leading to maintenance overhead and opaque loss reporting.

Outcome

Universal reduced the need for 1,332 pair‑to‑pair converters to a single hub with 30 components, and OMP provides a reusable, validated format that can be adopted incrementally by platforms.

Workflow

• Identify source platform and destination platform
• Use Universal web app or CLI to convert via the canonical hub
• Review loss report if route is Lossy
• Export or import OMP package for platform‑agnostic migration
• Validate with OMP schema validator

Evidence

Every migration tool I have used is a pile of pair-to-pair converters. Add a platform and you owe a converter to and from everything else.

Source

Universal refuses that shape: every source parses into one canonical item model, and every destination renders from it.

Source

The converter's registry covers 37 nodes: 21 researched platforms ... and adding platform #38 costs one parser or one renderer, never both.

Source

An OMP package is a manifest.json ... a validator that returns specific errors instead of vibes, and conformance levels — OMP Reader, OMP Writer, OMP Full.

Source

The toolkit itself is free and MIT‑licensed, and the AI step runs a local open‑weight model, so a migration costs nothing to run.

Source