---
title: HealthSherpa GoHighLevel (GHL) Sync Simple Step‑by‑Step Guide
description: "[Health Sherpa Data Sync Complete Demo](https://www.loom.com/embed/735683c93efc4f63829d46e4223f678c#?secret=5FdKobWde2) ## **What you need before starting** - Two files from HealthSherpa: 1. **Enrollment file (CSV)**—has all the basic details like FFM ID, first name, last name, phone, and email. 2. **The DMI file (CSV)**…"
url: "https://help.affordablecare.ai/docs/healthsherpa-gohighlevel-ghl-sync-simple-step%e2%80%91by%e2%80%91step-guide/"
updated: "2025-10-22"
category: Getting Started
---

# HealthSherpa GoHighLevel (GHL) Sync Simple Step‑by‑Step Guide

[Health Sherpa Data Sync Complete Demo](https://www.loom.com/embed/735683c93efc4f63829d46e4223f678c#?secret=5FdKobWde2)

## **What you need before starting**

- Two files from HealthSherpa:

  1. **Enrollment file (CSV)**—has all the basic details like FFM ID, first name, last name, phone, and email.
  2. **The DMI file (CSV)** has extra details, and it connects to the enrollment file using the **FFM ID**.
- A GoHighLevel account (make sure you can log in and select the right account or sub‑account).
- (Optional) **Tags** you want to use in GHL. If you don’t have them yet, create them in GHL under **Settings → Tags**.

### **Step 1—Import the Enrollment file**

1. Go to **Import** in HealthSherpa.
2. Choose the **enrollment file** and upload it.
3. The system will try to match the columns automatically. Double‑check them (this is called **field mapping**).
4. Click **Submit**. Wait for the records to import.
5. After it finishes, go back and confirm that **enrollments** are showing.

### **Step 2—Import the DMI file**

1. Go to **Import** again.
2. Select the **DMI file**.
3. The system will **link DMI records** to the enrollment records if the **FFM ID** matches.
4. After it finishes, check in **Enrollments** that the DMI info is connected.

Example: You can now filter by DMI type, status, or date.

### **Step 3—Connect to GoHighLevel**

1. Go to **Integrations**.
2. Click **Connect** under GoHighLevel.
3. Log in to GHL, give permission, and select your account (and sub‑account if asked).

### **Step 4—Pick which records to sync**

1. Open **Enrollments**.
2. Apply filters if you want (e.g., by DMI type, status, or date).
3. Select the records.
4. Click **Sync with GHL**.

### **Step 5—Map fields to GHL**

You now need to choose where the HealthSherpa fields go inside GHL.
**Required fields (shown in red):**

- First Name
- Last Name
- Phone
- Email

**Optional fields:**

- Any extra fields (map them if you want to save them in GHL).

### **Step 6—Add tags (optional)**

- Choose tags to add to the contacts.
- If a tag doesn’t exist yet, create it in GHL settings, then try again.
- Tags are useful because you can run **automations** in GHL based on tags.

### **Step 7—Sync and confirm**

1. Click **Sync with GHL**.
2. Wait a few seconds. You’ll see how many records were synced.
3. Go into GHL and check:

   - Contacts are created or updated.
   - Tags are showing.
   - Data looks correct.

### **Common problems & quick fixes**

- **DMI didn’t link?** → Check that FFM IDs match exactly in both files.
- **Red fields not mapped?** → Make sure you map First Name, Last Name, Phone, and Email.
- **Missing tags?** → Create the tags in GHL first.
- **Wrong account connected?** → Disconnect and reconnect under Integrations.

### **Best tips**

- Always import the **enrollment file first, then the DMI file**.
- Start with a **small test batch** (5–10 records) before syncing everything.
- Use clear file names (like enrollment_2025-09-27.csv).
- Keep a simple list of how fields should map so you do it the same way every time.

### **Quick glossary**

- **FFM ID**—Unique ID used to match Enrollment and DMI records.
- **Enrollment file** – Base file with client details.
- **DMI file** – Extra data linked by FFM ID.
- **Tags**—Labels in GHL are used to group and run automations.
- **Field mapping**—Choosing which column goes into which GHL field.

**That’s it!** By following these steps, you can easily sync HealthSherpa data into GoHighLevel without confusion.