Upgrading from ElmapiCMS v2
Important Notice
ElmapiCMS 3.x was a complete rewrite of v2, with a new architecture, database structure, and API design. Direct upgrading from v2 to 3.x (or 4.0) is not supported.
Current docs describe ElmapiCMS 4.0. If you are still on v2, plan a fresh install and content migration rather than an in-place upgrade.
What Changed since v2
Architecture
- Laravel-based backend with a React + TypeScript admin (Inertia.js)
- Projects, collections, and content model redesigned vs v2
API
- RESTful content and asset APIs with filtering, localization, and (in 4.0) versioning
Migration Options
Option 1: Fresh Installation (Recommended)
- Install ElmapiCMS 4.0 in a new environment
- Recreate your content structure using collections and fields
- Migrate content manually or via API
- Update your frontend applications to the current API (and JS SDK 1.0 if you use it)
Option 2: Parallel Installation
- Keep v2 running for existing applications
- Install 4.0 alongside for new projects
- Gradually migrate projects as needed
Option 3: Content Export/Import
- Export your v2 content via API or database
- Transform the data to match the current schema
- Import into 4.0 (project/collection import or API)
- Update your applications to use 4.0
Next step from 3.3
If you already run 3.3, use Upgrading to 4.0 instead of this page.
Legacy v2 Support
ElmapiCMS v2 no longer receives new features. Migrate to 4.0 when you can.