Reltio Connect

Hi Experts,

We are evaluating splitting Individual and Organization profiles into separate entity types in Reltio and would appreciate guidance from the community on best practices and implementation considerations.

Current Setup:

• We currently have two entity types:
  • Customer
  • Customer CA
• Both entities contain a mix of:
  • Individual profiles
  • Organization profiles
• We use a Business Flag attribute to distinguish profile type:
  • Business Flag = 0 → Individual
  • Business Flag = 1 → Organization

We are considering moving towards separate entities for Individuals and Organizations, mainly due to:

• D&B enrichment applicability only for organizations
• Matching/survivorship complexity
• Governance and scalability concerns

Our main concern is around relationships, as currently both profile types are part of the same entity model and many downstream integrations/reference relationships depend on it.

Questions:

1. Has anyone implemented a similar split from a combined customer model into separate Individual and Organization entities?
2. What were the major challenges during migration, especially around:
   • relationships
   • crosswalks
   • downstream integrations
   • historical data migration
   • matching rules
3. Would you recommend separate entities as a best practice for long-term scalability, governance, and enrichment integrations like D&B?
4. Any recommendations specifically for D&B enrichment with mixed-profile customer models?

Would appreciate hearing about real implementation experiences and lessons learned.

Thanks in advance!