Keep HubSpot for marketing and use Lightfield for sales
Lightfield
The short version
Yes, you can keep HubSpot for marketing and use Lightfield for sales. HubSpot Marketing Hub keeps running your marketing while your sales team works in Lightfield.
Lightfield is an agentic CRM. It captures every customer interaction, organizes that history so agents can work from it, and gives agents the tools to do consistent, good work.
The real question is how the two systems connect. Before anything moves, your team agrees which contacts, companies, deals, and fields sync, which system owns each field, and who maintains the connection. We think those choices are much easier to make before the first record moves than after.
What each system does in this setup
HubSpot Marketing Hub stays where your marketing runs. Lightfield is where sales works. It records and transcribes calls, and its records update from the calls, emails, and meetings it captures.
What syncs from HubSpot to Lightfield
A one-way setup brings HubSpot records into Lightfield. It matches each record by its HubSpot ID and copies only the fields you choose. It creates and updates records, and nothing more.
| Item | One-way setup | Two-way sync |
|---|---|---|
Companies | HubSpot companies create and update Lightfield accounts | You define reverse updates explicitly |
Contacts | HubSpot contacts create and update Lightfield contacts | You define reverse updates and consent handling explicitly |
Deals | HubSpot deals create and update Lightfield opportunities | You define which sales outcomes go back to HubSpot |
Lifecycle stage | Needs an agreed field mapping | You define what each stage means and which system controls each change |
Lead source | Needs an agreed field mapping | You keep the source values and agree overwrite rules |
Deletes and merges | Not included | Needs separate design and testing |
Blank values | Not copied | Agree how clearing a value should work |
Campaigns, marketing activity, subscription consent, list membership | Not established | Don’t assume them without explicit scope and testing |
In HubSpot, a workflow you configure sends each qualifying record to Lightfield. You set up one HubSpot workflow and one Lightfield automation for each record type you sync. You also need rules for qualification, field mapping, ownership, and how a seller is routed or notified. This setup doesn’t promise a full copy of historical activity or a sync of every property.
Event triggers only pick up changes made after the workflow is turned on. To bring over records that already exist, enroll them in the workflow by hand, and start with a small group.
What goes back to HubSpot
The one-way setup doesn’t send sales results back to HubSpot. If you need that, a reverse integration is scoped for the outputs you agree on, such as deal stage, amount, close date, or customer status. Those are examples of things to define, not a list of what a standard connector includes. Two-way sync is always a separately scoped integration.
Consent and unsubscribe status
Moving a record between systems must not reset marketing eligibility. Consent and unsubscribe status need their own rules in your design.
What you need before you start
- Lightfield: An owner or admin role, since only they can create automations, and a plan that includes automations. Automations are on Pro and above.
- HubSpot: Access to workflows on HubSpot Data Hub Professional or Enterprise, which the Custom code action requires. Check HubSpot’s current requirements on the day you start.
- A test record: One HubSpot record you can safely test with.
What your team maintains
Someone on your team owns the field and stage mappings, the source-of-truth rules, the health of the connection, sync failures, conflicts, and consent behavior. If you don’t build a reverse sync, sales outcomes need another route back to HubSpot.
Moving sales data to Lightfield
Your core CRM records and the fields we agree on can move to Lightfield. We can also scope notes, attachments, and historical conversations, but they may need to be exported separately from your companies, contacts, and deals. Before you switch off the old system, we agree what’s included, how it will appear in Lightfield, and what should stay in an archive. Connecting a mailbox and importing an old CRM are separate steps.
You can also run Lightfield alongside your existing CRM in a phased rollout. Before the overlap starts, we define which records and fields sync, which system owns each field, how conflicts are handled, and what has to be true before cutover.
Try it yourself
We wrote this page, so test it on your own data. Run these requests in both HubSpot and Lightfield, using your own customer history. Compare the answers, how much retyping each one took, and how long setup took:
- Which open deals have had no email or meeting in the last 14 days?
- Summarize the last three conversations with this account.
- Draft a follow-up to the most recent meeting on this deal.
- Which deals have a close date that conflicts with what was said on the last call?
- Which people on this account haven’t we spoken to yet?
Who this fits
This setup fits a team that runs marketing in HubSpot Marketing Hub, wants sales to work from Lightfield, and has someone who can own the field mappings and the connection.
It doesn’t fit a team that wants one product to run both marketing and sales. Lightfield doesn’t replace every hub, and it doesn’t claim to replace every marketing automation workflow on day one. A team in that position should keep HubSpot for marketing.
FAQ
Can we keep HubSpot for marketing and use Lightfield for sales?
Yes. We agree which contacts, companies, deals, and fields move between the systems. A one-way setup brings HubSpot records into Lightfield, and two-way sync is a separately scoped integration.
What syncs between HubSpot and Lightfield?
In the one-way setup, HubSpot companies, contacts, and deals create and update Lightfield accounts, contacts, and opportunities. Lifecycle stage and lead source need an agreed field mapping. Deletes and merges aren’t included.
Do sales results go back to HubSpot?
Not in the one-way setup. A reverse integration is scoped for the outputs you agree on, such as deal stage, amount, close date, or customer status.
Is the integration built in, or custom?
It’s a documented workflow-based setup, plus customer-specific integrations for two-way needs. We don’t claim a turnkey native connector for every Marketing Hub configuration.
What does the setup require?
A Lightfield owner or admin on a plan that includes automations, and HubSpot workflow access on Data Hub Professional or Enterprise. Check HubSpot’s current requirements before you start.
Will my existing HubSpot records sync?
Only after you enroll them in the HubSpot workflow by hand. Event triggers pick up changes made after the workflow is on.
What happens to marketing consent when records move?
Moving a record between systems must not reset marketing eligibility. Consent and unsubscribe status need their own rules.
Does Lightfield replace every HubSpot hub?
No. Lightfield doesn’t replace every hub, and it doesn’t claim to replace every marketing automation workflow on day one. Keep HubSpot for marketing if you need that.
How long do we run both systems?
There’s no fixed number of days. We define the records and fields in scope, which system owns each field, how conflicts are handled, and what has to be true before cutover.
Next step
Book a demo to scope what would sync for your team.
