Hey!
I know there has been quite a lot challenges after the major update to V2 world. I’m in that boat and we have had zero success while trying to move our self hosted design files to the new era.
I’ve given up already and I’m ready to shovel the design to the new version “by hand”… But, just wanted to ask about one detail (the very last straw). While trying to copy (as in just copy-paste) anything from “old” project/team to new one, there is this mystery error “Feature ‘components/v2’ is not supported.” and the it fails. Could this mean that there is something wrong in our own setup? Or is it just that the migration wasn’t able to do its’ magic to the V1.x files (I’m not running the environment–just trying to do the designing– so I don’t have any logs etc about the migration script)?
Hello,
The migration migrates entire teams and assigns the ‘components/v2’ feature to all files and the team. If you encounter this error, it means there is a feature mismatch between the files being copied. When transitioning from the latest version 1.x to 2.0, there is a script that automatically migrates all teams and files to the new format. Once this script is executed, all your projects should be in the new format. Migration via copy-paste is not recommended, especially if you extensively use components, as that’s where the main changes reside.
Have you been able to execute the migration? Have there been any issues in carrying out that migration?
For more details on this topic, refer to the documentation here: 1. Self-hosting Guide
Hey!
Yes, we’ve tried the automatic and manual migration scripts, but there were some mystic errors that were not traceable, so we gave up with that (don’t have the logs since it was done by other people). I haven’t created any extensive set of components, at least from my PoV, so I don’t think that would not be the case. That said, the problem might be more exotic and maybe related to the hosting env.
Funny thing though, that exporting “old” file and importing it to new team (which is set up for the v2 things) works in some cases. If the importable file is too large it fails, but on smaller scale it works. Also if there are any components in the old file that’s imported, they are detached in the process. So it seems that importing does some on-the-fly-migration that the copy-paste can’t do (while trying to copy-paste the same content from old file to new file) 
But yeah, I think I’ll survive with the shoveling – just wanted to double check if there were anything else that we could try to smoothen this update.
