How to Migrate from WordPress to OS iXanagi — The Complete 8-Step Migration Pipeline

Most companies approach a WordPress migration as a "content move": export posts, import them somewhere else, redirect the old URLs, done. This mindset is precisely what makes migrations difficult and disappointing.

Copying WordPress content as-is into another system produces no meaningful benefit. The reason is structural. WordPress stores content as flat text — a wp_posts table full of HTML strings. OS iXanagi stores content as Meaning Objects: structured entries with semantic tags, locale pairings, domain classifications, and relational connections to other objects in the system.

Consider a sentence on your WordPress site: "Our platform reduces operational costs by 30% compared to legacy solutions." In WordPress, this is a string. In OS iXanagi, it becomes a Meaning Object tagged as a value proposition, classified under the Financial and Demand domains, connected to the relevant product page via an explicit Relation, and available to AI Agents as structured context for proposals, sales responses, and content generation.

The move from WordPress to OS iXanagi is not relocation. It is renovation — rebuilding the informational foundation of your business with meaning at its core.

Before any migration work begins, you need a clear inventory of what exists in your current WordPress installation. The data elements that require migration consideration include: posts, pages, media files, custom fields, plugin configurations, comments, and user data.

Content volume and types Count your total published posts and pages. Identify any custom post types (CPTs). Document all meta fields managed by plugins such as Advanced Custom Fields (ACF). This inventory directly determines migration scope and timeline.

Plugin dependency analysis The average business WordPress site runs 20 to 50 active plugins (industry standard). The single largest migration challenge is rebuilding plugin functionality in the new system — a finding confirmed by Focus Reactive's 2026 research, which named plugin replacement as the top migration obstacle above content quality or volume. Each plugin needs to be mapped to an OS iXanagi equivalent: contact forms become Pledge Set interactions, SEO plugins are replaced by the Content Publish workflow, and custom data plugins are rebuilt as structured Knowledge Objects.

URL and SEO asset documentation Record every current URL pattern, taxonomy structure, and meta configuration. This becomes the input for the redirect mapping strategy that protects SEO ranking during and after migration.

With this audit complete, the 8-step Pipeline can begin.

The Migration Pipeline divides the work into eight discrete phases. Each phase has a clear separation between what AI handles automatically and what requires human judgment.

Step 1: Import — Bringing WordPress Content In

What AI does: Parses the WordPress XML export (WXR file), normalizes post data, page data, media metadata, and custom field values into OS iXanagi's internal Source format.

What humans do: Run the WordPress exporter, upload the file to OS iXanagi Source Import. The technical overhead at this stage is minimal.

At the end of this step, all WordPress content exists in OS iXanagi as raw Source Items — unprocessed input material, not yet converted to Meaning Objects.

Step 2: Extraction — AI Extracts Meaning from Content

What AI does: Analyzes each piece of imported content and infers its semantic function. It identifies value propositions, FAQ pairs, customer testimonials, policy statements, and product descriptions. The Knowledge Extraction engine generates Signal candidates — structured extractions with meaning type classifications and confidence scores.

What humans do: Monitor the extraction results as they appear. This step is primarily AI-driven. Human effort is minimal until the Review step.

Step 3: Candidates — Selecting What Gets Migrated

What AI does: Scores each content item for quality, uniqueness, and strategic relevance. Flags duplicates, outdated information, and low-value pages.

What humans do: Review AI scoring and make final inclusion decisions. This is a critical business judgment moment: "The 2019 product pricing page has traffic but the prices are wrong — update before migrating." "This post was written for a product we discontinued — exclude it." No AI can make these calls. Only people with business context can.

The quality of what you choose to migrate here directly determines the quality of your OS iXanagi Knowledge Graph after launch.

Step 4: Mapping — Translating WordPress Structure to OS iXanagi Structure

What AI does: Proposes how WordPress categories, tags, and page templates should map to OS iXanagi Meaning Objects, Relations, and Section Types. It suggests Relation Vocabulary connections (e.g., parent_of, contains, labeled_by) between proposed objects.

What humans do: Validate AI mapping proposals in context of business meaning. "This category belongs in the Demand Domain." "This landing page template should use the hero + pillar_grid section pattern." These architectural decisions shape how content will be experienced and how AI Agents will traverse the knowledge graph.

Step 5: Review (HITL) — Humans Verify AI Decisions

What AI does: Assembles all extraction and mapping results into a structured review interface, with proposed Meaning Object definitions, confidence scores, and reasoning visible for each item.

What humans do: Examine each proposed conversion. Accept or reject on an item-by-item basis. This HITL step cannot be bypassed — it is a constitutional requirement of OS iXanagi.

The reason is simple: AI processes content without business context. A sentence like "We serve enterprise clients globally" could be a brand positioning statement, a factual capability claim, or an outdated aspiration that no longer reflects the company. Only a human with context can determine which it is. Getting this right means the Knowledge Graph that powers AI Agents will be accurate from day one.

Step 6: Apply — Confirming as Meaning Objects

What AI does: Converts all accepted items into finalized OS iXanagi Meaning Objects — Draft objects for content, Knowledge Objects for structured rules and insights, FAQ objects for question-answer pairs.

