![salesforce person accounts vs standard accounts salesforce person accounts vs standard accounts](https://i.ytimg.com/vi/5CHfyWAe3zo/maxresdefault.jpg)
![salesforce person accounts vs standard accounts salesforce person accounts vs standard accounts](https://acumen.architecture.com.au/globalassets/asset-import/images/abic-contracts.jpg)
It isn’t until much later that they realize they are using a feature that is incorrect for their business and thus it is very inefficient. My experience, and what seems to be the experience of others during my research, seem to indicate that organizations tend to use Person Accounts without fully understanding their use-case in SalesForce. So, why would an organization want to split up a Person Account after going through the very specific process to create it? During this assignment, the user will have the ability to designate an existing Contact record to form the mandatory 1:1 relationship or else one will be automatically generated and assigned. A Person Account is denoted by the IsPersonAccount boolean on the Account object which is set when a Person Account record type is assigned to the Account record. Salesforce developed the concept of a Person Account for those who conduct business with individuals (B2C vs B2B). That is until a project came up where I had to convert a few million Person Account records into individual Account and Contact records. Did you know that you can split Salesforce Person Account records into Account and Contact records? Yea neither did I.