Hello Laurent.

Unfortunately, this is still the only way to move Amelia's data to another website. We're going to work on the export/import option, but at this time it's not a priority so I can't provide you with an ETA.

The procedure is still the same:

Once you access your database, from where Amelia needs to be moved, you'll see a list of tables that start with "wp_amelia" (or your_prefix_amelia). You need to select all those tables, as shown in the screenshot below:

Once you select them, scroll all the way down, and in the "With selected" drop-down click on "Export":

A new screen will be presented which may look different, depending on the database manager you're using and its version, but in short - you don't need to select any specific options, just run a quick export by clicking on the Export button in the bottom:

A new file will be saved to your computer with the name of the database, followed by the ".sql" file extension.

Once you download that file, make sure that Amelia is installed on another site. After it's installed, access its database and check the prefix. If the prefix is the same, select all wp_amelia tables, as you did in the 1st step, and under "With selected" click on drop to delete all those tables.

Then, confirm this action on the next screen, and once you're done you won't see any Amelia tables anymore.

If the prefix is different, open the database_name.sql file and run "Find and Replace". Replace the old prefix (from the original database) with the new prefix and save that file.

Back in the database of the new site, click on "Import" in the top menu:

Select the database_name.sql file, scroll all the way down, and click on Import:

Once that is done, all services, employees, appointments, and so on will be copied from site 1 to site 2. Now, for the settings - go back to the original database and access the "wp_options" database table (or your_prefix_options) and click on the Search button in the upper menu:

Under option_name, type "amelia_settings" and hit Go at the bottom:

This will return one row, so click on "Edit":

When you edit it, under "option_value", you'll see a JSON input. This can be copied into the same location on another site, so select all the text in there:

Copy it, and then access the same location on the new site (wp_options -> search for "amelia_settings" under option_name and then paste the copied data into the option_value field).

Once you save this, you'll need to modify the Redirect URI of Google and Outlook Calendar, so in the new site, access Amelia/Settings/Integrations/Google Calendar, and replace the domain of the old site with the domain of the new site. In our example, we need to replace "localhost/current":

 with "localhost/lite1":

Switch to the Outlook Calendar tab, and do the same.

If you configured Redirect URL after booking under Amelia/Settings/General Settings, you'll need to replace that as well, along with the Successful Cancellation Redirect URL and Unsuccessful Cancellation Redirect URL found in Amelia Settings/Notification Settings.

That would complete the data migration from one database (site) to another.

Please let me know if you have any follow-up questions about this.

Hello Viorel-Cosmin.

I understand that import/export functionality is important to many users, and we do have plans to implement it this year—though I can't provide a specific ETA yet. In the meantime, the manual migration process we outlined is still valid: installing Amelia on the new site, dropping the default Amelia tables, then exporting and importing the database tables from the old site.

If you have any issues following these steps, feel free to reach out, and we'll do our best to assist!

Hi Sylwia.

Yes, the process remains the same—you can migrate everything by copying the phpMyAdmin tables related to Amelia. This will ensure that all services, employees, and appointments are transferred so that Amelia functions the same way on the new site.

To answer your specific questions:

1. Keeping the old site active while testing the new one & updating later

   • Since data in Amelia is constantly changing (new appointments, cancellations, customer updates, etc.), manually updating only the new changes would be very complex due to the relationships between Amelia's database tables.
   • The best approach is to migrate everything again once you're fully ready to switch to the new site. This ensures that all new appointments and changes are carried over without data inconsistencies.
   • If needed, you can first test the migration on a staging environment to verify that everything works as expected before doing the final transfer.

2. Running Amelia on both sites at the same time

   • Yes, Amelia will work on both sites simultaneously while you're testing.
   • However, to continue receiving automatic updates, you'll need to deactivate the purchase code on the old site (Settings > Activation) and activate it on the new site once you're ready to finalize the switch.

3. WooCommerce Integration

   • By default, Amelia creates a generic "Appointment" product when WooCommerce integration is enabled, so this will be automatically created on the new site.
   • If your services/events were linked to specific WooCommerce products, these links will likely be broken after migration because the WooCommerce product IDs won’t match in the new database. You’ll need to manually relink services to their corresponding WooCommerce products through the Service settings in Amelia.
   • Other WooCommerce-related elements (orders, transactions, etc.) are not part of Amelia’s database, so they won’t transfer automatically.

Let me know if you need further clarification!