No, I think the point of getting the 1st version out is to let people finally see the wayyyyy overdue product.  Mike is quite aware that until the full conversion routine is perfected that extremely few people will switch.  Even then, it is going to take quite a while before there is any significant switch in the customer base.

At this point we have no plans to convert to anything other than DBA. My company is currently using MS-Access, MySQL and DBA. We won't need another program to learn. We need our current apps. to get better ...!
 
Besides I used the current conversion program (DBA -> Ezijobz), It's  
not enough. I need all the data in DBA to get converted before we can use Ezijobz.  
 
We currently hold 10 life-time licenses
Estimated time to convert ---> @ 1-3-2005.

Hmmm, my information source paints a slighty different picture.  First, a new conversion program was setup on DBA's web site a few days ago.  Here are the details:
 
v2 (10/27/2003) Everything from v1 plus:  
 
Now supports DBA versions back to 2001.1.  
Now fully clears all Ezijobz data before starting  
Transfers DBA Shop Calendar, Work Centers, Machines and Tools  
Machines and Tools go into Ezijobz as Assets, with service Events created for each  
Ezijobz Resources and Descriptors are created for each WC, Machine and Tool  
v1 (10/13/2003) Initial posting of the conversion program:  
 
Supports DBA versions 2002.1 and higher  
Transfers company setup info from DBA (e.g. bank accounts, next SO#, etc.)  
Transfers GL Chart of Accounts, GL Mapping (defaults), accounting periods  
Transfers Customers, Salespeople, Territories, Lead Sources, and Tax Authorities  
Transfers Vendors  
Transfers Inventory, Locations, and Location UOH  
Stock items end up as Ezijobz Items, non-stock items as Ezijobz Descriptors  
 
BOM and Routings will be coming up on the next data transfer update, but I'm told there are still no plans to include transaction data.  I'll do some more checking on this though.