So in answer to my own question. If the doc type has standard properties it works. If not you get ysod

Could not find a map for a property editor with a legacy id of 82cc7433-acb3-4a7a-8ab3-a02ec6dd181e. Consider using the new business logic APIs instead of the old obsoleted ones

Ismail

the internal ID for datatypes has changed from a GUID to a string,

if we had a map then it would be possible, just by replacing the GUIDs with the new IDs - then the import would work.

might knock up a migration mapper - would use something like this

<migrationMapper>
    <DataType Name="Approved Color" v6="f8d60f68-ec59-4974-b43b-c46eb5677985" v7="Umbraco.ColorPickerAlias" DatabaseType="Nvarchar"/>
    <DataType Name="Checkbox list" v6="b4471851-82b6-4c75-afa4-39fa9c6a75e9" v7="Umbraco.CheckBoxList" DatabaseType="Nvarchar" />
    ...
</migrationMapper>

Hi,

update - i don't know why i just did this ? - because it replicates standard functionality - i suppose what it does let you do is extend it - if we now what the non standard doctypes mapto between versions you can use this to map from one to another - but without that it's me not reading properly headdesk

uSync.MigrationEdition has been born (in the last 1hour - so might be buggy)

http://our.umbraco.org/projects/developer-tools/usyncmigrationedtion

but it is a command line tool - point it at the folder with your v6 data types and it will write out v7 ones with the id's mapped.

It works on some simple ".udt" (standard exports) and ".config" (usync files - not that usync works on v7.0.2 at the moment) datatype exports.

try - see it work (or fail).

i don't know why i just did this ? - because it replicates standard functionality - i suppose what it does let you do is extend it - if we now what the non standard doctypes mapto between versions you can use this to map from one to another - but without that it's me not reading properly headdesk .

is working on a reply...