CAFE Connector: migrations into CAFE
The CAFE Connector moves data from somewhere else into CAFE fields: custom fields an
old theme left behind, Advanced Custom Fields (ACF), tables of an old system, CSV and
JSON files, or any source a developer connects. You use it in CAFE → Migration, with
WP-CLI (wp cafe migration), or from your own PHP code (cafe_import_object()).
Source (WordPress meta, ACF, database table, CSV, JSON, your own)
↓ read in batches (the source is never changed)
Map → Transform → Validate → Preview / dry run
↓
Import: WordPress fields with WordPress functions, CAFE values with CAFE's public API
↓
CAFE Core (storage, cache, bulk loading): imported values work everywhere,
templates, REST, Elementor, WPML
The Connector is not a second CAFE: it has no storage of its own for values and never
writes to CAFE's database tables. Every value goes through the same API as
cafe_save_values(), so validation, sanitizing, WPML behavior and cache clearing are
exactly those of CAFE Core.
Pages
| Page | For |
|---|---|
| Using CAFE → Migration | Step by step in wp-admin: source, target, mapping, preview, dry run, import, history, rollback |
| Sources: WordPress, CSV, JSON | Moving old custom fields; importing spreadsheets and exports |
| ACF → CAFE | Converting this site from ACF: 11 steps, verification, frontend code, removing ACF data |
| Tables of an old system | Tables of an old system, with lists (Collections) from a second table: full example |
| Transformations | Every built-in transformation, and writing your own |
| Relationships, taxonomy and users | Old IDs → new IDs, terms, users |
| Media | Images and galleries by ID, URL or path |
| Runs: dry run, batches, recovery, rollback | What happens when you import, and how to undo it |
| Custom PHP migrations | Your own migration code with cafe_import_object(): full example |
| Custom sources | Connecting a system CAFE cannot read by itself |
| Security and performance | What the Connector checks, and how it stays fast |
Limits
- Sources are read, never written. A rollback undoes what CAFE wrote; it cannot undo changes you made to the old system.
- Users are updated, never created.
- Files (CSV/JSON) are read in the browser and stored with the migration: at most 5 MB. Larger files: WP-CLI with a custom source or custom PHP.
- The Table of an old system source reads tables of this site's database with this site's table prefix.
- Media files are never downloaded automatically (see Media).