Migration from Blocs 2.6.1 to 3.5.4 seems to not work

I have a project website created with Blocs 2.6.1. Blocs offers me to migrate the project, but even after saving it, when I open it again I keep having the same message with the proposition to migrate the project that is still considered as a Blocs 2.6.1 project.
How can I manage a proper migration?


That doesn’t sound right. I would send in a support ticket along with the project file to have it checked out. As a general practice I always rename newly saved project files in cases like this where they are migrated and keep it separate from the old version. If you haven’t done that already it might be worth trying.

1 Like

Good idea. I’ll try this.