Summary
After migrating projects to Catina, you may notice multiple projects with the same name followed by Copy 1, Copy 2, Copy 3, and so on. This article explains why this happens, how to identify the correct project to use, and how to prevent duplicate projects during future migrations.
Why Duplicate Projects Are Created
Duplicate projects are created when the same ACD5 project is migrated more than once. Each migration creates a new Catina project. To prevent overwriting existing data, Catina automatically adds Copy 1, Copy 2, etc., to the project name.
This commonly occurs when:
A migration is run multiple times for the same project
A migration is restarted after an interruption or error
Multiple users migrate the same ACD5 project independently
A partially migrated project is migrated again
Important Things to Know
Each duplicate is a separate Catina project
Projects are not synced with one another
Changes made in one copy do not appear in the others
Only one project should be used as the active working project
How to Identify the Correct Project
To determine which project to continue using:
Open each project copy
Check which one contains the most complete documents and recent updates
Confirm which project your team is actively working in
Continue working in only that project
Unused duplicate projects can be ignored or deleted if you have permission.
How to Prevent Duplicate Projects in the Future
To avoid creating duplicate projects during migration:
Migrate each ACD5 project only once
Confirm a project has completed migration before restarting the process
Coordinate with your team so only one person migrates each project
Avoid re-migrating projects that were partially completed unless instructed by Support
Tip: If a migration appears stuck or fails, contact Support before attempting to migrate the project again.
FAQs
Why do my migrated projects have names like Copy 1, Copy 2, or Copy 3?
These copies are created when the same ACD5 project is migrated more than once. Each migration creates a new Catina project, and Catina adds “Copy” to the name to avoid overwriting existing data.
Which duplicate project should I continue working in?
Use the project that contains the most complete and up-to-date documents. Changes made in one copy do not appear in the others.
How can I prevent duplicate projects from being created again?
Make sure each ACD5 project is migrated only once, confirm the migration has completed successfully, and coordinate with your team so only one person migrates each project.