Database migration preparation

<< Click to Display Table of Contents >>

Navigation:  Administration > Database Administration > About Migrating Databases >

Database migration preparation

Concordance databases that you want to open in Concordance Desktop need to first be migrated to Concordance Desktop. Before migrating however, there may be some additional preparation involved, based on the version of Concordance with which the database was built, as well as some other factors.  

Concordance databases created with Concordance versions 8.x or 9.x must first be converted to Concordance 10.x databases, before they can be migrated to Concordance Desktop databases.

Only Concordance 8.x and 9.x databases can be converted to Concordance 10.x. If your database was built with an earlier version of Concordance, it cannot be converted to Concordance 10.x, and cannot be migrated to Concordance Desktop.

If using Concordance Image, prior to converting a Concordance 8.x or 9.x  database to 10.x, the imagebase must be converted from a version 4.0 imagebase to a version 5.0 imagebase in Concordance Image.

Additional factors in determining how a database should be prepared for migration to Concordance Desktop:

The version of Concordance used to create the database

Whether Concordance Image was used to view native files

Whether Concordance Desktop Viewer was used to view near native files

Whether the database has been moved

Whether the native files (only if using Concordance Image) have been moved

Whether the near native files (only if using Concordance Desktop Viewer) have been moved

Only Concordance version 10.x SQLite databases can be migrated to the Concordance Desktop database format. Therefore, all databases created with Concordance 8.x or 9.x need to first be converted to version 10.x SQLite databases before attempting to migrate them to Concordance Desktop.

Prior to converting a Concordance 8.x or 9.x version database to 10.x, you must convert the imagebase in Concordance Image from a version 4.0 imagebase to a version 5.0 imagebase. Only after this is done can you proceed with converting the database to Concordance version 10.x.

The migration is permanent and there is no process to convert a database back to a Concordance database. Therefore, we recommend that you make backup copies of the databases before migrating them to Concordance Desktop.

Do you plan on moving a database you want to migrate?

Concordance 10.x database (other than a 10.21 E-Documents database)

If you plan to migrate a Concordance 10.x database to Concordance Desktop, and also plan to move it to another server, drive, or folder, please follow the steps below, in the order they appear.

1.Move the database to its new location.

2.Open the database in Concordance 10.x. Doing this ensures that the notes DCB is properly linked to the parent DCB.

3.If the native files have been moved, edit the native file path (see Updating hyperlinks file path), and then recreate the hyperlinks in the records using the CreateHyperlinks CPL.

4.Re-index the database and test the hyperlinks to ensure they work.

5.Refer to the factors in the table below that apply to a Concordance 10.x database (other than a 10.21 E-Documents database).

Concordance 10.21 E-Documents database

If you plan to migrate a Concordance 10.21 E-Documents database, and also plan to move it to another server, drive, or folder, please follow the steps below in the order they appear.

1.Move the database to its new location.

2.Open the database in Concordance 10.21. Doing this ensures that the notes DCB is properly linked to the parent DCB.

3.If the native files have been moved, edit the native file path (see Updating hyperlinks file path), and recreate the hyperlinks in the records (see the CreateHyperlinks CPL topic).

4.Refer to the factors in the table below that apply to a Concordance 10.21 E-Documents database.

Database preparation checklist

Below is a checklist that provides the various preparations, based on the various factors listed above.

Database factor

Preparation

Concordance 7.x or below database

YES: The database cannot be migrated to Concordance Desktop.

NO:  Continue to next factor.

Concordance 8.x or 9.x  database

YES: Are you using Concordance Image?

Yes: If using Concordance Image 4.0 (formerly Opticon), the imagebase must be converted to Concordance Image version 5.0, prior to converting the database to Concordance 10.x.

Is the imagebase currently a Concordance 5.0 imagebase?

Yes: Convert the database to a Concordance 10.x database.
See Converting databases on the Concordance Answer Center.

No: Convert the imagebase to Concordance Image from version 4.0 to 5.0 first, then convert the database to Concordance 10.x.
See Converting imagebases and Converting databases on the Concordance Answer Center.

No: Concordance Image is not being used. There is no imagebase to convert.
You are ready to convert the database to Concordance 10.x.
See Converting databases on the Concordance Answer Center.

NOTE: Once the database has been converted to Concordance, 10.x, go to the Concordance 10.x (other than E-Documents) database factor below.

NO: It is not a Concordance 8.x or 9.x database. Continue to the next factor.

 

Concordance 10.x database

(other than a 10.21 E-Documents)

If the database is a Concordance 10.x database, other than a 10.21 E-Documents database, then follow this set of preparations.

YES: Are you using Concordance Image?

Yes: If the database folder contains a [database name].DIR file and a [database name].VOL file, it indicates that Concordance Image was used for the imagebase.

Do you want to maintain your redactions and notes when you migrate the database to Concordance Desktop?

Yes: Use the Redline Migration Utility to migrate the database to Concordance Desktop.

CAUTION: When using the Redline Migration Utility to migrate a 10.x database to Concordance Desktop, all data from the database moves over, but only redactions and notes are moved over from the imagebase.

NOTE: If you plan to move the database to another server, drive, or folder, move the database first, and then open it in Concordance 10.x to reset the link between the DCB and the Notes DCB. Once these two steps are finished, you can migrate the database.  

No: There is no need to run the Redlines Migration utility. The database is ready for migration to Concordance Desktop.

NOTE: If you plan to move the database to another server, drive, or folder, move the database first, then open it in Concordance 10.x to reset the link between the DCB and the Notes DCB, and then migrate the database.

No: Are you using Concordance Desktop Viewer?

Yes: If using Concordance Desktop Viewer, you can use any of the methods in the Migrating databases to Concordance Desktop topic, to migrate the database to Concordance Desktop.

CAUTION: When migrating a 10.x database to Concordance Desktop, all data from the database moves over, but markups (redactions, notes, etc.)are not moved over. Markups will need to be either burned in prior to migration, or reentered through Concordance Desktop after migration. Please note that burned in markups cannot be edited, they are permanent.

No: The database can be migrated, providing the database has not been moved. If the location of the database has changed since you last opened it in Concordance 10.x, please see the note above.

NO: The database is not a Concordance 10.x database (other than an 10.21 E-Documents database). Continue to the next factor.

Concordance 10.21 E-Documents database

If the database is a Concordance 10.21 E-Documents database, there are two final determining factors that need to be addressed; whether the database was built with the old e-documents engine or with the new e-documents engine. The new e-documents engine creates databases that are completely compatible with Concordance Desktop, however, the old e-documents database engine does not.

YES: Does the database folder contain a [database name].CIB file and a Near Natives folder?

Yes: This indicates that the database was built with the new 10.21 E-Documents engine, which is completely compatible with Concordance Desktop. The database is ready to be migrated.

NOTE: When migrating a 10.21 E-Documents database that was built with the new E-Documents engine, all data is moved over, and markups (redactions, notes, etc.) are also moved over. Markups will need to be reentered through Concordance Desktop after the database has been migrated.

No: The database was created with the old E-Documents database engine.

CAUTION: When migrating a 10.21 E-Documents database that was built with the old E-Documents engine, all data is moved over, but markups (redactions, notes, etc.) are not moved over. Markups will need to be reentered through Concordance Desktop after the database has been migrated.

NOTE: If you plan to move the database to another server, drive, or folder, move the database first, and then open it in Concordance 10.x to reset the link between the DCB and the Notes DCB. Once these two steps are finished, you can migrate the database.

NO: Return to the factor above that applies to the database version and type.