I would go for your first solution, transfering data from a database to another. And there are several reasons for that:

On a side note, even though I know that it may be late for you, I would say that changing data structures during development could be a symptom of a weak design. Perhaps spending more time at the design desk would save you all this ordeal.

 _  _ _  _  
(_|| | |(_|><
 _|   

In reply to Re: OT: Ways of managing changes to a database's structure during a project. by gmax
in thread OT: Ways of managing changes to a database's structure during a project. by EvdB

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":