01Who this is for
- Founders launching a new subaccount can clean up placeholder records before real data is added.
- Agency administrators can customize sample contacts, tasks, and notes to fit client onboarding templates.
- CRM managers can quickly spot and remove example records to keep the database tidy.
02Sample data, explained
When a new subaccount is created, HighLevel inserts sample records for Contacts, Tasks, Notes, Companies and Tags. If the subaccount location has a default pipeline, sample Opportunities and Pipelines are also generated. All example records carry an "(Example)" prefix in their names, making them easy to distinguish from real entries.
These records are fully editable and can be deleted at any moment, giving users full control over the initial data set. The feature does not affect subaccounts that were created before the setting was enabled; those accounts retain whatever data they already contain. The sample data lives within HighLevel module of the HighLevel platform, accessible through the standard record lists.
03How businesses use sample data
- Marketing agency. The agency creates a new subaccount for a client, then opens the sample contacts and edits the fields to match the client’s lead capture format. Unneeded example tasks are deleted to start with a clean slate.
- Real estate firm. Agents open the sample notes, modify the content to align with their listing guidelines, and remove any example records that are not relevant.
- SaaS startup. The onboarding team reviews the newly created subaccount, looks for records with the "(Example)" prefix, and deletes them before importing actual customer data.
04The numbers and rules that matter
- Sample data includes Contacts, Tasks, Notes, Companies, and Tags.
05How to set up and use sample data in HighLevel
Edit or delete sample data
- Open any sample record marked with "(Example)", make desired changes, or delete the record entirely.
Understand default pipeline impact
- Verify whether a default pipeline is set for the location; if not, only contacts, tasks, notes, companies and tags are created as sample data.
Confirm existing subaccounts are unaffected
- Create a new subaccount and observe sample data; note that previously existing subaccounts retain their original records without added examples.
Identify sample records
- Look for the "(Example)" prefix at the start of a record’s name to distinguish sample data from real entries.
06Things to know before you rely on it
- Sample data is generated only for newly created subaccounts.
- If a location lacks a default pipeline, sample Opportunities and Pipelines are omitted.
- All example records are prefixed with "(Example)" for easy identification.
07How it connects to the rest of HighLevel
- Configure searchable fields for contact records. Searchable fields guide
- View and sort contact records using list views and filters. List views and filters
- See the pricing plans for HighLevel. Pricing page
Michael's take

If I were setting up a new subaccount, I would strip out any "(Example)" contacts and keep only the pipeline structure I need. That way the team sees a clean board and can start adding their own records without distraction.