Legacy Migration Overview
Move your API calls, CSV workflows, and CRM enrichment to your new key.
Use this guide to move an existing Crunchbase integration from a legacy API key to your newly provisioned key. Start by retrieving your key, follow the migration path for each way you use Crunchbase data, then validate your workflows before coordinating retirement of the legacy key.
1. Get your new key
Open Crunchbase API integrations, sign in, and select Show Key.
Your new key is provisioned to a package based on your current agreement. If you cannot find it, or the access shown does not match what you expect, contact your account team before proceeding.
For help finding your key, see API key retrieval instructions.
2. Choose your migration path
Follow every path that applies to your integration. For example, a team using both API calls and scheduled CSV downloads should complete both guides.
| How you use Crunchbase today | What to update | Start here |
|---|---|---|
| Direct API calls from your application, scripts, or API tools | Credentials, endpoint URLs, and any request or response handling affected by the migration. | Migrate API calls |
| CSV exports downloaded manually or by scheduled jobs | Export URLs and credentials, plus column mappings used by your downstream workflows. | Migrate CSV workflows |
| CRM enrichment through the Crunchbase Salesforce or monday.com integration | The API key and connection settings in your CRM integration. | Migrate CRM enrichment |
Changing the key is one part of the migration. Use the relevant guide to check whether URLs, data mappings, or integration settings also need to change.
References to keep alongside your migration
- API calls: use the legacy-to-current endpoint mapping to identify replacement URLs.
- CSV workflows: consult Legacy exports for available files and download URLs, and Legacy CSV Field Mapping for column changes.
- Package access: use API Packages Overview to find the reference for your provisioned package.
3. Validate each workflow
Before considering the migration complete, confirm that:
- Every application, scheduled job, and CRM connection you identified uses the new credentials.
- API requests return the expected records and fields, CSV files download and load correctly, and CRM enrichment updates the intended records.
- Your downstream processing still handles the returned data correctly, including any updated field or column mappings.
- Scheduled workflows have completed successfully with the new key.
If you encounter missing access or a workflow fails, contact your account team with the affected workflow and error details. Do not include your API key.
4. Confirm completion with Crunchbase
Once all applicable workflows have been validated, notify your account team that the new key is in use and coordinate retirement of your legacy key. Include the migration paths you completed and any unresolved issues.
Ready to begin? Choose API calls, CSV workflows, or CRM enrichment above.
Updated 5 days ago