Content
View differences
Updated by Max Mutzge over 5 years ago
As a potential OpenProject customer
I want to use an (as far as possible) automated way to import my >10,000 Confluence pages to OpenProject wiki
so that I don't have to do this by hand.
### Current situation (OpenProject's view)
"The challenge is that we currently can read wiki pages via the API but not create or update them \[1\]. This would first need to be implemented to have a technical foundation to build on top of. Evaluating this topic for a smaller number of pages it became quite apparent that there are a lot of functionalities that do not have a corresponding functionality in the OpenProject wiki pages. So in any event there would be a lot of fine-tuning to be done for it to look and work properly.
Therefore, we decided against an automated approach (which would require the implementation of additional API endpoints and a script or some import functionality and then would still require a lot of manual fine-tuning).
Instead, we discussed the following: Since OpenProject wiki pages support markdown, it is relatively straight-forward to copy and paste a markdown page into the markdown OpenProject page.
My understanding is that Confluence does not support a Markdown export out of the box but there are Markdown exporters available on the Atlassian marketplace (e.g. \[2\]). You could use that to export a Confluence page and then import it (manually) to an OpenProject wiki page (via copy & paste in the Markdown view).
You would still need to add attachments (images, etc.) afterwards but the basic formatting (headings, lists, styling, etc.) should be close to the original Confluence page.
For most use cases (unless they have thousands of pages) this should be a somewhat practical approach."
I want to use an (as far as possible) automated way to import my >10,000 Confluence pages to OpenProject wiki
so that I don't have to do this by hand.
### Current situation (OpenProject's view)
"The challenge is that we currently can read wiki pages via the API but not create or update them \[1\]. This would first need to be implemented to have a technical foundation to build on top of. Evaluating this topic for a smaller number of pages it became quite apparent that there are a lot of functionalities that do not have a corresponding functionality in the OpenProject wiki pages. So in any event there would be a lot of fine-tuning to be done for it to look and work properly.
Therefore, we decided against an automated approach (which would require the implementation of additional API endpoints and a script or some import functionality and then would still require a lot of manual fine-tuning).
Instead, we discussed the following: Since OpenProject wiki pages support markdown, it is relatively straight-forward to copy and paste a markdown page into the markdown OpenProject page.
My understanding is that Confluence does not support a Markdown export out of the box but there are Markdown exporters available on the Atlassian marketplace (e.g. \[2\]). You could use that to export a Confluence page and then import it (manually) to an OpenProject wiki page (via copy & paste in the Markdown view).
You would still need to add attachments (images, etc.) afterwards but the basic formatting (headings, lists, styling, etc.) should be close to the original Confluence page.
For most use cases (unless they have thousands of pages) this should be a somewhat practical approach."