I think I have to make a nuance on the documentation here. As of Uniface 10, we make a distinction between straightforward import and migration, where migration involves import following by a conversion (map data from old to new). As of Uniface 10, export files include a file version. This is a different version then the Uniface version. As long as the file version is compatible with the Uniface version you are trying to import into, import is possible and no data migration is required (and not performed). If a migration routine exists for the file version, it will be imported and converted (and only the imported data will be migrated). And then obviously, if no migration routine exists (the file version is really too old), the import will be rejected making sure that your repository does not get corrupted. Currently, incompatible export files cannot be detected good enough, which will corrupt the repository. We will keep on providing migration facilities for file versions that we think are appropriate. Not much changes here. About Uniface 10.1.01, being an early adapter release; it does not provide any migration. Simply, because we do not provide all editors just yet. Hope this helps clarifying things a bit - Gerton

Got it We will wait and see what will lie under the christmas tree :-)