Every investor entry you add to a company profile gets mapped, once, to a specific Recruiterflow company record. Understanding how that mapping works helps you avoid creating duplicate investor profiles or accidentally repointing data you didn't mean to change.
How mapping works
Investor mappings are account-wide: once an investor string like "Meridian Capital" is mapped to a Recruiterflow company ID, every instance of that same investor entry across your account, no matter which portfolio company's profile it was typed on, resolves to that same investor profile.
Renaming vs. remapping: they're not the same thing
Renaming is editing the display text of an investor entry, like fixing a typo. This does not change what the entry is mapped to.
Remapping is pointing an investor entry to a different Recruiterflow company profile entirely. This is the only action that changes what the entry resolves to, and it re-aggregates everything tied to that relationship, including jobs, placements, deals, contacts, and portfolio membership, against the new mapping. No stale data is left behind from the old mapping.
Example
You notice an investor entry reads "Meridian Cap" instead of "Meridian Capital." Fixing the spelling is a rename, the mapping to Meridian's company profile stays exactly as it was. But if you realize the entry was mapped to the wrong Meridian entirely, changing which company profile it points to is a remap, and every rollup tied to that entry instantly reflects the correct investor.
Things to know
Mappings don't cross accounts. Each Recruiterflow account maintains its own investor mappings independently.
There's no single screen to view or manage every investor mapping in your account today. Mappings are managed from each company profile individually.
Enrichment automatically adds new investor matches for AIRA Plan and JCA-enabled accounts, but skips adding a match if that investor string already exists on the profile, so you won't see duplicates from enrichment.