It is not a good idea to import DDD because you need to get it exactly right otherwise you can break your system. Even if you imported DDD it would not correctly create the inferred model.
Creating the inferred model through CSV you would need to make sure you followed all the relationships and sorted out the linking up which would be really painful in CSV import. The import is not really designed for building lots of different relationships.
The only practical way is using consolidation.
Are you saying your DEV and Test systems can't talk to each other over the network? If so, what about setting up a consolidation appliance on the same network as your test system and then restoring the DEV consolidator's backup to the Test consolidator?
Thanks for the reply,
So I have a dev scanner in one domain that can't scan devices in another domain because of policy. In Production I don't have the same issue since it can scan everywhere. Unfortunately my F5 devices are in a domain my Dev scanner can't reach out to. I am looking for a way to model an application in Dev that would have those devices available. I also do not have enough space in dev to do a restore...
Thanks Andrew - I thought it might get tricky...
If it is question of just testing in DEV environment with minimal number of devices then you could use record data of those F5 devices. However make a note that record data will give you information about device which is recorded, i.e. If some changes happens on F5 device then your DEV scan will not reflect them. So this is just a temporary workaround you can have.
As Andrew said practical way is to use Consolidator.