Preparing to Import Data

Before you attempt to import data into the database, prepare your strategy. Some things you will need to consider are:

Is the data that you want to import unique, or does it conflict with data already in the database?

The import data feature will not replace existing data. For instance, if you are importing jobs from a legacy system, you cannot import job data if the jobs you want to import contain job numbers that already exist in the database.

Do you have Folder Types defined in your database to accommodate the type of data you want to import?

Does the data you want to import correspond to Folder Types defined in your Job Manager database? Job Manager comes with predefined Folder Types, and can be extended with User Defined Folder Types. When importing data, you have to select a Folder Type for the records you want to import.

Do you have fields in your database to accommodate the data to be imported?

Before importing data, you will need to ensure that you have appropriate fields defined in the Job Manager database that correspond to the data fields you want to import.

Can you test the data import in a test environment before importing into your production database?

It is always recommended that you import data into a test environment before importing it into your production environment. By doing this, you have the opportunity to both test your import files and evaluate the results of importing data without putting your production data at risk.