Tiago,

<< PDX. Had 56 files 31.336.448 bytes BDEtrans took 14 seconds to migrate to
DBI4 and generated 52 files 46.053.232 bytes Same source took 3:43 minutes
to migrate to EDB and generated 65 files 62.516.888 bytes
DBI4: 52 files 46.053.232 bytes took 3:20 minutes to migrate to EDB and
generated 65 files 62.683.760 bytes

Conclusions:
May be client/server, version misc or BDE configuration on that machine,
but yesterday after 2 hours bde migration was still running (not hanged) !!
>>

No, more than likely it is just the differences in the catalog updates,
flushing, etc. that takes place with the EDB migrations.  This is especially
true if you have a lot of indexes defined for the tables being migrated.
We're looking into providing DDL transactions that will help eliminate the
flushing and, subsequent, slowdown from it.

--
Tim Young
Elevate Software
www.elevatesoft.com