How to Upgade !

It' not to find in comfort update!

That's indented. Currently an 100% working upgrade from 2.X to 3.X is not possible.

Will it be possible in the future!

Yes.

Thank you, Jelo, for providing this answer. I'm working on this problem right now.

Hi olle,
Can you already estimate when this will go live?
That would be great, thanks!

Hi,

As far as I can tell, we've removed the biggest problems with theme configuration etc, BUT it's still "do it on your own risk". Neither plugins or templates are compatible from 2 to 3. We still haven't decided a date for comfort update upgrade. It might take a couple of weeks, still.

I would always recommend a parallel installation, when it comes to a major release. And then move to the new installation gradually.

Yes, this might be a bit of work if you have a lot of users/surveys.
But there are some important advantages:
- Current surveys will definitely not break and you can run them until the end with the old version.
- New surveys can be built in the new version, but if something goes wrong (e.g. bug, feature not working, etc.) you can export the survey and import it on the old platform as a fall back.
- You have a clean install and don't carry old weight with you.

The space a new installation requires is minor, I think. But you can reduce the risk of any problem quite a bit with this approach. And it doesn't cost you more (ok, you might use more 2x as much updates from your comfort update, but usually the number of available updates in the package allows you to update 2 installations without running into problems).

Is there now an upgrade path from latest 2.5.x build to 3.x, using Comfort Update?

My 2.72 offers me an upgrade to 3.x via comfort Update, so I guess there is. Haven't tested it though, because I always install mayor new releases in parallel, as described above.

So I tried this on a sandbox copy of my 2.5 site, and the upgrade failed with the message:

You have an error inside your survey instance. See:

With nothing after the word "See", and upgrade didn't complete (but it didn't break LS either).

What is the exact version of your 2.5 site?

I guess the safest way is to upgrade to the latest version of 2.x branch, which is 2.72, and then go from there. But as I said, I haven't used it yet, so I don't know if/how it works.