Exporting and importing a form is pretty straightforward unless you are involving lookup fields that need to be changed to a new server.

In my case I was going from a test environment that we used for proof of concept to the client's server. The form I have involves over 50 lookup fields that are hidden until filled in.  The new environment is also the client's test server so presumably we will need to follow these same instructions when moving into production.  

I didn't want to try to redo alllll of these lookup fields. After a little thought I realized the export you do from forms server A to forms server B is an xml file which can be edited!

I used my favorite handy dandy editor (Notepad++) to search for my SQL server and found it here:

<lookuprule>
  <externaldatabase>
     <server>testsystem..internal.corp</server>
     <database>lfformstemp</database>
     <tableName>Manifest_Data</tableName>
     <user>domain/MyDBUsername</user>
  </externaldatabase>
(etc)

So what this allowed me to do was to do a search/replace on >testsystem.internal.corp(so it found every instance of the test db I had) and replace it with >customerstaging.internal.corp.

I also had to replace the database name as well. Presumably you can also use this if the tablename is different. 

So instead of spending hours redoing all of my lookups, I spent a few minutes using the notepad++ replace function to swap out all of the database info.

Of course before doing this you need to add the new database to your forms server. It will only work if there is a database on your system that includes the same sqlserver/database/user/table that you have inserted into your xml file before you import it.