We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #2717042
backing up amelia data
Closed

Comments

  • Thomas Hönemann started the conversation

    Hallo everyone,

    we are going to migrate our website to a new WordPress installation WITHOUT restoring the old xml-database as it includes too many bugs ...

    Is it possible to seperately back up the amelia data and settings to an external file (independent from the xml-Database) and to restore it after migration, so that we do not have to reiterate all the entries (e. g. we have nearly 100 employees)? 

    Or ist there another chance to grab the entries from the code and to restore it in the new installation?

    This would be really helpfull.

    Best regards from Germany!

    Thomas

  • [deleted] replied

    Hi, Thomas!

    I apologize for the delayed response.

    And thank you for choosing Amelia.

    I'm afraid, other than cloning the website, the only available option is to copy all 47 wp_amelia database tables, and option_name "amelia_settings" from your wp_options database table.

    In this case, when you move the site, you should import all wp_amelia database tables, and overwrite the option_value column in wp_options (when you search for option_name "amelia_settings").

    Not sure if that's what you're looking for, but it can't be achieved without copying the database tables.

    If you have any other questions, please let us know.

    Best Regards. 

  • Thomas Hönemann replied

    Thank, you, Liza, for your answer. I will do my very best to follow that steps, and hope I will get all the data migrated.

    Maybe it would be an idea to equip the plugin with a backup-tool?

    Best regards,

    Thomas

  • [deleted] replied

    Hi, Thomas!

    That's a great idea. And we are always looking for ideas on how to make Amelia better. So if you have a couple of minutes, please suggest this feature on our website.

    Let us know if you have any other questions, we will gladly help you out.

    Best Regards.

  • Thomas Hönemann replied

    Good morning Liz, I tried several times to post my suggestion on the board, but unfortunately it does noch work. MAybe you can copy it into the board as follows?

    Making it possible to back up Amelia data (seperately) - would be very helpful in any case of crash or migration of the WP database.

  • [deleted] replied

    Hi again, Thomas!

    I will send your suggestion directly to our project manager since we have no access to the feature request page.

    Thank you for your time.

    Best Regards.