---
title: CAI MQL→SQL Automation — Field Mapping Fix
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-03-19-cai-hubspot-connect-131231738.md
tags:
- hubspot
- automation
- mql
- sql
- lifecycle-stages
- citrus-america
- field-mapping
layer: 2
client_source: null
industry_context: null
transferable: true
---

# CAI MQL→SQL Automation — Field Mapping Fix

## Overview

The automation responsible for advancing contacts from **Marketing Qualified Lead (MQL)** to **Sales Qualified Lead (SQL)** in Citrus America's HubSpot instance was broken due to a field mismatch. The trigger was linked to the wrong property, preventing the lifecycle stage transition from firing correctly.

This article documents the root cause, the fix, and the data migration steps required.

## Root Cause

The MQL→SQL workflow was configured to trigger on the field **"You juicing currently?"** — a field that is not the canonical qualifier for this transition. The correct field is **"Are you already juicing?"**, which includes the answer options that map to sales intent (e.g., *"No, but I seem interested"*).

Miriam identified the issue during a walkthrough of the contact lifecycle using a test contact, noting that filling out the correct fields did not advance the lifecycle stage as expected.

> *"I was not finding the potential number of locations and are you already juicing, which would be the qualifier to turn them into a sales qualified lead."*
> — Miriam Framson

Karly confirmed the misconfiguration:

> *"I just need to change out this field to the already juicing one... I'll just remove this one and then replace."*
> — Karly Oykhman

## Fix

### Step 1 — Relink the Workflow Trigger

In the MQL→SQL enrollment workflow, replace the trigger condition:

| | Field | Value |
|---|---|---|
| **Remove** | You juicing currently? | (any) |
| **Add** | Are you already juicing? | is any of: *No, but I seem interested* / *Yes* |

### Step 2 — Map Existing Data

Before hiding or deprecating **"You juicing currently?"**, export all contacts with a non-null value in that field and copy the data into **"Are you already juicing?"** where appropriate. This prevents loss of historical qualification data.

> *"In doing so, we also do need to map any information that's in this field over to that other field if we're hiding it."*
> — Karly Oykhman

### Step 3 — Verify the Fix

After relinking the trigger, re-run the test contact flow (Miriam uses a test contact named "Anna Musterfrau") to confirm:

1. Filling in **"Are you already juicing?"** with a qualifying answer advances the lifecycle stage to **SQL**.
2. No duplicate or conflicting triggers remain on the old field.

## Related Context

This fix is part of the broader CAI HubSpot sales lifecycle setup. The full lifecycle flow is:

**Prospect → Lead → MQL → SQL → Opportunity**

The **Lead** stage transition (Prospect → Lead) was confirmed working. The **Opportunity** stage has a confirmed two-way sync with deal creation — see [[wiki/clients/citrus-america/hubspot-sales-workflow]] for details.

The **"Are you already juicing?"** field is also the basis for the BANT qualification framework. See [[wiki/knowledge/hubspot/bant-scoring-simplification]] for the simplified scoring rules (Budget/Authority/Need = 3, Timing = 3 or 4).

## Action Items

| Owner | Task | Status |
|---|---|---|
| Karly Oykhman | Relink MQL→SQL workflow trigger to correct field | Pending |
| Karly Oykhman | Export and map existing data from "You juicing currently?" to "Are you already juicing?" | Pending |
| Miriam Framson | Re-test lifecycle stage transitions after fix is deployed | Pending |

## Related Articles

- [[wiki/clients/citrus-america/hubspot-sales-workflow]]
- [[wiki/knowledge/hubspot/bant-scoring-simplification]]
- [[wiki/knowledge/hubspot/lead-source-field-consolidation]]
- [[wiki/clients/citrus-america/_index]]