Migrating only data from v2.3.5 to v3.1

I have set up a new indico v3.1 on Ubuntu/nginx server, which is working fine. I am now told that there is a production server from which I need to move the all old event data. I checked the old server. It is a Centos 7/Apachi with posgres 9.x. As you can see my situation is a bit peculiar and is not covered on the migration/installation guide.
My plan:

  1. move the /opt/indico/archives/event directory to the new server
  2. take dump of the old database and restore it to the new server.
  3. Maybe the next step is to run the indico db upgrade?

Any idea, if this would work?
Thank you in advance for any suggestions,

This is in fact exactly what we suggest in the 2.x to 3.x upgrade guide…


1 Like

Thank you for the quick reply. Yes, I saw that guide. My problem is that I have already made a lot of changes to my new deployment and do not want to run the indico setup wizard again. My question here is by only dropping the new database and restoring from the old DB then moving the event folder work?
I just want to know if there is any proven way, I will have to try it anyway.


If you don’t use the wizard you need to make sure the required directories exist, and you probably want to also run indico setup create-symlinks and indico setup create-logging-config (this is usualyl done by the setup wizard).

You can check what it does near the bottom of this file: