Confluence Migration Assistant finishes with 100% but fails to migrate some pages
Asked by Michal Turecki:

We are migrating self-hosted confluence to the cloud after successful JIRA migration and all spaces but one, largest (149 MB of media, 363 pages, 0 blogs, 245 drafts) migrated successfully.

The failing space is only partially copied last migrated page is from 2016) yet Content Tools -\> Trash shows some of the recently created attachments and pages.

The atlassian-confluence.log during the migration process shows no errors and the following information:

2018-11-12 14:48:06,948 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Backward compatibility for export: Checking...  
2018-11-12 14:48:06,955 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7202: "Remove the legacy Plugin License Storage plugin from the user installed plugins" - Ok  
2018-11-12 14:48:06,957 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7201: "Upgrade to build number: 7201" - Ok  
2018-11-12 14:48:06,957 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7110: "Reindex all blogs." - Ok  
2018-11-12 14:48:06,958 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7109: "Drop and update some low performance indexes on EVENTS table for Synchrony" - Ok  
2018-11-12 14:48:06,958 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7108: "Update index sp_comp_idx when the definition is not correct" - Ok  
2018-11-12 14:48:06,958 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7106: "Drop the hibernate 2 constraints in preparation for them to be re-created in the hibernate 5 n  
aming style" - Ok  
2018-11-12 14:48:06,965 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7105: "Drop or update some low performance indexes on CONTENT" - Ok  
2018-11-12 14:48:06,965 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7104: "Set the mime type for csv files to text/csv" - Ok  
2018-11-12 14:48:06,966 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 7101: "Migrate over Documentation theme settings to Custom Page Settings in the default theme" - Ok  
2018-11-12 14:48:06,994 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6439: "Reindexes all PersonalInformation objects, creating them for any users that do not have one."  
- Ok  
2018-11-12 14:48:06,994 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6430: "Upgrade to build number: 6430" - Ok  
2018-11-12 14:48:07,011 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6424: "Adds missing multi-column unique constraints to the Crowd database tables" - Ok  
2018-11-12 14:48:07,026 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6423: "Cleaning data that violates constraints we want to add in the next migration task" - Ok  
2018-11-12 14:48:07,026 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6422: "Upgrade to build number: 6422" - Ok  
2018-11-12 14:48:07,038 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6412: "Delete all FileStore IDs" - Ok  
2018-11-12 14:48:07,038 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6406: "Reindex all spaces" - Ok  
2018-11-12 14:48:07,039 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6403: "Upgrade to build number: 6403" - Ok  
2018-11-12 14:48:07,039 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok  
2018-11-12 14:48:07,040 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6193: "Rebuild the Confluence favourites index" - Ok  
2018-11-12 14:48:07,040 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6189: "Upgrade to build number: 6189" - Ok  
2018-11-12 14:48:07,054 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6180: "Adds a multi-column index to content table that speeds up many common queries." - Ok  
2018-11-12 14:48:07,055 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6175: "Upgrade to build number: 6175" - Ok  
2018-11-12 14:48:07,055 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6169: "Upgrade to build number: 6169" - Ok  
2018-11-12 14:48:07,055 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6161: "Upgrade to build number: 6161" - Ok  
2018-11-12 14:48:07,056 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6139: "Upgrade to build number: 6139" - Ok  
2018-11-12 14:48:07,061 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6122: "Remove the legacy Confluence Thread Dump Plugin from the user installed plugins" - Ok  
2018-11-12 14:48:07,062 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6116: "Upgrade to build number: 6116" - Ok  
2018-11-12 14:48:07,073 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 6112: "Finds all attachments that are missing a content_status and marks them as current" - Ok  
2018-11-12 14:48:07,073 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5914: "Upgrade the customizations from the ondemand doctheme to the format expected by the standard c  
onfluence doctheme" - Ok  
2018-11-12 14:48:07,089 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5702: "Enables membership aggregation across directories" - Ok  
2018-11-12 14:48:07,090 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5613: "Upgrade to build number: 5613" - Ok  
2018-11-12 14:48:07,094 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5612: "Upgrade to build number: 5612" - Ok  
2018-11-12 14:48:07,097 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5604: "Upgrade to build number: 5604" - Ok  
2018-11-12 14:48:07,097 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5603: "Upgrade to build number: 5603" - Ok  
2018-11-12 14:48:07,097 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5602: "Upgrade to build number: 5602" - Ok  
2018-11-12 14:48:07,098 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 5601: "Upgrade to build number: 5601" - Ok  
2018-11-12 14:48:07,103 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 4984: "Upgrade to build number: 4984" - Ok  
2018-11-12 14:48:07,103 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 4950: "Upgrade to build number: 4950" - Ok  
2018-11-12 14:48:07,104 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 4526: "Remove the legacy remotable apps plugin from the user installed plugins" - Ok  
2018-11-12 14:48:07,105 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Build number 4517: "Migrate all Page Templates using a storage format round-trip conversion" - Not Ok  
2018-11-12 14:48:07,105 INFO \[pool-18-thread-1\] \[atlassian.confluence.upgrade.AbstractUpgradeManager\] getExportBuildNumber Backward compatibility for export: "Migrate all Page Templates using a storage format round-trip conversion" preve  
nts compatibility before 4517  

