Skip to end of banner
Go to start of banner

How to Export and Import Polls data from one Confluence instance to another for the Polls for Confluence app

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This article describes how to export and import Polls data from one Confluence instance to another for the Polls for Confluence app.

Introduction:

Polls data in Confluence is not specific to a particular space but is global for the entire Confluence instance. Therefore, standard space export/import operations do not restore poll data. However, there are two cases in which you can export/import poll data.

Case1:

If you want to migrate to another Confluence instance fully, the following steps are required:

  • Backup Confluence data from source instance to a file: Administration → Backup & Restore → Export this site → Export

  • On destination Confluence instance:

    • Install Polls for Confluence app

    • Import backup file: Administration → Backup & Restore → Import Confluence data, choose archive file, click Upload and Import

    • After this, you should have all Polls for Confluence app data on the destination Confluence instance

Case2:

If you don’t want to migrate the whole Confluence instance data and move Polls for Confluence app data, you can follow these steps:

  • On the source Confluence instance, dump the data of the following tables:

    • AO_7CB12A_OPTION_ENTITY

    • AO_7CB12A_POLL_ENTITY

    • AO_7CB12A_VOTE_ENTITY

  • On a destination Confluence instance:

    • Install Polls for Confluence app.

    • Update the license for Polls for Confluence app.

    • Restore the date of dumped tables.

    • Now, you should have all Polls for Confluence app data imported into the destination instance.



  • Ensure to take the back up of the database before proceeding.

  • We always recommend to test the app data migration in a staging environment first and then proceed in the production instance.

  • Ensure you have appropriate administrative privileges on the source and destination Confluence instances.

  • No labels