To ensure data integrity and the application functions as expected, we do not allow users to import their own data from another application. The backend database of this software has several dependent relationships. *

To maintain the proper data relationships, we have written some fairly complex data importation algorithms. These algorithms are specific to the  structure of the data that is to be imported. For each unique data structure we must write a unique algorithm. It is impossible to just "Copy and Paste" from one data set into the application database.

Depending on the amount of data to be imported into the application, you will be required to upgrade to a premium membership when your data is imported. This is because we don't want a large amount of data residing in the main application database.

We have currently written data import code for the following applications:

• DJ Webmin
• E Webmin
• Gigbuilder 3
• Gigbuilder 4
• Gigbuilder 5
• Gigbuilder 6
• Infomanager 2
• Infomanager 3
• DJ Calendar
• DJ Pro

We have not written data import code for the following applications:

* DJ Intelligence - there is no database to import, it is just a collection of forms

If you have a database of events in another popular event management software application, we would be willing to consider writing the import subroutines for it. Please contact us with the name of the application.

If you have a database of events that is stored in a proprietary format (a format that you designed), we would be willing to consider writing the import subroutine for it. If we are not able to reuse the code for other future users, any time spent developing the code will be fully chargeable to you personally. We will provide an estimate for the work involved. Before work begins on a custom written import, 50% of the estimate will be required. We have written these custom import routines before, but it is generally for larger companies or companies with large amounts of data to import.

More information regarding data import procedures can be found here.

* Technical explanation: Referential integrity of the data must be maintained in the application. Many data tables within the application contain pointers to entries in other tables. They are linked through primary keys. For example, in the event table, there is only one value stored for the primary venue. That value is the primary key of the venue, which is stored in the venue table.