Before installing IBM® Rational® Change, select a central CR database. You have two options:
Unpack a new, empty database to be your central CR database. That way, there are no development objects, such as tasks or source files, in the database. Then, you can migrate all existing CRs into that database with the CR migrate feature.
If you have an existing system environment where the set up is like a central database, you can designate that existing, non-empty database as your central CR database. Do so only when you have a database dedicated to CRs. For example, you can initially submit all CRs into one database. Then, use IBM Rational Synergy Distributed, also called Distributed Configuration Management (DCM), to transfer them to other databases before associating tasks.
If you have any tasks or objects, anything other than CRs and their attachments, in that initial database, they might become inaccessible or damaged in a central server. The advantage of using an existing database is that it might speed up migration if most of your CRs are already modifiable in that database.