Sync job changes to your CRM

When Starbridge identifies a job change, you get two things: a contact — the person who changed jobs — and a signal — the event itself. We recommend syncing both. Contacts sync to your CRM Contact object to keep your contact data current. Signals can be consumed directly in the Starbridge feed, or synced into a dedicated custom object in your CRM for automated workflows, task creation, and reporting.

​

Why separate contacts from signals

Contacts represent current state — who someone is, where they work, what their title is today. Signals are immutable historical events — the fact that someone changed roles on a specific date never changes, even as the contact’s current state evolves. Keeping them separate means your Contact records stay accurate and up to date, while your job change records preserve the full history of career transitions across your accounts.

​

Choose your path

There are two ways to consume job change signals. Most teams start with Path 1 and graduate to Path 2 as their workflows mature. Regardless of which path you choose, always sync contacts to your CRM Contact object first. The steps below cover contacts first, then the two paths for signals.

​

Step 1: Sync contacts to your CRM

Before syncing job change signals, make sure every person in your Job Changes Bridge exists as a contact in your CRM. This ensures that when job change records are created, the contact lookup resolves correctly. Follow the full guide at Sync contacts to your CRM.

​

Path 1: Starbridge feed

In this path, job change signals stay in Starbridge. Reps review them in their feed and email digest, and take action manually — creating leads or tasks in your CRM when relevant. This path requires no additional CRM setup beyond syncing contacts. How to set up a review workflow for your team:

• Reps log into Starbridge and review their feed, or read their email digest
• When a relevant signal surfaces, reps create a task or lead in your CRM manually
• Reps use Starbridge’s built-in status flags (Actioned, Starred, Not interested) to track what they’ve reviewed

When to consider moving to Path 2:

• Your team has clear patterns of which signal types always require action
• You want automated task creation or routing rather than manual triage
• You need job change data in CRM reports and dashboards

​

Path 2: Custom object

In this path, job change signals sync into a dedicated custom object in your CRM. Each signal becomes its own record, associated to the contact and account, giving you a full history of transitions and a foundation for automated workflows.

​

Why a custom object

Syncing job changes to a custom object — rather than as fields on the Contact or Account — keeps your data model clean:

• History-preserving — each job change is a separate record, so a contact can have multiple job changes over time without losing prior context
• Reporting-friendly — easy to answer questions like “Which accounts lost a key contact in the last 90 days?” or “How many new hires joined ICP accounts this quarter?”
• Clean separation — contacts hold current state; the custom object holds the historical event record

​

Video walkthrough

Watch a full video walkthrough at Starbridge University.

​

Before you start: create the custom object in your CRM

Create a custom object called Job Change (or Signal: Job Change) with the following fields: Relationship fields:

• Contact (Lookup → Contact) — the person who changed jobs
• Account (Lookup → Account) — the account associated with the contact

Core fields:

• Job Change Type (Picklist) — New Joiner, Title Change, or Departure
• Effective Date (Date) — when the job change takes effect
• Announced Date (Date) — when the job change was announced
• Summary (Long Text) — description of the job change
• Current Title (Text) — the person’s current title
• Previous Title (Text) — their previous title, for title changes

Deduplication field:

• Job Change ID (External ID, Text) — Starbridge’s unique identifier for each job change event. Mark this as an External ID to enable upsert operations and prevent duplicate records.

Optional prioritization fields:

• Account ICP? (Checkbox)
• Contact Champion? (Checkbox)

​

Set up the sync

​

Set up CRM automations

Once job changes are syncing to your CRM, configure automations to route signals to the right people automatically. New hires and promotions at ICP accounts Trigger when a new Job Change record is created where Type = “New Joiner” or “Title Change”, the account is an ICP account, and the current title matches your target decision-maker roles. Action: create a Task assigned to the Account Owner or SDR/BDR owner, due 7 days from the effective date, with the job change summary and a link to the CRM record. Departing champions Trigger when a new Job Change record is created where Type = “Departure”, the account is a customer account, and the contact is marked as Executive Sponsor, Champion, or Primary Contact. Action: create an urgent Task assigned to the CSM or AM owner, due immediately or before the effective date, flagging the retention risk and prompting them to identify a replacement champion. Champions moving to new accounts Trigger when a new Job Change record is created where Type = “New Joiner”, the account is an ICP account, and the contact is marked as Champion or Executive Sponsor in your CRM from their previous company. Action: create a Task assigned to the AE or Account Owner, due 3 days from the effective date, noting the warm intro opportunity and linking to the previous account record.

​

Reporting

With job changes as a dedicated object, you can build reports like:

• Champions who moved to ICP accounts in the last quarter
• Accounts that lost key contacts in the last 90 days
• New hires at target accounts by title and month
• Job change volume by type over time

​

Alternative: CRMs without custom object support

If your CRM plan doesn’t support custom objects, you can add two custom fields directly to the Contact object instead:

• Started Date (Date) — when the contact started at this employer
• Ended Date (Date) — when the contact left

Map Effective Date to Started Date for new joiners, and to Ended Date for departures. Build automations that trigger on updates to these fields.

​

Next steps