If your team previously created prospect lists in the legacy platform, you can migrate them into the new platform to continue working with them without rebuilding your lists.
Migration creates a copy of your legacy list in the new platform. Your original list remains unchanged and remains available in the legacy platform.
Prerequisites
Before migrating a list:
- You must have the RevOps role.
- Migration is started manually by an administrator from the Lists page in the new platform.
- Migration does not consume credits.
- Your original legacy lists remain available after migration.
Migrate a Legacy List
- Open Lists in the new platform.
- Select Migrate Legacy Lists.
- Choose the legacy lists you want to migrate.
- Start the migration.
Once complete, the migrated lists appear in Lists within the new platform.
You can then:
- View the migrated lists.
- Continue working with the contacts.
- Export lists to your CRM.
- Download lists as CSV files.
What is migrated?
During migration, Cognism preserves as much information as possible, including:
- List name.
- List owner (where the owner exists in the new platform).
- Contact membership.
- List creation and update timestamps (where reliable).
If a list owner no longer exists in the new platform, an administrator can reassign ownership after migration so the list remains manageable.
What happens to the contacts?
During migration, each contact is matched against Cognism's latest database.
Where newer information is available, the contact is automatically updated.
Updated contacts are clearly identified within the new platform so you can easily see which records have changed since the list was originally created.
Contact reveal status
Migrated contacts are not automatically revealed.
By default:
- Contacts remain unrevealed after migration.
- If a contact has already been revealed in the new platform and no job change has been detected, that revealed status is preserved.
- If a job change has occurred, the contact is treated as requiring a fresh reveal before updated contact information is available.
What happens to my Legacy lists?
Migration creates a copy of the list in the new platform.
Your original legacy list:
- Remains available in the legacy platform.
- Is not deleted or modified.
- Can still be downloaded as a CSV file if required.
Credit consumption
Migrating legacy lists does not consume credits.
Credits are only used when you:
- Reveal previously unrevealed contact information.
- Export unrevealed contacts.
Previously revealed contacts do not consume additional reveal credits during your current contract period unless refreshed contact information requires a new reveal because of a job change.
For more information, see Understanding Credit Consumption.
Frequently Asked Questions
Who can migrate Legacy lists?
Only users with the RevOps role can migrate legacy lists into the new platform.
Does migrating a list consume credits?
No. Migration itself never consumes credits.
Does migrating reveal contact information?
No. Contacts remain unrevealed unless they were already revealed in the new platform and no job change has been detected.
Will my Legacy lists be deleted?
No. Migration creates a copy in the new platform. Your original lists remain available in the legacy platform.
Will my contacts be updated?
Yes. During migration, contacts are matched against Cognism's latest database. Where newer information is available, the records are automatically refreshed and marked as updated.
What happens if the original list owner no longer exists?
If the original owner is no longer present in the new platform, a RevOps administrator can reassign ownership of the migrated list to another user.