This page last changed on Nov 16, 2005 by jnolen.
This document will assist you in migrating data from other wikis such as JSPWiki to a Confluence installation. If you need something clarified in this document, please feel free to send us an email at confluence-support@atlassian.com
Migrating Data from JSPWiki
To import data from a JSPWiki site you should first run a standalone application called jspwiki-exporter to export the JSPWiki site to a Confluence zip file. Then you can import the exported zip file on any Confluence installation from Administration > Backup & Restore > Restore. You can choose to build the exporter yourself or simply download it.
If you would like to build the exporter from source, you will find instructions to do so here.
Download JSPWiki exporter
- Download the pre-built exporter here (jspwiki-exporter-1.4.4.zip or jspwiki-exporter-1.4.4.tar.gz)
- Extract the exporter into a new directory (we'll call this the working directory for this guide)
 | Note to existing Confluence 1.3.x users
If you would like to create an export for Confluence 1.3.x, the latest exporters for this version are jspwiki-exporter-1.3.6b.zip or jspwiki-exporter-1.3.6b.tar.gz. You can use these same set of instructions for these exporters (just remember to use the correct version number). |
Download the confluence-1.4.4.jar
- Download this jar from here and copy over to the working directory.
 | Note to existing Confluence 1.3.x users
If you would like to create an export for Confluence 1.3.x, you will need to copy the confluence-1.3.6.jar instead. Available here |
Copy confluence jars into working directory
- This step assumes that you have already downloaded either the standalone or WAR version of Confluence. If you haven't done so already, you can do so from here.
- Extract the zip and copy all the jars from your confluence WEB-INF/lib directory into the working directory.
Running the jspwiki-exporter
- Now open up a command/console window and switch to the working directory. To Run the exporter enter:
java -jar jspwiki-exporter-1.4.4.jar <1st parameter> <2nd parameter> <3rd parameter>
where:
Parameter |
Explanation |
Example |
1st parameter |
Points to the location of the jspwiki.properties file |
d:\java\tomcat\webapps\JSPWiki\WEB-INF\jspwiki.properties |
2nd parameter |
name of the space (make sure this doesn't already exist and that it is a valid Confluence space name. If in doubt, try testing it by creating a space with that name first.) |
fromjspwiki |
3rd parameter |
name of a user (make sure this user exists) |
john |
IMPORTANT: If camel case linking was enabled and used in your JSPWiki instance, please ensure that you have camel case linking switched on in Confluence before you import. This setting can be found in the Adminstration > General Configuration section.
The export zip is called jspwikiexport_ddMMMyyyy_time.zip and can be found in working directory/exports/ folder. Now that you have created a confluence export file from you jspwiki data, you can begin to import this data into Confluence. To do so, go to the Confluence Backup and Restore page, and simply browse for this zip file and click restore.
It appears jspwiki-exporter-0.6 needs the commons-logging.jar and commons-logging-api.jar. I think it will work fine without, but you won't be able to see any logging/progress messages, so knowing whether or not it works will be a bit tough After adding those JARs, the export ran fine, but I did get a bunch of warnings from Hibernate. I'm assuming those are safe to ignore, since I imported the resulting ZIP into Confluence without problem.

Posted by kadams54 at Sep 02, 2004 11:27
|
Howdy, Where can I find the latest source or an exporter that is configured to work with Version: 1.2.3 Build:#60 Oct 08, 2004? I tried to follow in the instructions as stated here. I received a ClassNotFoundException for bucket/config/wizard/SetupWizard. According the Manifest the exporter was expecting atlassian-bucket-0.6.7.jar not the one shipped with the current version of Confluence: atlassian-bucket-0.6.9.jar. I didn't want to just update that reference because that usually leads to a slippery slope. So I thought I can build from source and update the dependencies based on the shipped jar files. Which leads back to my question - Where can I find the latest source or an exporter that is configured to work with Version: 1.2.3 Build:#60 Oct 08, 2004?
Thanks...

Posted by melriffe at Nov 16, 2004 10:49
|
Discrepancies in the versions of the atlassian-bucket jar have been fixed in version 1.3.1a of the exporter. Thanks for pointing that out.

Posted by dave@atlassian.com at Jan 09, 2005 17:00
|
When creating your JSPWiki export - you should probably use the shortened space name you will want as the space name on the exporter command line option. For example, "DEV" for "Development". The import process will automatically assign the name as the key for the space, which cannot be changed later (AFAICT). The space name can easily be changed after it is imported.
This is particularly useful if you want a long name on your space and want to create cross-space links without entering the entire space name.

Posted by at Jan 10, 2005 14:07
|
I think a note of some sort should be added that says the exporter should be run on the machine/server that's hosing JSPWiki. I'm running Confluence and JSPWiki on separate machines and although I can access the JSPWiki server using <server-name>, the JSPWiki PageManager reads in the properties file which contains path information relative or absolute to the machine. Until I realized this, my exports were always empty. When I ran the exporter on the JSPWiki machine, my exports were 18MB (I know not too big, but not too small).
Thanks. – Mel Riffe

Posted by melriffe at Jan 13, 2005 16:01
|
the current version of the exporter doesn't work with the new Confluence since the classpath entry in the manifest doesn't reflect the new jar versions. I was able to run the exporter successfully using this unix command line:
$ java -cp `echo *.jar | tr " " :` com.atlassian.confluence.jspwiki.ConfluenceExporter yerargshere
I would suggest that a simple bat|sh would last much longer than the java -jar solutions...

Posted by g.rabellino@pro-netics.com at Jan 26, 2005 11:25
|
Don't know if this happened to others, but it might be worth mentioning that after importing from JSPWiki, you have to set the home page by hand in space administration, otherwise you'll get quite a few errors from the Dashboard.
Also, import could use some help about encoding. Our pages are in italian, and all non-ASCII characters are quite screwed up...

Posted by g.rabellino@pro-netics.com at Jan 26, 2005 19:11
|
Gianugo, thanks for your comment, that worked for me. But to get it running I still had to copy all the jars from confluence/commons as well into my working dir.

Posted by at Feb 01, 2005 13:57
|
"..migrating data from other wikis such as JSPWiki"
I have a PHPWiki that I'd like to import into my Confluence. Any pointers as to how I can do this would be appreciated 

Posted by eivindw at Apr 08, 2005 06:46
|
Hi there,
Trying to export JSPWiki content to Confluence using this tool. It appears the manifest inside the Jar is really, really, out of date (at least with respect to the version of Confluence we have recently purchased - 1.3.5 Build:#122 Mar 01, 2005. Any chance we could have a new one so that the Atlassian instructions above actually work?
Many thanks

Posted by rupertj at Apr 12, 2005 02:31
|
I've just tried to import a smallish JspWiki (80Mb) into an empty Confluence installation. The import had problems with attachments - pages are created within Confluence, but all attachments don't exist.
The reference from each page exists, but the file itself is missing from the "attachments" directory.
In the attachments area is the file's directory (into which verions are placed), but no version file exists (1, 2, etc.).
Upon further investigation, the archive created by the JspWiki exporter places the attachments in a numbering system very different to that in the end used by Confluence.
Any help would be appreciated. Cheers, Rob.

Posted by rob.whitney@adi-limited.com at May 18, 2005 22:07
|
Hi Rob,
Thanks for spotting this. This has been addressed in the latest exporter for version 1.4.1 of confluence.
Cheers,
Dave

Posted by dave@atlassian.com at Jun 13, 2005 23:58
|
|