We are working with a migration expert and have found a snag. Migrations and infopath xml’s not migrating properly when the xml’s are in one library and the associated form template (.xsn) is in another. This allows us to have version on the .xsn itself. The issue is that the data connections for the forms are ‘hard-coded’ not in a data connection library. Thus, when we open the InfoPath forms in 2010, they link back to a place on the old server.
Ever heard of a tool or SQL option for changing server reference inside versioned infopath XSNs? i.e. Our .XMLs on our new server after migrating will only point to the latest .XSN.