Legacy CSV Field Mapping

Use this reference to map fields from the legacy Crunchbase CSV exports to their equivalents in the current Crunchbase API and static exports.

About this reference

The tables below are the complete legacy-to-current field crosswalk. Most rows are direct mappings. When a legacy field requires a join, relationship traversal, aggregation, filter, or derived value, its field name is linked to the corresponding recipe in Advanced migration patterns at the bottom of this page. Each recipe identifies the exact current fields and includes example v4 API calls.

Mapping notes

• N/A identifies a legacy field that was intentionally removed and has no direct replacement.
• Some mappings require deriving a value, joining another export, or aggregating related records. See Migration notes for the required transformation.
• Every mapping and note from the maintained legacy CSV mapping workbook is included below.

Legacy table index

acquisitions · category_groups · degrees · event_appearances · events · funding_rounds · funds · investment_partners · investments · investors · ipos · jobs · org_parents · organization_descriptions · organizations · people · people_descriptions

acquisitions

Back to table index

category_groups

Back to table index

degrees

Back to table index

event_appearances

Back to table index

events

Back to table index

funding_rounds

Back to table index

funds

Back to table index

investment_partners

Back to table index

investments

Back to table index

investors

Back to table index

ipos

Back to table index

jobs

Back to table index

org_parents

Back to table index

organization_descriptions

Back to table index

organizations

Back to table index

people

Back to table index

people_descriptions

Back to table index

Advanced migration patterns

The mappings above are usually direct field renames. This section covers the exceptions that require interpreting a structured value, combining collections, traversing a relationship, aggregating records, or deriving a value.

Before you run these examples

• Replace values in angle brackets, such as <IPO_ID>, with a UUID or permalink returned by Crunchbase.
• Replace YOUR_API_KEY with your API key. Keep the key in the X-cb-user-key header; do not embed it in saved code or documentation.
• Fields are optional. Handle missing objects and empty arrays in your transformation code.
• Card responses return at most 100 records per request. Use after_id to paginate when a card contains more records.

Exceptions covered

The generic rank fields marked N/A and degrees.cb_url are not included below because the current v4 schema provides no direct replacement that an API traversal could reproduce.

Read entity types and degree completion

Specific field mappings

The old type columns described the entity represented by the row. In v4, read entity_def_id. For participant type, read participant_identifier.entity_def_id. For degree completion, a populated completed_on.value confirms completion. A missing value may mean either incomplete or unavailable data, so it should not automatically be treated as a definitive false.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/degrees/<DEGREE_ID>?field_ids=entity_def_id,completed_on' \
  --header 'X-cb-user-key: YOUR_API_KEY'

Interpret the response as follows:

legacy degrees.type         = properties.entity_def_id
legacy degrees.is_completed = true when properties.completed_on.value is populated
missing completed_on.value     = unknown or incomplete; not conclusively false

For an Event Appearance:

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/event_appearances/<APPEARANCE_ID>?field_ids=appearance_type,participant_identifier' \
  --header 'X-cb-user-key: YOUR_API_KEY'

legacy participant_type = properties.participant_identifier.entity_def_id

Rebuild roles with facet_ids

Specific field mappings

facet_ids can contain more than one classification, so it replaces both the old role list and the lossy single primary_role value.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/organizations/crunchbase?field_ids=identifier,facet_ids' \
  --header 'X-cb-user-key: YOUR_API_KEY'

legacy organizations.roles        = every applicable value in properties.facet_ids
legacy organizations.primary_role = do not choose layout_id; retain the applicable facet_ids values

Rebuild the legacy Investors table

Every field under the legacy investors table comes from the union of qualifying People and Organizations records. After filtering both collections to the investor facet, apply the field mapping shown in the table above.

To rebuild the legacy Investors table, request qualifying Organizations and People separately, then union the results. Retain only records whose facet_ids include the investor classification.

curl --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/organizations' \
  --header 'X-cb-user-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "field_ids": ["identifier", "facet_ids", "investor_type", "num_investments"],
    "query": [{
      "type": "predicate",
      "field_id": "facet_ids",
      "operator_id": "includes",
      "values": ["investor"]
    }],
    "limit": 1000
  }'

curl --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/people' \
  --header 'X-cb-user-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "field_ids": ["identifier", "facet_ids", "investor_type", "num_investments"],
    "query": [{
      "type": "predicate",
      "field_id": "facet_ids",
      "operator_id": "includes",
      "values": ["investor"]
    }],
    "limit": 1000
  }'

Paginate each search independently with after_id, then concatenate the two result sets.

Rebuild events.event_roles

Specific field mapping: events.event_roles → distinct values from EVENT_APPEARANCES.appearance_type, joined where event_identifier identifies the Event.

Event roles belong to Event Appearance records, not the Event record itself. Retrieve the Event’s appearances card and collect the distinct appearance_type values.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/events/<EVENT_ID>/cards/appearances?card_field_ids=appearance_type,participant_identifier&limit=100' \
  --header 'X-cb-user-key: YOUR_API_KEY'

For example, appearances with appearance_type values of speaker, sponsor, and exhibitor produce those three values for the legacy event_roles field. The same response provides each participant’s legacy type through participant_identifier.entity_def_id.

