You save with self-help evaluation tools, low cost, single package pricing, and our unique 180-day return policy.
At DBA we've been delivering manufacturing, MRP, and accounting solutions to thousands of businesses since 1992
Stay current with what's happening at DBA.
Because the two products are so different, the conversion process is essentially the same as converting to DBA Next-Generation from any outside accounting system.
In most cases you will be able to import the major DBA Classic master tables using our DBATRAN data transfer utility. The transfer does not include any transaction history or accounting information. In some cases this utility may not work and the import will have to be done using the standard Next-Gen import utilities.
Apart from the master tables import, the implementation process is exactly the same as it is for any company coming from another system and is covered by our Implementation Planner guide.
In regards to accounting, we recommend that you convert to the new standard chart of accounts that is supplied with Next-Gen. Within the new chart of accounts you can cross-reference your old accounts to help with the transition.
Once you are finished with the Setup phase, you should install our training company option and follow all the steps in the Rehearsal phase, using your own data. The Rehearsal phase is your "trial run" and should uncover any transition issues (such as forms and labels) or any "work arounds" that may be needed.
After the Rehearsal phase is completed you can schedule a system startup day when you will manually enter all your open orders, jobs, PO's, customer invoices, supplier invoices, and beginning GL account balances. As of startup day you will cease using Classic and operate entirely on DBA Next-Generation.
Do not attempt to run both systems in parallel, which would put a tremendous strain on your employees and customers. The far better approach is to be as thorough as possible during the Rehearsal phase so that all employees are fully trained and prepared such that there is no need to run in parallel.
Because no transactional history is brought over, you will want to keep DBA Classic on your server for some time for reference purposes.