To answer the other question regarding BinaryData20xx, DataRecord20xx, these refer to member IDs which will likely be different in the target application, so if you simply replicate those tables then it will create a massive integrity mess because the memberIDs in the [Member] table will be completely out of sync. (Not to mention this selective table copying is not supported)
If you can't copy the database because you want to preserve artifacts in the target application, then that could also mean that the data won't fit into the target application, because different artifacts may mean different metadata, rules, constraints etc.
Or is it only dashboard items or extender rules that you mostly want to preserve? In that case it would be easier to extract those dashboards/rules to an XML file, then do a database copy (and maybe shrink it while you are at it), and then re-load the artefacts over the top of it using XML.
If the target application is structurally different (i.e. metadata) then there is no way around the need to map/transform the data extracted from the source application ; but that isn't a OneStream-specific limitation.
