Migrating from Aiomatic

What changed when Aiomatic became Aimogen Pro, which technical identifiers stayed the same, how to migrate a legacy licence, and what existing sites need to do.

The plugin was renamed from Aiomatic to Aimogen in version 2.6.3. The premium edition is now Aimogen Pro.

The short version: an existing Aiomatic install does not need to do anything. The rename was deliberately surface-only. Nothing in the database was renamed, no shortcodes changed, no hooks were removed and no settings were migrated, because none of them needed to be.

What changed#

Technical identifiers keep the Aiomatic name#

This is intentional. Renaming an option key, a shortcode or a hook would break every existing site, every custom snippet and every third-party integration. So they stayed.

Examples you will encounter:

// Options
get_option( 'aiomatic_Main_Settings' );
get_option( 'aiomatic_Chatbot_Settings' );

// Shortcodes - both spellings are registered and identical
[aimogen-chat-form]
[aiomatic-chat-form]

// Filters
add_filter( 'aiomatic_modify_ai_query', ... );

// REST namespace
/wp-json/aiomatic/v1/text

// Capability
current_user_can( 'access_aiomatic_menu' );

// Database tables
{$wpdb->prefix}aiomatic_logs

The complete list is at Legacy Aiomatic identifiers.

Migrating a legacy licence#

If you bought the plugin as Aiomatic on Envato, your purchase code is in the Envato UUID format (8charact-xxxx-xxxx-xxxx-12charactersx). Aimogen Pro still accepts it.

The plugin recognises both formats:

You may see a banner inviting you to migrate the licence to WPBay. Migration gives you WPBay-managed renewals and support.

To migrate, follow the migration section on the Aimogen Pro product page. The announcement video explaining the rename and the migration is linked from Aimogen Pro › Settings › Activation.

Upgrading an existing Aiomatic install#

1. Update normally. Use the built-in updater. Settings, rules, chatbots, logs and generated posts are preserved.
2. Expect the folder name to change. If you update through WordPress the folder is handled for you. If you install manually, use aimogen-pro.
3. Menus moved. From 2.8.1 the single creators, bulk creators and forum creators live together under AI Content Creators; "Limits & Statistics" and "Logs & Translations" merged into System & Logs; the developer screens sit under Advanced Tools ▾. See The admin interface.
4. Check your models. Recent releases removed retired models. See Updating Aimogen Pro.
5. Your workspace is untouched. Because aiomatic_default_workspace does not exist on an upgraded site, you keep the full menu. See Workspace.

Custom code written against Aiomatic#

Existing snippets keep working. All the documented filters and actions retained their names, and the aiomatic_* prefixes are stable.

Newer hooks introduced after the rename use the aimogen_ prefix — for example the per-provider API key filters (aimogen_openai_api_key, aimogen_anthropic_api_key) and the PHP API bootstrap action (aimogen_api_ready). Where both exist, the aiomatic_ filter runs after the aimogen_ one, so a legacy filter still has the final word:

$token = apply_filters( 'aimogen_openai_api_key',  $token );
$token = apply_filters( 'aiomatic_openai_api_key', $token );

See Filter reference.

Old tutorials and Knowledge Base articles#

Many videos and Knowledge Base articles were recorded or written under the Aiomatic name. The underlying behaviour is usually still accurate; the branding and occasionally the menu location are not. Where such a video is embedded in this documentation, a note points that out.

Next: Recommended server configuration.