If the card contains more than 100 records, take the final record UUID from the response and send the next request with &after_id=<LAST_UUID>.

Rebuild the legacy investment_partners table

Every legacy investment_partners field is sourced from INVESTMENTS. In particular:

The old table is a filtered view of Investments. Retrieve the required investment fields and retain records where partner_identifiers is not empty. Emit one output row for each partner identifier when an investment has multiple partners.

curl --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/investments' \
  --header 'X-cb-user-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "field_ids": [
      "identifier",
      "funding_round_identifier",
      "investor_identifier",
      "partner_identifiers",
      "created_at",
      "updated_at"
    ],
    "query": [],
    "limit": 1000
  }'

legacy partner_uuid = each properties.partner_identifiers[].uuid
legacy partner_name = each properties.partner_identifiers[].value

Use after_id to paginate until the complete Investments collection has been processed.

Traverse IPO geography

Specific field mappings

IPO geography belongs to the organization that completed the IPO. The traversal is IPO → Organization → Location.

1. Retrieve the IPO’s organization identifier.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/ipos/<IPO_ID>?field_ids=identifier,organization_identifier' \
  --header 'X-cb-user-key: YOUR_API_KEY'

2. Use organization_identifier.uuid or .permalink to retrieve the organization’s locations.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/organizations/<ORGANIZATION_ID>?field_ids=identifier,location_identifiers' \
  --header 'X-cb-user-key: YOUR_API_KEY'

Select the identifiers by location_type:

legacy ipos.city   = location_identifiers[] where location_type == "city" → value
legacy ipos.region = location_identifiers[] where location_type == "region" → value

3. Look up the country and region Location records for their codes.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/locations/<COUNTRY_LOCATION_ID>?field_ids=country_code' \
  --header 'X-cb-user-key: YOUR_API_KEY'

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/locations/<REGION_LOCATION_ID>?field_ids=region_code' \
  --header 'X-cb-user-key: YOUR_API_KEY'

legacy ipos.country_code = country Location properties.country_code
legacy ipos.state_code   = region Location properties.region_code

Retrieve organization street address and postal code

Specific field mappings

Use the headquarters_address card rather than attempting to reconstruct the street address from location_identifiers.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/organizations/<ORGANIZATION_ID>/cards/headquarters_address?card_field_ids=street_1,street_2,postal_code&limit=1' \
  --header 'X-cb-user-key: YOUR_API_KEY'

legacy organizations.address     = join street_1 and street_2 when present
legacy organizations.postal_code = postal_code

Interpret other structured location fields

Specific fields covered: the combined legacy country_code, state_code, region, and city rows under Acquisitions, Events, Funding Rounds, Investors, Organizations, and People. Use the exact structured location field named in each mapping-table row, then select identifiers by location_type.

Several legacy tables stored country_code, state_code, region, and city as separate columns. The replacement field is often a list such as location_identifiers, acquiree_locations, or funded_organization_location. Do not substitute location_group_identifiers: that field describes broader regional groups rather than the entity’s city, administrative region, and country.

Request the mapped location field on the relevant entity, then select the array item whose location_type matches the legacy column. If you need country_code or region_code and it is not embedded in that response, look up the selected Location identifier using the Location call shown in the IPO example.

Flatten multi-value identifier lists

Specific field mappings

The current category_groups field is an array of structured identifiers. Preserve every array element and join its value members in the order returned when recreating the legacy comma-separated column.

For category rows:

curl --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/categories' \
  --header 'X-cb-user-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "field_ids": ["identifier", "category_groups"],
    "query": [],
    "limit": 1000
  }'

For an organization:

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/organizations/<ORGANIZATION_ID>?field_ids=identifier,category_groups' \
  --header 'X-cb-user-key: YOUR_API_KEY'

legacy category_groups_list = properties.category_groups[].value joined with ","

Derive legacy domain fields

Specific field mappings

Request website_url, then parse its hostname. Do not remove subdomains unless your application explicitly requires a registrable root domain.

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/organizations/crunchbase?field_ids=website_url' \
  --header 'X-cb-user-key: YOUR_API_KEY'

JavaScript example:

const websiteUrl = response.properties.website_url;
const legacyDomain = websiteUrl ? new URL(websiteUrl).hostname : null;

Construct legacy Crunchbase URLs

Specific fields covered: every legacy field ending in cb_url, including entity URLs such as acquisitions.cb_url and relationship URLs such as acquisitions.acquirer_cb_url. Use the exact identifier/permalink expression and website path shown in the corresponding mapping-table row. degrees.cb_url is the exception and cannot be reconstructed.

For entities that still have linkable Crunchbase profile pages, build the URL from the returned permalink. For example:

curl --silent --show-error \
  'https://api.crunchbase.com/v4/data/entities/acquisitions/<ACQUISITION_ID>?field_ids=identifier' \
  --header 'X-cb-user-key: YOUR_API_KEY'

const permalink = response.properties.identifier.permalink;
const legacyCbUrl = `https://www.crunchbase.com/acquisition/${permalink}`;

Use the entity path documented in the mapping table (organization, person, funding_round, ipo, and so on). Degree records are the exception: they no longer have standalone linkable profile pages, so degrees.cb_url cannot be reconstructed.