Hello Patrick,

Thank you for reaching out to us.

We do not have access to your data and everything is stored on your server. We do not do migrations and your hosting prvoder should help you with migrations that is their area of expertise, the hosting provider deals with migrations because the databases are stored on their servers. We will help you as best we can.

Other than cloning your website, there's a way to migrate only Amelia's database tables.

There are around 47 tables with wp_amelia_ prefix that need to be moved. Please note that wp_ is the default database prefix, but on your end, it could be anything, so look for your_prefix_amelia_ tables.

Besides that, you also need to go to wp_options and search for option_name "amelia_settings" - that returns one row, so you need to copy the option_value and paste it in the same field on the other site. Note that this contains all info from your old website, so you will need to replace the URLs in this cell.

Hope this helps.

If you have any more questions please open a new ticket for each question and we will gladly help you there.

We wish you all the best.

Have a nice day. 

Hello Patrick,

Sorry if my explanation about moving all "wp_amelia" tables did not suffice, I'll provide more detail. I agree with you that import/export feature is rather important, and I'll make sure to remind our developers of that, so hopefully they'll prioritize it.

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 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 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 Patrick,

We are glad to hear that everything worked, as for adding this to our documentation suggestion I have forwarded your suggestion to the appropriate sector so that it can be reviewed. 

We wish you all the best and have a great holiday. 

Hello Patrick,

We have forwarded your ticket to our level 2 agents and as soon as we get some feedback from them we will contact you immediately.

Hello Patrick,

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Looking forward to your reply. 

Hello Patrick,

We have managed to reset the password and we are looking now for the issue. We will contact you here as soon as we find it.

Talk to you soon. 

Hello Patrick,

It turns out that this was just a caching issue. All should be fine now. If you find any more pages where the booking form is not showing correctly please contact us again and we will gladly take a look.

We wish you all the best. 

Hello Patrick,

As far as I can see, the ticket was assigned to my colleague and he replied to you today. Please continue further conversation with him on that ticket and he will gladly help.

If you have any new questions please open a new separate ticket for each question and we will gladly help you there.

We wish you all the best.

Have a nice day.