Version 1 of the Data Migration Framework (DMF) for Microsoft Dynamics AX 2012 was supplied by Microsoft in the USR Layer as an optional tool available through its InformationSource portal.
https://informationsource.dynamics.com/RFPServicesOnline/RFPSLHost.aspx#/View/ToolsDownload.xaml
The new version of this tool, now renamed as the Data Import Export Framework (DIAF), is supplied in the FPK layer.
During trials that we did with version 1 of the DMF tool for a customer, we concluded that leaving the tool in the USR Layer was not really an option for us so so we elevated it to the VAR layer and left it in it’s own model. But we found that new objects created for new MDF entities were created in the AOT in the layer and model where the DMF objects reside, regardless of which model you are currently developing in. Although this is a bit odd, it is not an issue in itself unless you want to keep modifications in a different model.
When an object has been created and moved to the model required and then deployed if, for any reason in the future, the original entity is regenerated you must remember to move the AOT objects to the correct model again otherwise you will run into conflicts when trying to re-deploy the objects.
I will be testing what happens with version 2 of the tool to see what happens with this version of the tool as I would assume that it will not create new objects in the FPK layer….but you never know. If anyone gets around to looking at this before us, we would love to hear about it.