The page id is a unique identifier in the database, for the computers, not for us humans. When you're importing, there's no way to keep the old id because it does not matter to us, and there's every chance the target system may have already used it.
Easy way to say 'no it is impossible'.
Why could not be done by matching pageName with old- and new- pageID in the database?
content table in the confluence database but has no pageID value for each page contenttype what I found this very very bad!
This is a big problem for all migration tasks. Confluence guys must find a solution, whilst they add pageID - pageName matching in database, in my opinion.
Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond. A long time favorite, Team Cale...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events