# Migrate a WordPress Site with Agent Starter: B0, F1, B1, and C1

Agent Starter's Migration Foundation workflow prepares an existing-site migration in two passes. The first pass establishes the destination's design and structure. The second pass creates the rules Agent Composer will follow when producing content.

This separation prevents a content plan from being generated for a version of the site that no longer exists.

The Starter interface sometimes calls an uploaded proposal a **candidate**, and calls its first automated check **preflight**. A candidate is simply a proposal waiting for review; preflight checks whether it is safe and compatible with the current site.

## When should I use Migration Foundation?

Use it when you are rebuilding or substantially redesigning an existing public site and need a site-specific Canvas foundation. For a new site that fits one of Starter's four standard structures, use the normal Starter import workflow instead.

Before starting:

- install and activate Agent Canvas and Agent Starter;
- install Agent Composer if the new site will use governed content generation;
- install every plugin that provides a required block, content type, taxonomy, field or relationship;
- collect source material you are allowed to use, along with decisions about site structure, language and media rights.

The included public-site profiler helps collect information about the source site. It does not make changes or create the migration proposal by itself, and it should only be used on a site you are authorized to analyze.

## What do B0, F1, B1, and C1 mean?

| Stage | Meaning | Does it change WordPress? |
| --- | --- | --- |
| **B0** | A read-only snapshot of the destination before Foundation changes. | No. |
| **F1** | The proposed site foundation generated from B0 and reviewed source material. | Only after Starter's checks, preview and explicit activation. |
| **B1** | A new read-only snapshot taken after F1 has been applied. | No. |
| **C1** | The content-governance proposal generated from B1, normally including a draft Composer Config Set. | Starter may import the draft, but it remains inactive. |

B0 and B1 are observations. F1 and C1 are proposals. B1 is not the Composer proposal; C1 is the proposal produced from B1.

A useful analogy is:

- B0 is the first survey of a building;
- F1 is the reviewed renovation plan;
- B1 is the survey after the renovation has been completed;
- C1 is the operating handbook for people working in the finished building.

## Pass 1: capture B0 and apply F1

Download the Migration Foundation agent kit from **Appearance > Agent Starter**. The kit contains B0, a description of the Canvas design, the files and instructions needed to prepare a proposal, and a read-only profiler. Downloading it does not change the site or send data to an AI service.

Provide the kit, authorized source material and your site decisions to your chosen AI model or reviewed authoring process. The returned F1 proposal can include:

- site colors, typography, spacing and other supported Canvas design choices;
- WordPress Custom CSS and shared styling for WP Suite plugin interfaces;
- navigation;
- header, footer and template customizations stored safely by WordPress;
- reusable site-owned user patterns;
- an optional draft Composer configuration, imported but left inactive.

F1 cannot:

- change Canvas theme files or create a new theme ZIP;
- replace Canvas's built-in design settings, release information or built-in patterns;
- install plugins or generate theme/plugin source-code files;
- register custom post types, taxonomies, fields or relationships;
- publish ordinary content;
- activate a Composer Config Set.

Required content types, attached taxonomies, fields, and relation storage must already be supplied by WordPress or reviewed site/provider plugins. Starter checks what is really available on the destination instead of accepting unsupported items from the proposal. It may import inactive Composer relation and taxonomy-access contracts, but it does not register the data model or duplicate their abilities; the provider owns the model and Composer owns the generic governed workflows.

### What do Starter's checks and preview do?

**Starter's checks** confirm that F1 belongs to the current B0, has the expected format, uses available blocks and content types, and contains no passwords, secret keys, executable code or unanswered decisions that make activation unsafe. Saving the proposal for review does not change the site's appearance.

**Preview** shows a human-readable list of everything Starter proposes to change and checks compatibility again. It is a preview of the changes, not a picture of the finished website.

**Starter activation** reads the destination again and applies F1 only if the site and proposal still match what you reviewed. If the site changed in the meantime, activation stops and you must create or review a new proposal. Starter records the applied changes so they can be rolled back safely.

## Pass 2: capture B1 and generate C1

After F1 activation, inspect the site visually. Then download a fresh **content-governance** kit. Its new destination snapshot is B1.

B1 reflects the foundation that now really exists: current styles, templates, navigation, user patterns, installed plugins and registered content types. Never reuse B0 for the second pass.

Generate C1 from B1, the reviewed content strategy and representative source material. C1 should usually preserve the applied design and define:

- the Config Set that keeps the rules together;
- the Site Contract, including language, allowed content types, fields, templates, media rules and which installed plugins may provide features;
- Blueprints for the page and content types an agent may create;
- which Blueprints use Gutenberg documents and which use structured fields;
- permitted patterns, blocks, relationships, taxonomy access, SEO and editorial rules.

C1 creates governance, not articles or pages. Actual content is generated later as governed drafts.

## Why does the Composer Config Set need separate activation?

There are two different activations:

1. **Starter proposal activation** applies the reviewed migration changes and imports the Composer configuration as an inactive draft.
2. **Composer Config Set activation** happens later, after a human inspects the imported Site Contract and Blueprints and Composer validates the complete configuration.

After C1 is activated in Starter:

1. Open **SmartCloud > Agent Composer**.
2. Inspect the imported Config Set, Site Contract and Blueprints.
3. Run Composer validation.
4. Resolve every reported issue.
5. Explicitly activate the validated Config Set.
6. Create and review representative drafts before generating content at scale.

Starter never makes imported rules active for content generation without this separate approval.

## What if F1 already imported a draft Composer configuration?

B1 includes only the Composer Config Set that is currently active. A draft configuration imported by F1 is not automatically included in B1.

If C1 must refine that draft, include it when preparing C1, or deliberately validate and activate it in Composer before taking a later snapshot. Do not reuse the same Config Set identifier for a different configuration; Starter reports a conflict instead of replacing it.

## What makes a proposal outdated?

A proposal becomes outdated when the destination no longer matches the snapshot on which it was based. Examples include changes to styles, templates, navigation, user patterns, installed plugins, registered content types or the active Composer configuration.

Download a fresh kit and create a new proposal. Then run Starter's checks again and review the new list of changes. This is safer than trying to force an older proposal onto a site that has moved on.

## Related guides

- [Agent Starter overview](https://wpsuite.io/docs/agent-starter/overview)
- [Standard Starter import workflow](https://wpsuite.io/docs/agent-starter/import-workflow)
- [Agent Starter integrations](https://wpsuite.io/docs/agent-starter/integrations)
- [Agent Starter troubleshooting](https://wpsuite.io/docs/agent-starter/troubleshooting)
- [Agent Canvas setup](https://wpsuite.io/docs/agent-canvas/setup)
- [Agent Composer configuration](https://wpsuite.io/docs/agent-composer/configuration)
- [Create governed drafts through Composer](https://wpsuite.io/docs/agent-composer/direct-mcp)