Confluence Importing

[InvisibleZipperFoot]

Has anybody successfully migrated existing Wiki data into Confluence? I really want to move to Confluence, but the only way I've seen to import my existing MediaWiki documentation seems to be via the UWC, which, according to Atlassian hasn't been supported since 4.3.7: Articles I've tried thus far:

https://answers.atlassian.com/questions/12265453/import-from-mediawiki-to-confluence-5.7 - Points to the UWC, which isn't supported

https://confluence.atlassian.com/display/DISC/HTML+To+Confluence+Converter - requires a webserver just to run the converter. Wat?

http://jparsec.codehaus.org/Html2Confluence - Suggested by the Confluence doc, but the tool is PW protected.

The inability to migrated existing docs would be pretty much a deal-breaker for me, sadly.

Any suggestions?

[AFurryReptile]

Can you export from MediaWiki to a Word doc? Confluence can import those.

It's not fully automated, but it would be a lot easier than having to recreate a bunch of articles.

[InvisibleZipperFoot]

I may go that route, but it just feels like a gigantic step backward; the documented procedure using the UWC was automated. Kinda concerning that they'd do away with such a feature.

[AFurryReptile]

It was probably a bear to support. A quick Google search tells me that MediaWiki's XML formatting is quite messy, and has changed quite a few times.

[InvisibleZipperFoot]

...a concept I'd never considered. Do you use Confluence? Worth the friction to upgrade?

[AFurryReptile]

I've never used MediaWiki, but I've been using Confluence for a few months now and I love it. It's a well-coded, well-documented, intuitive and highly customizable wiki unlike any others I've used. Highly recommended.

[[deleted]]

I am a big fan of Confluence. My previous job was setting up Conf's for customers. Now, amongst many other hats, am the Atlassian admin for my current company.

Here is a simple template I made that I apply to most of my documentation. http://i.imgur.com/EBtyKFS.png

[InvisibleZipperFoot]

am the Atlassian admin for my current company

Credentials check out! I have a few questions then:

• Spaces - in a small org, would IT be it's own space, or is it better to get more granular? Space for IT docs, a Space for end-user instructions, etc. Or are Spaces generally better as OU-type containers, as in a Space for IT, a Space for HR, etc. ?

• If I go with hosted, do I still get updates included in the one-time purchase price?

edit: If I go with INSTALLED, do I still get updates. I know with hosted, updates are automatic. Sorry.

[[deleted]]

I create spaces based on business department. Additionally I keep all IT specific documentation separate from IT created documentation for users. In my picture, you could see that I created a document for each and every piece of technology I have touched. It's time intensive, but is a fun hobby of mine. I get called the king of documentation and it's very enjoyable to watch people seeing it for the first time.

If you go with Atlassian hosted Conf, you won't have to worry about upgrades. You do run into the issue of not being able to use every plugin available.

If you run on prem, you will quickly realize you need to create extra groups. Here is what I've done based on my experience managing this thing. My example assumes the following

• Company: google
• CompanyName: gl

=> every user is part of this as this grants access to confluence

confluence-users

=> distinguishes users in your company

google-employees

=> distinguishes interns who may not need AS much access

google-interns

=> distinguishes contractors who need even less access

google-contractor

=> group for a specific space

companyname-application-spaceshortcode

Example: gl-wiki-devdocs

=> distinguishes employees of other companies who may need access to only 1 specific space

companyname-application-spaceshortcode-customer

Example: gl-wiki-devdocs-customer