What humans do: Review the generated object list. At this point, what was WordPress text has become structured, semantically tagged, relationally connected objects with locale pairings (EN/JA where applicable).

Step 7: Audit — Scoring Migration Quality 0–100

What AI does: Runs the Projection Audit across all migrated content. Scores quality on a 0–100 scale. Identifies structural problems: isolated pages with no internal links, missing SEO metadata, relation gaps, broken reference targets.

What humans do: Review the audit report. Prioritize fixes based on score. A score of 80 or above is the standard completion threshold before proceeding to publish.

Step 8: Publish — Live Publication with Automatic SEO Application

What AI does: Triggers the Content Publish workflow. Meaning Objects are assembled into Projections (page designs), SEO metadata is generated automatically for both English and Japanese locales, and the Next.js SSR layer renders the final output. Core Web Vitals compliance is validated in the process.

What humans do: Give final publication approval. Decide the DNS cutover timing. Manage the switchover from the live WordPress site to OS iXanagi.

For a detailed look at what changes in your day-to-day operations after Step 8, see article #9 in this series: "Life After WordPress — What Actually Changes."

The Migration Pipeline is designed for zero-downtime migration. Your WordPress site continues operating throughout the entire migration process.

Phase 1 (Steps 1–5): WordPress runs normally. All pipeline work happens in OS iXanagi without any user-facing changes. Zero risk to live traffic.

Phase 2 (Steps 6–7): OS iXanagi staging environment hosts the converted content for internal review and audit. WordPress site still live.

Phase 3 (Step 8): After final approval, publish to OS iXanagi production and execute DNS cutover. All former WordPress URLs are managed through website_url_redirects with 301 redirects preserving SEO equity.

If at any point the migration needs to halt, WordPress remains the live system until DNS is explicitly switched. The pipeline is fully reversible up to the final step.

Industry benchmarks put Headless CMS migration timelines at 2–4 months for small sites and 6–12 months for large sites. OS iXanagi's automated pipeline typically delivers faster results because Steps 1, 2, and 6 are largely automated.

Small sites (under 100 pages): 2–6 weeks. One to two team members can manage the review steps.

Medium sites (100–1,000 pages): 1–3 months. Content review requires marketing team involvement. Mapping decisions require business stakeholder time.

Large sites (1,000+ pages): 3–6 months. Plugin functionality redesign as Pledge Sets is typically the longest phase, alongside content curation decisions at the Candidates step.

There is also a strategic timing argument for moving quickly. Industry research from 2025 shows that 50% of AI-cited content was published within the past 13 weeks. Completing migration and publishing structured Meaning Objects as AIO-ready content early means capturing AI referral traffic before competitors who remain on unstructured WordPress installations.

Q1: What happens to our domain during migration? Your domain remains unchanged. Migration involves switching where the domain points, not changing the domain itself. After DNS cutover, yoursite.com continues to resolve — it simply serves content from OS iXanagi instead of WordPress.

Q2: Will our SEO rankings drop during migration? A properly executed migration minimizes SEO impact. Step 8 automatically applies SEO metadata through the Content Publish workflow. All former WordPress URLs are handled with 301 redirects via the website_url_redirects system. In most cases, Meaning Object-structured content outperforms flat HTML pages for AI-generated answer inclusion, so post-migration traffic trends improve over 3–6 months.

Q3: Which content should we migrate and which should we leave behind? Step 3 provides AI-scored guidance, but the core filter is: does this content reflect current, accurate, and strategically useful information? Content with active search traffic, product and service pages, and knowledge that currently lives only in people's heads are high priority. Content older than 3 years with no traffic and no updates is a candidate for exclusion or fresh creation.

Q4: What happens to our email addresses? Nothing. Email is independent of the website infrastructure. Migration does not touch email services, DNS MX records, or mail server configurations.

Q5: Can we stop the migration partway through? Yes, at any point before Step 8. Steps 1 through 7 involve no changes to the live WordPress site. OS iXanagi operates in parallel in staging mode. You can pause, restart, or abandon the migration without any consequence to the live site.

The migration process begins with understanding what you have. Documenting post count, page count, active plugins, and custom field structures gives you a realistic picture of scope and timeline.

More importantly, it gives you an opportunity to think about what your content actually means — not just what it says. The companies that get the most value from OS iXanagi migration are the ones who approach it as a chance to transform accumulated content into structured organizational knowledge that AI Agents can actually use.

For a technical deep-dive into how WordPress data is converted to OS iXanagi Meaning Objects, see article #8: "Not Content Migration — Meaning Migration."

Ready to discuss your migration? Contact CloudEffects — from WordPress audit to full Migration Pipeline execution, we support every step.

---

Sources:

• Focus Reactive, "WordPress Migration Challenges Report," 2026
• Industry standard: Headless CMS migration timeline benchmarks, 2025
• Industry research 2025: AI content citation recency analysis
• OS iXanagi Documentation: Migration Pipeline 8-Step Process
• OS iXanagi Documentation: Projection Audit Scoring System