Error doing followup migration - We can't communicate with your server

[Mike Farver]

We completed a migration from server 6.13 to Confluence Cloud, but some users created sites after the sites were originally selected.  We had been on the free version of Confluence Cloud but switched to a paid for version after the migration.

This morning, I get an error that the migration assistant can't communicate with our server, so while it shows me my local instance, it never lets me save the migration or complete it.

As we're almost migrated from 6.13, I'd rather not upgrade to 6.14 so I can manually export the 2 sites that need to be migrated.  It worked on Friday the 14th, but today it's not.  I'm not sure if the migration assistant is having issues or if something else has changed.

[Fabian Lim · Accepted solution]

Hi @Mike Farver

I recommend you open a ticket with atlassian support directly for a faster response and analysis.

Regards

[Mike Farver]

Our self-hosted server is on the free license and so support is not included, only the forums.  As I'm migrating to a paid version that comes with support, I'm in the gray area of which license is this covered under.

[Radek Dostál]

Another way to look at it - you're paying for support including migration, for an instance, and you want to import data to that instance. Whether the data comes from another Confluence or not is irrelevant - coincidentally, it's better because Atlassian is familiar with it. In my experience Atlassian are pretty friendly and generally try to help - unless you ask them for something totally out of scope. Confluence Server to Confluence Cloud doesn't sound like a bad pitch.

[Mike Farver]

I just opened a case with support, so we'll see if the issue gets resolved.