TeamPulse Sample Import Data: Populate SuiteCRM for Testing

Evaluating a sales intelligence tool against an empty CRM is like test-driving a car with no fuel – you can confirm it starts, but you cannot tell whether it actually performs. TeamPulse sample data for SuiteCRM import solves this problem by giving you a realistic, pre-structured dataset that triggers real scoring, signals, and hygiene alerts the moment you switch TeamPulse to Live Mode. No manual data entry. No waiting for your team to generate enough activity history. Just a clean evaluation environment that behaves like a working sales team.

The sample data was introduced in TeamPulse v0.7.3 and is included in every installation package.

[Image Placeholder: SuiteCRM Admin import wizard showing CSV field mapping for TeamPulse sample data]

What Is Included in the Sample Dataset

The sample-data/ folder in your TeamPulse installation package contains five CSV files and one README. The data is deliberately varied – not every rep performs well, and not every deal is healthy. This ensures that TeamPulse’s scoring, signal, and hygiene engines all have something meaningful to evaluate.

The README_import.md file in the same folder contains step-by-step import instructions, field mapping tables for each CSV, and a post-import verification checklist.

Import Order Matters

SuiteCRM’s call, meeting, task, and opportunity records all reference user IDs. If you import activities before users exist in the system, the import will either fail or create orphaned records that TeamPulse cannot attribute to any rep.

Always import in this order:

1. 01_users.csv – creates the 27 user accounts that all other records reference
2. 02_calls.csv
3. 03_meetings.csv
4. 04_tasks.csv
5. 05_opportunities.csv

Do not skip steps or import multiple files in parallel. Each file depends on the records created by the file before it.

Step-by-Step: Importing the Sample Data into SuiteCRM

Step 1 – Locate the Files

After installing TeamPulse via SuiteCRM’s Module Loader, navigate to the sample-data/ folder within the installed package. If you uploaded the package via Module Loader, you can also find the sample files in the TeamPulse module directory on your server. Refer to README_import.md for the exact server path.

Step 2 – Import Users (01_users.csv)

1. In SuiteCRM, go to Admin (top navigation) and click Import, or navigate directly to Admin > Users and use the module-level import option.
2. Select 01_users.csv as the import file.
3. Work through SuiteCRM’s import wizard. When prompted for field mapping, refer to the mapping table in README_import.md – it lists each CSV column and its corresponding SuiteCRM field name.
4. Complete the import and confirm the record count matches: 27 users.

Step 3 – Import Activities and Opportunities

Repeat the import wizard process for each remaining file in order. For each import:

• Select the correct module (Calls, Meetings, Tasks, or Opportunities) before uploading the CSV
• Apply the field mappings from README_import.md – pay particular attention to the user relationship field, which links each record to its owning rep
• Confirm record counts match the table above before proceeding to the next file

Step 4 – Repair and Rebuild

After all five files are imported, run Admin > Repair > Quick Repair and Rebuild. This ensures SuiteCRM’s relationship indices and metadata are up to date before TeamPulse reads from the database.

After Import: Switch to Live Mode and Score the Data

By default, TeamPulse operates in Demo Mode immediately after installation – it displays built-in mock data so the UI is never empty. Once your sample data is imported and the repair is complete, switch TeamPulse to Live Mode:

1. Open TeamPulse and go to Settings > General.
2. Set the Data Source toggle from Demo to Live.
3. Save settings. TeamPulse will begin querying SuiteCRM directly.

The scoring engine will run on the imported data and populate the Dashboard, Health Scorecard, Leaderboard, and Signals views. Because the dataset was designed with varied performance levels, you should see a realistic spread of scores – some reps in the green, some with warning-level signals, and at least one or two with deal hygiene alerts active.

Verification Checklist

After switching to Live Mode, confirm the following before treating the environment as ready for evaluation:

• 27 active users are visible in the TeamPulse Leaderboard or Compare Reps view
• 403 calls are reflected in rep activity scores – call volume signals should be active for reps with lower call counts
• Coaching recommendations are firing in the Recommendations view – the overdue tasks in 04_tasks.csv are designed to trigger at least High-tier recommendations
• Deal hygiene alerts are visible in the Deal Hygiene Monitor – the stale opportunities in 05_opportunities.csv should generate pipeline health flags
• The Dashboard momentum chart shows week-over-week variation rather than a flat line – this confirms the 5-week call history is being read correctly

If any of these checks fail, review the import logs in SuiteCRM (Admin > Import > View Import History) and confirm that the user IDs in your activity CSVs match the user records created in step 2.

Next Steps: Clean Up and Import Your Real Data

Once you have completed your evaluation using the sample dataset, delete the imported records before going live with your team’s actual data. Use SuiteCRM’s standard record deletion or mass-delete tools to remove the sample users, calls, meetings, tasks, and opportunities. Then repeat the import process with your real team data and switch TeamPulse back to Live Mode.

If you prefer a clean slate, the safest approach is to evaluate TeamPulse on a separate SuiteCRM test instance and then install fresh on your production instance with real data from day one.

Frequently Asked Questions

Can I mix sample data with real data in the same SuiteCRM instance?

This is not recommended. Sample user accounts will appear alongside real users in TeamPulse views, skewing team averages and generating coaching recommendations for fictitious reps. The sample data is designed for a clean SuiteCRM test instance. If you must evaluate on your production instance, create a separate SuiteCRM team or role group for the sample users and filter accordingly – but a dedicated test instance is the cleaner approach.

Does importing sample data affect my TeamPulse license?

No. Your TeamPulse license is not metered by the number of records in SuiteCRM. Importing and then deleting sample data has no effect on your license standing. The 27 sample user accounts do not consume user license seats if your license is seat-based – confirm with your license terms if you are on a per-user plan, but in standard TeamPulse licensing, the sample import is free to use.

What if my SuiteCRM field names differ from the default mappings in README_import.md?

SuiteCRM allows administrators to rename and customize fields. If your instance uses non-default field labels, use SuiteCRM’s import wizard field mapping step to manually match each CSV column to the correct SuiteCRM field. The README_import.md lists both the SuiteCRM default field name and the underlying database column name – use the database column name as a fallback reference when field labels have been customized.