---
updatedAt: 2026-09-16T14:13:30.000Z
agentTools:
projectIndex: https://ror.readme.io/llms.txt
---
# Transition from Open Funder Registry to ROR
In September 2023, Crossref and ROR announced a long-term plan to deprecate the Open Funder Registry (formerly known as FundRef) and merge it into ROR, the Research Organization Registry. In September 2026, Crossref began adding ROR IDs to publisher-supplied metadata that includes funder names but no identifiers.
We're thrilled that ROR is set to become the standard identifier for funders, and we're determined to help make this transition as easy as possible for all concerned. Here are some answers to frequently asked questions about this transition, including guidance on how to switch from using Funder IDs in your metadata to using ROR IDs.
# Why is this transition happening?
Merging the two registries will make workflows more efficient and less confusing for all concerned and will enable the development of robust new services that use organization identifiers. The Open Funder Registry currently includes about 45,000 IDs and records for funders, and a large majority of the most-used of these Funder IDs already exist in ROR, with others being continually added through ongoing curation work. Funders, publishers, and others should not need to decide whether to use Funder IDs or ROR IDs and should not need to use both: a single registry, ROR, can fulfill the purpose of identifying research organizations -- including funders.
# When is this transition happening?
This transition is happening now! Users of the Open Funder Registry can begin the work of switching to ROR at any time. ROR's [data structure](https://ror.readme.io/docs/ror-data-structure) has always included an external identifier field to enable mapping of ROR IDs to Funder IDs, and ROR has been [working since 2022 to add and update ROR records from Open Funder Registry data](https://ror.org/blog/2023-10-12-ror-funder-registry-overlap/). The Open Funder Registry will continue to be updated and its existing technical infrastructure will remain available for the foreseeable future, but future systems and processes at Crossref will be designed to use ROR IDs to identify funders.
# Can I use ROR IDs instead of Funder IDs in Crossref metadata?
Yes, you can! If you are a Crossref member, you can [now use ROR IDs to identify funders](https://www.crossref.org/blog/come-ror-with-us-using-ror-ids-in-place-of-funder-ids/) in any place in Crossref metadata where you currently use Funder IDs. You can consult [Crossref documentation on funding metadata](https://www.crossref.org/documentation/funder-registry/funding-data-overview/) to learn more.
# Will every Funder ID have a corresponding ROR ID?
Our aim is to provide comprehensive coverage of Funder IDs that are widely used, are not duplicates or errors, and are in [scope](https://ror.org/registry/#scope-and-criteria-for-inclusion) for ROR. Based on our analysis of funding data in Crossref, DataCite, and ORCID metadata, about one-third of the Funder Registry accounts for the majority of actual usage, so weโre creating and updating ROR IDs for funders on this basis. Currently, there are ROR IDs for over 94% of cases where a Funder ID is used in DataCite and Crossref DOI records. We will continue to improve this coverage to better support the funder identification use case. See How ROR and the Funder Registry Overlap to learn more.
# Will Funder IDs continue to resolve?
Absolutely! Funder IDs are DOIs, and as such are persistent. The Funder ID for the Alfred P. Sloan Foundation, for instance, is [\](https://doi.org/10.13039/100000879) (or `100000879` in some usages), and Crossref will ensure that all such Funder IDs continue to resolve to a page with information about that funder.
# Will the Crossref Funder API remain available?
Yes, Crossref will maintain the current funder API endpoints at `https://api.crossref.org/funders` at least until ROR IDs become the predominant funding identifier for newly registered content, and perhaps beyond.
# Will the Crossref Funding Data search remain available?
Yes, Crossref will maintain the current [funding data search](https://search.crossref.org/search/funders), which connects funders to published works, at least until ROR IDs become the predominant funding identifier for newly registered content, and perhaps beyond.
# I use Funder IDs in my system. How can I switch to ROR?
We're here to help! Take a look at the guidance below and write with any questions.
## Two quick resources for switching from Funder IDs to ROR IDs
- [Map other organization IDs to ROR IDs](https://ror.readme.io/docs/mapping) - guide to help you map Funder IDs to ROR IDs using the ROR API, data dump, or sample scripts
- [Create ROR-powered forms](https://ror.readme.io/docs/forms) - guide to creating a funder lookup field in your system using ROR
## Find both IDs for a single funder
To find both the Funder ID and the ROR ID for a single funder, go to and search for a funder name to determine whether that funder has a ROR record. If the ROR record exists and is mapped to a Funder ID, the ROR record will include both the ROR ID and the Crossref Funder ID.
You can also type the suffix of the Crossref Funder ID itself in the ROR web search to find the record. For the Alfred P. Sloan Foundation, the search term `100000879` returns the ROR record.
## ROR IDs and Funder IDs are not always mapped on a one-to-one basis
A single ROR ID can often be mapped to multiple Funder IDs. When a ROR ID has multiple corresponding Funder IDs, the preferred Funder ID is stored in the field `external_ids.preferred` in v2 of the ROR metadata schema. Be sure to check the [status](https://ror.readme.io/docs/ror-data-structure#/status) of the mapped ROR record to ensure that it has a status of "active."
## Get a CSV file of all Funder ID to ROR ID mappings
To get a CSV file of Funder ID to ROR ID mappings, retrieve the latest copy of the ROR [Data dump](https://ror.readme.io/docs/data-dump) from Zenodo at and download and unzip the .zip file. The provided CSV will show mappings between ROR IDs and, where available, one or more Funder IDs in the `external_ids.all` field. Remember that one ROR ID can have multiple corresponding Funder IDs. When this is the case, the preferred match is stored in the field `external_ids.preferred`.
## Map a custom list of Funder IDs to ROR IDs
Because Funder IDs are included in ROR records in the [external\_ids](https://ror.readme.io/docs/ror-data-structure#external_ids) field, you can map a custom list of Funder IDs to ROR IDs using the ROR API or ROR data dump. This method will also allow you to retrieve additional ROR metadata. For more information and examples, see our guide [Map other organization IDs to ROR IDs](https://ror.readme.io/docs/mapping).
## Build ROR-powered forms
You can build ROR-powered funder lookups into your system so that researchers, editors, funder staff, and other users can easily select a funder by name that is connected to a ROR ID and its associated metadata. See [Create ROR-powered forms](https://ror.readme.io/docs/forms) for guidance.
# How can I give feedback on or get support for this transition?
* For ROR technical or metadata questions, write .
* For Open Funder Registry technical or metadata questions, [contact Crossref](https://support.crossref.org/hc/en-us/requests/new).
# Where can I learn more?
* **Crossref Services - Open Funder Registry** - general information about the Open Funder Registry
* **Crossref Open Funder Registry - GitLab** - complete downloadable Open Funder Registry data
* **Crossref Funder Advisory Group** - advisory group for Crossref funder members
* **Open Funder Registry to transition into ROR**, blog post, September 7, 2023
* **How ROR and the Open Funder Registry Overlap: A Closer Look at the Data**, blog post, October 12, 2023
* **ROR-ing ahead: using ROR in place of the Open Funder Registry**, blog post, January 30, 2024
* **Why We All Need Good Funding Metadata**, panel slides and recording, January 31, 2024
* **Come ROR with us: Using ROR IDs in place of Funder IDs**, blog post, March 4, 2025
* **Improving How Funding Connects to Research Outputs**, blog post, September 15, 2026