42WORKS MULTISITE CPT MIGRATOR
42Works Multisite CPT Migrator compatibility with REEID Translate
42Works Multisite CPT Migrator compatibility with REEID Translate is being reviewed using official plugin documentation. Copies standard post fields (title, content, excerpt, date, menu order) between WordPress Multisite subsites as a fresh draft. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What 42Works Multisite CPT Migrator does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
42Works Multisite CPT Migrator is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How 42Works Multisite CPT Migrator compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Copies standard post fields (title, content, excerpt, date, menu order) between WordPress Multisite subsites as a fresh draft.
- Clones featured images by re-uploading them into the target subsite’s media library (not linking across sites).
- Transfers ACF field values, including deeply nested repeaters, groups, and flexible content, and re-uploads referenced attachments into the target subsite’s media library.
- Re-resolves post references (post_object, relationship, page_link) on the target by slug and post type; leaves references empty and flags issues when clean transfer isn’t possible.
- Re-resolves page parent relationships by slug on the target.
- Matches taxonomy terms by slug and auto-creates missing terms on the target.
- Flags transfer problems on the cloned draft with a yellow warning panel (e.g., failed image copies, missing referenced posts, missing page parents, auto-created taxonomy terms, and ACF field-group drift), and the panel disappears after the first publish or can be dismissed manually.
TRANSLATION BOUNDARY
42Works Multisite CPT Migrator capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
42Works Multisite CPT Migrator and REEID Translate FAQ.
What does 42Works Multisite CPT Migrator do?
42Works Multisite CPT Migrator has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does 42Works Multisite CPT Migrator have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from 42Works Multisite CPT Migrator?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate 42Works Multisite CPT Migrator in a multilingual WordPress workflow.
REEID documents 42Works Multisite CPT Migrator functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.