Skip to content
Start free trial

Contacts and the Lifecycle

A Contact is a person you do business with. HARi keeps a single record per person and tracks where they are in your buyer journey via a Lifecycle Stage field. There’s no separate Lead entity to maintain in parallel — you don’t end up with the same person tracked twice.

Every Contact has a lifecycle_stage value drawn from a fixed list. The stage is what HARi uses to decide which views, dashboards, and automations a contact appears in.

StageWhenWhat it means
LeadDefault for new contacts created through intake forms or importsA prospect you haven’t yet qualified — minimal information, no commitment
QualifiedAfter your sales process flags them as worth pursuingActive opportunity territory — they fit the customer profile and have budget/intent
CustomerAfter they sign / pay / convertExisting customer relationship — visible in customer-success views and renewal pipelines
LostWhen the relationship does not continueMarks the contact inactive. The record stays, and it leaves the active lists
ContactA person you work with who is not in a sales stageStays active. Use it for someone who is not a lead and not a customer
Business PartnerA partner rather than a buyerStays active

A company has the same six stages. Default for a freshly created contact is Lead, so a person who arrives from a form starts as a prospect. You move them through stages on the contact, or with a workflow.

The stage field appears in three places by default:

  1. Active Leads view — filtered to Lifecycle Stage IN (Lead, Qualified). Replaces the old /lead workspace; the URL is /contact?view=contacts_leads.
  2. Dashboard chart — pre-built grouping by lifecycle stage so you can see your funnel composition at a glance.
  3. Per-record badge — visible on the contact’s detail page next to their name, colored to match the stage (Lead = amber, Qualified = blue, Customer = green, Lost = red, Contact = indigo, Business Partner = purple).

You can build additional saved views on the Contact entity that filter by stage — e.g. “My Customers” filtered to Lifecycle Stage = Customer AND owner = me, or “Lost prospects to re-approach” filtered to Lifecycle Stage = Lost AND last_activity > 90 days ago.

Workspaces created before April 2026 had a separate lead entity that’s now retired. Existing Lead records aren’t touched automatically — your admin runs a one-shot migration during a maintenance window:

  1. The migration creates a Contact for each active Lead, copying source + description into notes, setting lifecycle_stage = Lead.
  2. If a Lead had a non-zero estimated value AND a linked Contact AND no existing Opportunity on that Contact, the migration also creates an Opportunity at the “Qualification” stage with the Lead’s amount.
  3. The old Lead row is soft-archived but the table stays in place for one quarter as a safety net (full table drop ships in a future release after admins confirm zero reads against it).

Until your admin runs the migration, your old Lead records stay accessible from the Lead workspace exactly as before. The transition is on your timeline, not ours.

  • Companies — still a separate entity. Companies represent organizations; Contacts represent the people inside those organizations who you talk to.
  • Opportunities — still a separate entity. An Opportunity is a deal-in-progress (with stage, amount, close date); a Contact is a person you might have many deals with over time.
  • Owner / Team — every Contact still has an owner and an optional team for permission scoping. Lifecycle Stage is independent of ownership.
  • Lost is the inactive stage. Choosing Lost marks the contact inactive. The other five stages leave the contact active. Use a separate list when you need steps that are not one of these six.
  • Bulk-update lifecycle stage on imports. When you import a list of existing customers, set lifecycle_stage = “Customer” in the CSV — otherwise they all default to “Lead” and your funnel charts misread.
  • Use lifecycle filters in workflow triggers. Instead of “fired on every new contact”, scope to “fired on contacts where Lifecycle Stage changes to Qualified” so onboarding flows don’t fire on every cold lead.