Background information to my question:
- I am about to deploy a new release of a Salesforce Service Cloud solution to a customer
- The customer primarily utilizes the solution for B2C purposes
- In the release that is being used by my customer, there are 100.000+ cases and 50.000+ contacts
- In the first release of the solution, only Cases and Contacts were used. In second release, I am introducing Accounts
- In the first release, we relied on a Public data model. In the new release we are converting to a Private Data Model. Because of the new Private Data Model, I have to somehow assign all contacts to an account.
- I am aware that Salesforce suggests solving this problem by converting into Person Accounts, but because it is such an extensive change (permanent change), which would have so many complications for my customer, I am thinking of following an alternative approach: creating a new account called "No account", which I will assign all 50.000+ contacts to.
And here comes my questions:
- What are your general thoughts on the above?
- What do you think about my alternative approach?
- Could any issues arise from so having so many contacts related to the same account?
- What are pros and cons of following my suggested alternative approach VS. converting to person Accounts?
- Can you think about any additional approaches to address this problem? For instance, would it be better to just create a new custom object that replicates some of the functionality of the standard Account-object/layout, etc.