This need for an overhaul typically reveals itself when an organization has three or more disparate business relationships are being facilitated within one database. For example, this occurs when a nonprofit is using Salesforce to manage their fundraising (much like B2B relationships for businesses), memberships (B2C) and e-commerce (B2C and B2B).
It is even more likely to occur if the development of these relationships are done iteratively over time, which is not uncommon for early adopters. For example, the company began building the CRM to accommodate e-commerce to sell to businesses, and then they decided to add the ability to manage events for individuals. Both are a commerce function but they require a different architecture when they are leveraged simultaneously rather than alone.
Like any ailment, you will notice symptoms that may indicate you have a bigger problem. Here are some of the symptoms you might notice:
- Broken (or confusing) reports.
- Multiple ways to view or enter data for the same contact.
- An inability to configure a new process without breaking an existing process. (i.e. you want to use an event solution with your Salesforce instance but can’t without conflicting issues arising with your e-commerce solution).