Microsoft Copilot Studio to HubSpot
Low-code platform for building conversational agents. Agents are stored as Dataverse components inside Power Platform environments.
Microsoft Copilot Studio data can move into HubSpot, landing mainly in Agent Hub. 0 of 5 mapped objects move directly; 3 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 Microsoft Copilot Studio
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 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-2 agents, under 10k transcripts
Mid migration
3-10 agents, 10k-100k transcripts
Large migration
10+ agents, over 100k transcripts, many connectors
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 Microsoft Copilot Studio: what you need to get in, what lands in HubSpot, and what will not.
Dataverse tables (bot, botcomponent, conversationtranscript) and solution export
Maker or admin access to the Power Platform environment holding the agent.
At least the System Customizer security role to export or import agent solutions.
Choose your route
How will you move the data?
No native connector was found.
- You need: Maker or admin access to the Power Platform environment holding the agent.
- Permission: At least the System Customizer security role to export or import agent solutions.
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.
- Solution export of the agent as a zip (unmanaged solutions only)
- Download conversation transcripts from Copilot Studio or Power Apps as CSV or ZIP
- Azure Synapse Link for Dataverse to Azure Data Lake Storage Gen2 for long-term transcript retention
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 Microsoft Copilot Studio
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Agent instructions and topics | Custom objects | manual | Solution export is Dataverse-to-Dataverse only. Instructions and topics must be re-authored in HubSpot Agent (Customer Agent). |
| Knowledge sources | Files | manual | Re-add source documents and URLs in HubSpot. SharePoint knowledge answers are not captured in transcripts. |
| Tools, actions and flows | Custom objects | manual | Rebuild as HubSpot agent tools or workflows. Connector references and environment variable secrets are not transferred. |
| Conversation transcripts | Notes | partial | Transcript JSON can be exported as CSV and loaded as Notes on Contacts, but only if retention was extended. Default retention is short. |
| Evaluation cases | Custom objects | manual | Recreate test sets as reference material. HubSpot has no equivalent import in the sources reviewed. |
What to expect
Not portable. Only transcripts are exportable.
Not included in agent export.
Environment variable secret values are not exported.
Different model, behavior and platform constraints.
Handoff routing is platform-specific.
Connection references are not carried over.
Extend Dataverse retention or export via Synapse Link before cutover.
Confirm which environments log transcripts before relying on them.
Ask an admin to enable it, or raise a support ticket.
Run side-by-side evaluation on a fixed test set.
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.
Export/import paths and transcript handling are backed by Microsoft docs (S1-S5). I found no HubSpot-side docs or connector for Copilot Studio, so the HubSpot mapping rests on analyst category-level knowledge. API and rate-limit details were not verified.
Sources
Related migrations
Frequently asked questions
How do I migrate Microsoft Copilot Studio to HubSpot?
1. Inventory agents, topics, knowledge sources and flows in each Power Platform environment. 2. Confirm the System Customizer role or equivalent for the exporter. 3. Extend ConversationTranscript retention or set up Azure Synapse Link to ADLS Gen2. 4. Export the agent solution (unmanaged) as a reference archive.
What does not move from Microsoft Copilot Studio to HubSpot?
Runtime state and conversation variables, Topic-level and node-level comments and Secrets and connection references. Plan to rebuild or retire these.
How long does a Microsoft Copilot Studio to HubSpot migration take?
Small (1-2 agents, under 10k transcripts): 2-4 weeks. Mid (3-10 agents, 10k-100k transcripts): 4-8 weeks. Large (10+ agents, over 100k transcripts, many connectors): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Microsoft Copilot Studio?
Maker or admin access to the Power Platform environment holding the agent. At least the System Customizer security role to export or import agent solutions.
What compliance issues apply when moving Microsoft Copilot Studio data?
Check: Chat transcripts may contain health, financial or minors' data depending on the use case.. Agree consent, retention and access rules before exporting.
Moving Microsoft Copilot Studio 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