If all we're talking about is keeping schema in sync, it's simple enough -

I run sp__revtable on the tables on my Sybase server databases that have not yet been full ported to SQL Server. If I care only about schema, I can simply drop and remake

the tables and indices with the output.

As always "it depends". On an established system being rebuilt elsewhere, it's far more important that the new one be like the real thing, as opposed to what the source code thinks it should be. Of course, the source code should reflect this state, so if it doesn't due to neglect over the years, I can use this same method to generate a source list for tables and SCCS those to keep a history.

Far more critical and as yet unaddressed is doing the same for the data. HitSW DBMoto can do it if you don't mind pushing all the data every time - but that stinks for large dbs that usually change less than 1% of their data per day.