MODX Evolution to Revolution Migration: Content, Templates, API

We often encounter site owners on MODX Evolution complaining about outdated architecture: PHP 5.6, no PSR compatibility, unpatched vulnerabilities. Evolution uses a procedural approach, global `$modx` objects, while Revolution is modern OOP with <cite>[xPDO ORM](https://docs.modx.com/)</cite>. A dir

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Frequently Asked Questions

Latest works

  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1281
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1237
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    977
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    1026
  • image_website-sbh_0.webp
    Website development for SBH Partners
    1103
  • image_website-_0.webp
    Website development for Red Pear
    550

We often encounter site owners on MODX Evolution complaining about outdated architecture: PHP 5.6, no PSR compatibility, unpatched vulnerabilities. Evolution uses a procedural approach, global $modx objects, while Revolution is modern OOP with xPDO ORM. A direct upgrade is impossible — a full migration with code rework is required. Our MODX Evolution migration service transfers all content, templates, and custom code, ensuring a smooth transition and SEO preservation. Evolution does not support modern caching and autoloading standards, leading to slow performance and scalability issues. Revolution provides built-in caching, PSR-compatible classes, and a flexible event system. For example, in Evolution, to output a list of documents you had to write direct SQL queries, increasing the risk of SQL injection. In Revolution, this is handled via xPDO with automatic escaping.

Key Benefits of MODX Evolution Migration

Switching to Revolution delivers measurable benefits: average page load time is halved thanks to built-in caching, old architecture vulnerabilities are eliminated, and access to modern packages and autoloading is gained. Hosting cost savings can reach 30% — for a typical site with 50 resources, that means saving $500–$2000 annually on hosting. Additionally, Revolution supports PHP 8.x, extending the site's lifecycle. Support and development costs are reduced by up to 40%.

What is Migrated in MODX Evolution Migration

Component Method
Resources (pages) Export to JSON, import via Revolution API
TV parameters Keep name mapping
Templates Rewritten as Revolution chunks
Snippets Refactored for new API
Plugins Rewritten using Revolution events
Images Rsync from assets/
Users Import via API

The folder structure for images is usually identical, but paths in content may change. We automate replacement via regex or manual mapping.

MODX Evolution Migration Process

The migration follows these steps:

  1. Audit – we analyze the current site structure.
  2. Export – we export all data to JSON.
  3. Import – we import into Revolution.
  4. Refactor – we rewrite snippets and plugins.
  5. Test – we thoroughly test the new site.

Step 1: Analysis of the Current Site

Before migration, we conduct an audit: collect data on templates, TV parameters, snippets, and plugins. Example SQL query to estimate workload:

-- Count documents by template SELECT t.templatename, COUNT(d.id) as count FROM site_content d JOIN site_templates t ON t.id = d.template GROUP BY t.templatename; -- TV parameters SELECT tv.caption, tv.type, COUNT(tvv.id) as used FROM site_tmplvars tv LEFT JOIN site_tmplvar_contentvalues tvv ON tv.id = tvv.tmplvarid GROUP BY tv.id; -- Custom snippets SELECT name, LENGTH(snippet) as size FROM site_snippets; -- Plugins SELECT name, plugincode FROM site_plugins WHERE disabled = 0; 

Step 2: TV Parameters Migration

TV parameters are mapped by name. If in Evolution the field was called color, it remains color in Revolution. It is important to check types: in Evolution, the TV type may differ from Revolution (e.g., text field vs. text area). We adjust types manually. Additionally, we configure access to TVs via Revolution system settings.

Step 3: Snippets and Plugins Migration

Evolution snippets are written in procedural style with global $modx. The Revolution API is different. For example:

// Evolution (old API) $docs = $modx->getDocuments($parents = [5], $published = 1); // Revolution (correct API) $c = $modx->newQuery('modResource'); $c->where(['parent' => 5, 'published' => 1]); $docs = $modx->getCollection('modResource', $c); 

Snippets need to be rewritten. For typical tasks (listing, menus, forms), use ready-made Revolution extras: pdoResources, pdoMenu, FormIt. This speeds up development and reduces error probability.

Step 4: Images and Files Migration

# Image structure is identical (assets/images/) rsync -avz old-server:/var/www/evo-site/assets/images/ \ /var/www/revo-site/assets/images/ 

Detailed Migration Checklist

  1. Inventory all Evolution components (templates, snippets, plugins, TVs).
  2. Export database and assets to JSON and folders.
  3. Install Revolution with required packages.
  4. Map old TV names to new Revolution TVs.
  5. Rewrite each snippet to use xPDO queries.
  6. Convert plugins to Revolution events.
  7. Import content via Revolution API with proper resource IDs.
  8. Adjust all internal links and image paths.
  9. Set up 301 redirects for changed URLs.
  10. Test all functionality on staging environment.
  11. Perform load testing to verify performance gains.
  12. Deploy to production and monitor.

Real Case: E-commerce Store in 4 Weeks

Our client had an e-commerce store on Evolution with 300 resources, 20 snippets, and 10 TVs. We completed the MODX Evolution migration in 4 weeks. Key issues:

  • The cart snippet used direct SQL queries — rewritten to xPDO.
  • Templates contained outdated [+...+]] tags — replaced with Revolution [[+...]].
  • URL structure changed, .htaccess redirects configured.

The client noted: "Loading speed increased by 40%, and server load dropped by half."

Result: page load speed increased by 40% thanks to Revolution caching, vulnerabilities eliminated, server load reduced. Hosting savings up to 30% (about $500/year). Want the same? Order a free audit of your Evolution site.

Performance Comparison: Evolution vs Revolution

Revolution loads pages 2 times faster than Evolution, confirming its superior performance.

Parameter Evolution Revolution
Average page load time 1.2 sec 0.6 sec
Memory usage 32 MB 48 MB
Caching None Built-in (SQL, file)

Revolution is 2x faster in load time, and caching reduces server load.

Timeline and Cost

Site Type Timeline Starting Price
Simple site (up to 50 resources, standard snippets) 1–2 weeks $1,500
Medium (100–500 resources, custom snippets) 3–5 weeks $3,000
Large (1000+ resources, complex functionality) 2–3 months $10,000

Costs are project-based; final estimate after audit.

What's Included in the Work

  • Audit: analysis of templates, snippets, TVs, plugins.
  • Export: all data preserved as JSON.
  • Revolution setup: installation and caching configuration.
  • Migration: content import with template and snippet refactoring.
  • File transfer: image sync with automatic path fixes.
  • SEO preservation: 301 redirects for URL continuity.
  • Testing: staging environment verification.
  • Documentation: admin guide and training.
  • Post-release support: 30 days free bug fixes.

Why Trust Us

  • 10+ years of experience with both MODX versions.
  • Over 50 completed MODX Evolution migration projects.
  • Certified MODX Revolution engineers.
  • Quality guarantee: free bug fixes within 30 days.

Contact us for a free workload assessment. Order migration and forget about Evolution issues. Get a consultation within 2 business days.