Salesforce Agentforce to HubSpot
Agent platform on the Salesforce Platform. Agents use topics and actions, are grounded in CRM and Data Cloud data, and run through the Einstein Trust Layer.
Salesforce Agentforce data can move into HubSpot, landing mainly in Agent Hub. 0 of 6 mapped objects move directly; 5 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Salesforce Agentforce
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
1 agent, <100 articles
Knowledge base plus guidelines only.
Mid migration
2-5 agents, 100-1,000 articles
Several rebuilt actions and handoffs.
Large migration
6+ agents, >1,000 articles, many actions
Multiple channels, custom tools and a regulated-data review.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Salesforce Agentforce: what you need to get in, what lands in HubSpot, and what will not.
Salesforce Platform APIs (REST, Metadata) plus an Agent API; agent definitions are Salesforce metadata (specific types unverified)
Salesforce admin or developer user with access to agent setup and metadata; an external client app if the Agent API is used.
Admin rights to Agentforce setup, permission sets and Data 360 (Data Cloud); exact permission names unverified.
Choose your route
How will you move the data?
No native connector was found.
- You need: Salesforce admin or developer user with access to agent setup and metadata; an external client app if the Agent API is used.
- Permission: Admin rights to Agentforce setup, permission sets and Data 360 (Data Cloud); exact permission names unverified.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Retrieve agent and action configuration as metadata (e.g. via the Salesforce CLI); exact metadata types not verified here
- Session Tracing API (beta) returns an OpenTelemetry trace of one session per request, only for sessions started in the last 72 hours
- Data 360 (Data Cloud) stores session tracing data
- Manual copy of instructions, topics and prompt templates
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce Agentforce
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Agent instructions / topics | Custom objects | manual | Rewrite as Customer Agent guidelines and tone in HubSpot's agent setup. HubSpot has no import for Salesforce agent definitions. |
| Knowledge sources (knowledge articles, grounded content) | Files | partial | HubSpot Customer Agent sources can be knowledge base articles, uploaded files (PDF, DOCX, HTML, TXT, CSV, XLS) and public URLs. Export Salesforce articles and re-upload or re-publish them. |
| Agent actions / tool specifications | Custom objects | manual | Rebuild as HubSpot agent tools, workflows or integrations. Salesforce Flow, Apex and prompt template logic does not carry over. |
| Test and evaluation cases | Custom objects | manual | Re-run them in HubSpot's agent testing. HubSpot guidance says to test and rate replies before deploying. |
| Service cases | Tickets | partial | Cases are standard Salesforce CRM data, not Agentforce-specific. Move them with a normal CRM migration; mapping unverified. |
| Session transcripts and traces | Notes | no | Traces are only retrievable for 72 hours after a session starts, and are not designed for import. |
What to expect
Sessions and state are internal to Salesforce and not portable.
HubSpot has no equivalent import. Recreate the controls using HubSpot's own governance settings.
The API only serves recent sessions.
The formats differ.
Salesforce Flow, Apex and prompt templates have no HubSpot equivalent import.
The HubSpot agent is only as accurate as its sources.
Handoff must be recreated in HubSpot.
Salesforce agent users and permission sets do not map to HubSpot.
Replay a saved set of test questions and rate the replies before go-live.
Apply least-privilege CRM permissions to the HubSpot agent.
Use the 28-day free access window to estimate volume.
Audit sources before syncing and avoid sensitive data.
Export traces to a SIEM or archive before cutover.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Governance and HubSpot-side setup are backed by sources. Salesforce export paths, API names, limits and object mapping rest on category-level knowledge, because no Salesforce docs were retrieved. Agentforce is a rebuild, not a data migration.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce Agentforce to HubSpot?
1. Inventory agents, topics, actions and prompt templates in the Salesforce org. 2. List knowledge sources and where they are grounded (knowledge articles, Data 360). 3. Retrieve agent metadata with the CLI for the record, and save the instructions as text. 4. Enable Session Tracing and export representative sessions within the 72-hour window.
What does not move from Salesforce Agentforce to HubSpot?
Runtime state and live conversation sessions, Einstein Trust Layer configuration (masking, audit trail) and Session traces older than 72 hours via the Session Tracing API. Plan to rebuild or retire these.
How long does a Salesforce Agentforce to HubSpot migration take?
Small (1 agent, <100 articles): 2-4 weeks. Mid (2-5 agents, 100-1,000 articles): 4-8 weeks. Large (6+ agents, >1,000 articles, many actions): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce Agentforce?
Salesforce admin or developer user with access to agent setup and metadata; an external client app if the Agent API is used. Admin rights to Agentforce setup, permission sets and Data 360 (Data Cloud); exact permission names unverified.
Is there a native HubSpot connector for Salesforce Agentforce?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Salesforce Agentforce data?
Check: Health records, Financial or account numbers, National identifiers and Possible minors' data in support chats. Agree consent, retention and access rules before exporting.
Moving Salesforce Agentforce into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner