Do's, Don'ts and lessons learned with Confluence?

We are transitioning from a number of various knowledge bases to Confluence. Has anyone done this? Do you have any recommendations for do's, don'ts and lessons learned? 

2 answers

1 accepted

This widget could not be displayed.

Hi Jennifer,

Yes, I've done this.  There are lots of lessons learned and gotchas (too many to put here), but they largely boiled down to things like:

  • If you're a technical person, get a content person in before you move anything.  They'll spot issues you won't.
  • If you're a content person, get a technical person in before you move anything.  They'll spot issues you won't.
  • Plan your space structure, if you can, because you move things in.  It's pretty annoying having a structure set up and working only to find it doesn't scale to accommodate what you're transferring and you have to move things around again.
  • Automate as much as you can (some wikis have export tools and Confluence has built in Word import functionality which is very good).
  • Bring as much metadata over as possible, especially who last edited [whatever you're importing] and when.
  • If multiple people are bringing stuff in, agree on common naming conventions, page structure, and labels.
  • On the subject of labels, use them to say where a Confluence page came from, e.g. wiki name, shared drive, SharePoint, or wherever.
  • Consider adding smaller documents as attachments rather than extracting the contents.  This will greatly reduce your import time and allow you to turn off [old system] much quicker.  You can then turn the attachments into actually pages over time if you want to.
  • Manually porting things over can be boring and a lot of people won't do it right because of this.  Only get people who really enjoy doing this sort of thing to copy things over.
  • Keep your old repositories for at least 6 months, just in case.  Transfer them to a portable hard drive that an admin locks in a secure cupboard if necessary, but don't "move and delete" because you'll regret it (even if no-one needs the back up you'll always be fretting that someone will need the back up).  If after 6 months (or whatever time frame you're comfortable with) you haven't needed the back-up, get rid of it.

There are 100 little things as well, most of which will be context dependent.  If you get stuck ask a question here; if you get really stuck try  They're very, very good at answering, fixing, helping and generally supporting smile

This widget could not be displayed.

Hi Rob,

Thank you so much! It sounds like I am on the right track!!! I just needed to hear that the items I was concerned about were legitimate which it sounds like they are! Now I can make the business case to address them!



Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published Tuesday in Confluence

Add-on evaluation with confluence templates

Atlassian market place contains number of Apps/Addons which improves the capability of out of the box Atlassian products. It is good to follow a plugin evaluation process before install add-ons. So t...

75 views 9 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you