There are although some errors when viewing certain pages which can indicate potential issues causing the migration to fail:

2018-11-12 15:00:43,367 ERROR \[http-nio-8081-exec-11\] \[core.persistence.hibernate.HibernateObjectDao\] findSingleObject Uh oh - found more than one object when single object requested: \[Attachment: user-avatar v.2 (17498338) tmhunduru, At  
tachment: user-avatar v.1 (17498339) tmhunduru\]  
-- referer: <https://confluence.company.com/> \| url: /rest/dashboardmacros/1.0/updates \| traceId: 024c2eb575c00324 \| userName: mturecki  
2018-11-12 15:01:09,151 WARN \[ContentViewedListener:thread-1\] \[confluence.impl.hibernate.ConfluenceHibernateTransactionManager\] doRollback Performing rollback. Transactions:  
-\>\[PluginReadWriteTx\]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT (Session #721107627)  
-- url: /display/DEV/Products \| page: 1081372 \| traceId: cb2b0773d24172ae \| userName: mturecki \| referer: <https://confluence.company.com/display/DEV/Home> \| action: viewpage  
2018-11-12 15:01:11,056 WARN \[http-nio-8081-exec-4\] \[internal.integration.jira.DefaultJiraService\] handle Could not parse JIRA server's information: Unexpected character ('\<' (code 60)): expected a valid value (number, String, array, obj  
ect, 'true', 'false' or 'null')  
at \[Source: java.io.ByteArrayInputStream@2a646504; line: 11, column: 2\]  
-- referer: <https://confluence.company.com/display/DEV/Home?src=spacemenu> \| url: /rest/highlighting/1.0/panel-items \| traceId: fe63388ac5ee17fb \| userName: mturecki  
2018-11-12 15:01:11,760 WARN \[http-nio-8081-exec-5\] \[internal.integration.jira.DefaultJiraService\] handle Could not parse JIRA server's information: Unexpected character ('\<' (code 60)): expected a valid value (number, String, array, obj  
ect, 'true', 'false' or 'null')  

We are using Confluence version 6.3.1 which is greater than minimum required by Migration Assistant.  

How to enable more verbose migration logging?


Answers:
author: Ramona Scripcaru
body: Hey Michal,

The logs should provide us with a caused by when the migration plan was completed.

I'm checking how to increase the logs for this exact plugin, meanwhile, would it be OK if I also have a look at the complete logs? I've opened a support case and you should have received an email, can you please attach the full logs to that case?

Thank you,

Ramona

comments: author: Michal Turecki
body: Hi Ramona,

Thank you for looking into the issue. The issue sorted itself out after migrating to the latest version of Confluence and adjustments to permissions - several pages were belonging to groups which were not migrated as Migration Assistant does not move any permissions.

Please close the issue - we will be purchasing cloud contract this week.


author: Ramona Scripcaru
body: Hey Michal,

That is good news! Happy to hear that this issue got resolved after the server upgrade. Sure, I'll close the case now, but if you encounter any issues, just let us know.

(i)

After the migration, you might notice pages associated with an *Unknown user(userkey)* , if this is the case then the user is affected by a bug in our product, and I can apply a workaround for you. The bug report is: <https://jira.atlassian.com/browse/CONFCLOUD-64436>

Thanks,

Ramona


author: Ramona Scripcaru
body: Hi Michal,

I just wanted to confirm the details about logging enabling for this plugin, and I thought to be useful to note here the reference. :)

If a more detailed logging is required for Confluence Migration Assistant, a new logging configuration record should be added to Confluence Server logging settings with key **com.atlassian.migration** and level **INFO** / **DEBUG** . This page contains the details of how to do that <https://confluence.atlassian.com/doc/configuring-logging-181535215.html>

Cheers,

Ramona


Tags: migration

confluence-server

server