Description
In v2, a localized entry has the same ID as the default language. In v3, each entry has a unique ID. Great.
When migrating a multisite, all the localized entries get their own IDs. Great.
The entry with the default language and the localized entry is connected with origin. Great.
BUT: If you have an entry with a reference to another entry, let's say by linking to it using the fieldtype entries, and your entry has 3 languages, things start to get messy... In v2, the reference would be identical for all 3 languages (the link to the entry you're targeting, is the same for all 3 languages, using the same ID) Meaning, you wouldn't have to set localizable: true on fieldtypes such as entries.
In v3, however, you will need to open up the default language, do your linking to other entries, open up the second language, do another round of linking, and so on. For a migrated site with hundreds of pages, featuring 3 languages, with thousands of references to other pages, this is quite overwhelming..
Could the migrator handle this also? Please?