Exporting from legacy pubpub to self-hosted version? #1249
-
Hi Thank-you for developing a self-hosted version of pubpub. Is it correct to assume that it will be possible to export contents from an existing legacy pubpub to a self-hosted version? I've checked out the sandbox, and also managed to install the self-hosted version on a server. Though I'm unclear, when content is exported from legacy, does it 'recreate' the existing structure (and data) of the legacy site to the self-hosted version. Otherwise, for the self-hosting version, would I need to build the site from scratch, i.e. fields, types, forms, workflows, actions, members etc? Essentially, I'm trying to understand the complexity of moving from your hosted legacy to self-hosted, and how much work (and technical knowledge) would be needed. To be honest, when I check the sandbox and self-hosted version, it's appears rather daunting as it involves assembling many elements to have a working site that looks like a legacy version. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Thanks for writing in. Yes, we are working on tooling that will automate the process of both creating the structure and importing content from Legacy. Members will likely need to be re-invited, though we may be able to at least automate some of this process as well. You will need some technical knowledge to self-host Legacy, to be sure, though we will try to make it as easy as possible by providing easy deployment options for common services. But the migration process should be relatively turnkey, at most involving downloading and uploading files. |
Beta Was this translation helpful? Give feedback.
Thanks for writing in. Yes, we are working on tooling that will automate the process of both creating the structure and importing content from Legacy. Members will likely need to be re-invited, though we may be able to at least automate some of this process as well. You will need some technical knowledge to self-host Legacy, to be sure, though we will try to make it as easy as possible by providing easy deployment options for common services. But the migration process should be relatively turnkey, at most involving downloading and uploading files.