1. Keep the Local Test server shut down while organizing and cleaning Projects and their constituent objects.
1a. The reason for this is that Clarify Studio incrementally (and automatically) re-deploys changed Clarify objects and Projects to the Local Test server as you save them. It’s more efficient to make several changes, review/approve them, and then allow Clarify Studio to deploy all the changes at once.
2. EXTOL’s suggestion for dealing with large and/or complex environments is to convert your Projects, and then test and roll each Project into production individually.
2a. This is safer and easier than attempting to convert everything and then “go live” with everything at once. It’s also likely you will discover more Projects that are candidates for sharing than you originally thought.
3. Clean up the Project(s) containing common Clarify objects first. This makes it easier when cleaning up Projects that reference the common Project(s).
3a. Ruleset Data Objects (RDOs) are a new Clarify v3 construct that can be attached to a Ruleset. Although they are much more flexible, they approximate the glb section of the “Middle Tree” in EBI v2. The Clarify v3 advantage is that you can share RDOs between various Rulesets. It may be a good idea for you to put your shared RDOs in a common Project and reference them accordingly. If you’re not sharing RDOs, then it’s better to keep each RDO with its Ruleset.
3b. Since a Data Source is likely to be shared by more than one Database Adapter, it’s generally a good practice to place your Data Sources in a common Project and reference them accordingly.
4. Choose ONE Project to clean up and close the rest (except for common or referenced Projects). This keeps Clarify Studio running fast and using as little memory as possible.
5. After a Project is cleaned up and error-free, start the Local Test server to test the Project.
6. When happy with the results of one Project, commit it to your Version Control System, close it, and move on to the next Project.

**Source: Cleo documentation: EBI v2 to v3.1 Conversion Guide.pdf