We are going to make the assumption that the reader is familiar with certain basic working aspects of Revo and Evo for the purposes of this tutorial.

At this time Provisioner can import from Evolution sites and Revolution pre 2.2, and supports Revolution 2.0 - 2.2.x using mysql and sqlsrv as the target.

If you have been using MODX for any time now, you recognize the important improvements in the latest release of MODX Revolution. You also probably have many sites developed on the MODX Evolution platform. Although the Evolution platform works fantastic for what it was tasked to do, Revolution offers a great many performance and functionality improvements to merit an upgrade.

If this applies to you we have some good news. There is a tool called Provisioner that will translate your older Evo or Revo data directly into a new Revo install. Utilizing Provisioner and some minor tweaks, this process should be a lot less painful than you might expect.

In the past to migrate one MODX site to a new MODX install, some database experience would be necessary. A series of export/import sql tasks were required and depending on the version of MODX, may or may not be quite as simple as that.

Another approach would be to manually copy content from one manager instance to another. Depending on the size of the site, this may not be an option.

Provisioner provides the tool to help you in your migration without the need to start digging around the databases or spending hours on end copying and pasting.

We'll begin by installing Provisioner to your new instance of MODX Revolution. Provisioner is installed via Package Manager (for more info on Package Manager...). You can also install manually by downloading the transport file and unzipping it in your packages directory and perform a local install.

For Evolution sites, you'll need to install the gateway code to the source MODX instance. Download the revogateway.zip file and unzip it to the assets/snippets/ folder. This will allow Provisioner to access the necessary files. This allows read only access to the data needed for Provisioner.

Once you have completed the installation of Provisioner and the revo gateway, go to your new site manager. If you are already in the manager be sure to refresh the browser window to reload the menu bar. It would also be a good idea to clear your cache at this point. "Provisioner" should now appear under the "Components" menu item.


Click on the Provisioner component and log into the remote (source) site from the administration tab by filling in your remote site account details. In the URL field you will need to enter the URL to the "connectors" directory for Revo sites and the site URL for Evo sites. Be sure that the user account you enter has sufficient privileges for the operations to function. Admin privileges should be adequate.


Choose the remote site type.

Now you must supply a site identifier. This is an API key that allows the AJAX calls between the frontend and backend. This can be found near the top of the config.inc.php file.

You must be logged in to the remote site through Provisioner to continue.

It is recommended that you begin importing the remote site to a clean or empty MODX install.

If you have installed Provisioner correctly and successfully logged into the remote site you will see the corresponding data for the Resources, Elements, Files, Packages... listed as tabs in Provisioner.


From these tabs you can pick and choose which resources, elements, files etc are imported with a few options for each. Simply right click the resources you want and import as needed. It will also offer you the option of reformatting the syntax of MODX tags to match your new installation.

There is also a bulk import option under the "Evolution Site Import" tab. This option will allow you to import your remote site without having to select items one at a time. Evo to Revo tag conversion is automatic when performing this action.


It is not recommended that you import plugins as they were not written to function in Revo.

Packages are also something that should be managed with great care as the older packages will overwrite the newer ones on import.

Hi. We’re MODX.

We’re here to help you fix, build and grow fantastic sites. How can we help?

How can we help?

Tell us the general reason for reaching out so we can connect you with the right team.

MODX Diagnostics

MODX’s Open Source software is 100% free for anyone to download and use. As the team behind it for more than a decade, we know it inside, out, and then some.

Like any software, sometimes things break; we can usually fix them very fast. But, we do have to charge for our time to support our families and fund its ongoing development. There are almost an unlimited variety of things that can cause problems, including server upgrades, corrupt files, accidental changes, outdated software, database hiccups and more. We will save you a lot of time and frustration, and get you back in action.

With our MODX Diagnostic service, we determine the source of issues, and often fix them on the spot. For more extensive problems needing more time, like hacked sites or overdue upgrades, we provide additional estimates and guidance. MODX Diagnostics cost $99 for standard business hours support (US Central Time), or $500 for priority, rush or after-hours emergencies.

If you don’t have budget for professional support from the source, you look for answers in the MODX Forums or Documentation, or seek help from MODXers in the Community Slack, or from MODX Professionals near you.

  I’m not ready to pay, let’s talk…

After submitting this form and completing payment, we will collect your access credentials in a secure support ticket. We look forward to helping restore your site back to full health.

Hi! We’d love to work together.

If you have a simple problem that needs our assistance, please request quick fix help here.

What should we keep in mind?

The project involves:
(select all that apply)
What are you planning?
(select all that apply)

Some other considerations

Specific project information

Commercial Support Customers

Customers with a current Commercial Support agreeement can get help using this form. Learn more about MODX Preferred Support.

Let’s get started

What seems to be the issue?

Contact MODX

We welcome conversations, ideas, inquiries and even the occassional cold sales call, but support and requests about how to use MODX software sent via this form cannot be guaranteed a response. That said, we try to respond to everyone that reaches out to us within two business days.

To report a security issue or file a bug for MODX software, please email security [at] modx.com to reach our security team. If you are looking for help with MODX, many times you can find an answer in the MODX Forums or MODX Documentation, from MODXers in realtime at the MODX Community Slack Channel, or from a MODX Professional near you.

How can we help?