Personal Edition
Personal Edition was a retired, single-user Salesforce CRM edition built for an individual sales representative who wanted basic contact and account management without a team license.
Definition
Personal Edition was a retired, single-user Salesforce CRM edition built for an individual sales representative who wanted basic contact and account management without a team license. It gave one person access to accounts, contacts, activities, and synchronization with Microsoft Outlook, plus a small set of sales tools. Salesforce no longer sells it, so this entry describes what it was rather than something you can buy today.
The edition sat at the very bottom of the old lineup. It capped the org at one user, allowed only five custom fields per object, and offered no custom objects, custom apps, or Lightning Experience. Salesforce now lists Personal Edition among editions that are no longer sold, alongside Contact Manager, Group, Performance, and Database.com.
How Personal Edition worked and what took its place
What Personal Edition actually included
Personal Edition was a single-user CRM solution aimed at an individual sales rep, not a company. The official Salesforce documentation describes it as giving access to key contact management features such as accounts, contacts, and synchronization with Microsoft Outlook. It also handed the rep a few sales tools, most notably opportunities, so one person could track deals in a pipeline. The intent was simple. A solo seller could keep their book of business in Salesforce instead of a spreadsheet, and could push contacts back and forth with Outlook so email and CRM stayed roughly aligned. There was no team, no shared records, and no concept of roles or a sharing model beyond a single owner. Because everything belonged to one user, the edition skipped the collaboration features that define the rest of the platform. Activities, calendars, notes, and attachments rounded out the day-to-day surface. The product was deliberately narrow, which is why it could be priced as an entry point rather than a full business tool. That narrowness is also why Salesforce eventually retired it in favor of small-business suites that scale past one seat.
The opportunities cutoff in June 2009
One detail trips people up when they read old Personal Edition material. Opportunities were part of the edition, but only for orgs created early enough. Salesforce documentation states plainly that Personal Edition orgs purchased after June 2009 do not have access to opportunities. So two Personal Edition orgs could look different depending on their sign-up date. An org from 2007 might show a working Opportunities tab, while one from 2011 would not. This matters if you ever inherit a legacy org and wonder why a documented feature is missing. It is not a bug or a permission problem. It is the edition behaving exactly as Salesforce defined it after the 2009 change. The practical effect was that later Personal Edition orgs became closer to pure contact management, without the deal-tracking pipeline that made the edition useful for active selling. Anyone relying on opportunities had a strong reason to move up to a paid, multi-user edition. If you are auditing an old org and see no opportunities, check the creation date before you spend time troubleshooting. The behavior is by design, documented, and not reversible inside Personal Edition itself.
The hard limits that defined it
Personal Edition was capped tightly, and the caps explain why it could not grow with a business. The org allowed exactly one user account. You could not add a second seat, so the moment a second person needed access, the edition stopped fitting. Customization was minimal. You got five custom fields per object, and that was the ceiling. There were no custom objects, no custom apps, no custom tabs, no permission sets you could build, and no active validation rules. In practice this meant you worked with the standard objects as Salesforce shipped them, with only a handful of extra fields to capture your own data points. File handling was modest too, with a 5 MB cap on document uploads. Compare that to Contact Manager, which allowed five users, twenty-five custom fields per object, five custom objects, and three custom tabs, and you can see Personal Edition was a clear rung below it. These constraints were not accidental. They kept the edition simple and cheap, suited to one person tracking contacts and deals. The same constraints made any real automation, integration, or team workflow impossible, which is the core reason it did not survive.
No Lightning Experience, and why that signals its age
Personal Edition predates the modern Salesforce interface. The documentation is explicit that Lightning Experience is not available in this edition, and the same is true for Contact Manager and Group. That single fact tells you a lot about the era it came from. Lightning Experience became the flagship interface in the Winter 16 release, and Salesforce invested heavily in steering every active edition toward it. An edition that never received Lightning is an edition Salesforce had already decided not to carry forward. Users on Personal Edition stayed on the older Salesforce Classic look and feel, missing the redesigned record pages, the App Builder, and the broader Lightning toolset. For a solo user managing contacts, that gap might not sting day to day. For Salesforce as a company, it confirmed the edition was a legacy artifact rather than part of the roadmap. When you read that an edition has no Lightning Experience, treat it as a strong hint that the edition is either retired or close to it. Personal Edition fits that pattern exactly, and its absence from Lightning lines up with its later removal from the price list.
Why Salesforce retired it
Salesforce retired Personal Edition because its strategy moved away from a free or near-free single-seat product and toward small-business suites that can scale. The edition offered no customization worth the name, no automation, and no integration, which are the things that make Salesforce valuable once a business grows past one person. A single-user CRM with five custom fields and no custom objects had a very short runway. The day a second salesperson joined, or the day the owner wanted a custom process, Personal Edition could not deliver. Rather than keep maintaining an edition that almost everyone outgrew immediately, Salesforce folded that audience into newer entry points. The current lineup leads with Starter Suite and Pro Suite for small teams, then Professional, Enterprise, and Unlimited for larger needs, plus a free Developer Edition for building and testing. Salesforce now lists Personal Edition among editions that are no longer sold. Existing customers on a retired edition can typically keep using it, but no new orgs are created on it. The lesson for buyers is to start on an edition that can grow, since migrating later is more work than choosing correctly up front.
What to do if you encounter one today
You can still run into Personal Edition in the wild. A long-time individual user might hold a legacy org, or you might find an old account while consolidating systems. Treat any Personal Edition reference as historical information, not a current option, since you cannot sign up for a new one. If a person on Personal Edition needs more than basic contact tracking, the path forward is a current edition rather than a patch. Evaluate Professional for full-featured CRM with customization, or Enterprise when API access and deeper administration matter. For pure evaluation without spending, a free Developer Edition or a standard trial lets you test capabilities before committing. Plan a real migration when you move off Personal Edition. Export the accounts, contacts, and any activities, then import them into the new org and re-establish the Outlook connection through current tooling. Because Personal Edition has no custom objects or apps, the data model you carry over is small, which makes the move simpler than a typical org migration. Document the creation date and whether opportunities existed, so you map only the data that was actually in use. Confirm storage and licensing on the destination edition before you cut over.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Personal Edition.
- Salesforce EditionsSalesforce
- Salesforce Editions That Are No Longer SoldSalesforce
Hands-on resources to go deeper on Personal Edition.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What was Personal Edition?
Q2. Is Personal Edition available?
Q3. What should new users consider?
Discussion
Loading discussion…