What Happens to My WordPress Plugins After Migration?
WordPress plugins don't transfer to VeloCMS — but most plugin functionality has a native equivalent. Here's the substitution map.
WordPress plugins don't come with you when you migrate — VeloCMS doesn't run PHP and can't execute plugin code. What you get instead is native functionality built into the platform for the most common plugin use cases.
What replaces the most popular WordPress plugins?
Yoast SEO and Rank Math map directly to VeloCMS's built-in SEO panel — meta title, meta description, focus keyword, Open Graph, Twitter Card, and JSON-LD are all there without a plugin. Mailchimp and Mailerlite for newsletters are replaced by the built-in newsletter system with campaigns and subscriber management. WooCommerce for simple digital products maps to the VeloCMS shop module. Contact Form 7 and Gravity Forms have no direct replacement yet — embedded Tally or Typeform forms via an embed block are the current workaround.
What about security plugins like Wordfence?
Security plugins exist on WordPress because WordPress is inherently exposed — the admin panel lives at /wp-admin, PHP files are public, and plugins run arbitrary code. VeloCMS doesn't have any of that attack surface. There's no plugin-layer to exploit, no PHP interpreter, and the admin dashboard requires authentication to load a single byte. You don't need a Wordfence equivalent because the threat model is fundamentally different.
What if I used a plugin for something VeloCMS can't do yet?
The migration wizard flags any plugin in your WXR export that doesn't have a direct VeloCMS equivalent and shows a warning card for each one. The warning tells you what the plugin did and what the current workaround is. Some of those workarounds are embed blocks (iframes to third-party tools), some are on the VeloCMS roadmap with a rough ETA, and some genuinely don't exist yet. The wizard won't silently drop that functionality — you'll know before you commit to the migration.
Plugin data (WooCommerce orders, form submissions, ACF field values) is not migrated — only post content, media, and SEO metadata transfer. Export that data separately from WordPress before you take the site down.
Will I lose my plugin-created custom post types?
Custom post types from plugins come through the WXR export as HTML content in standard post records. The migration wizard converts them into VeloCMS posts, preserving the content body, title, slug, and publication date. The plugin-specific metadata fields (like ACF custom fields) don't transfer because VeloCMS doesn't have a matching schema. You'll see those posts in your drafts after migration and can decide whether to add the missing information manually or leave it out.