Esta página solo está disponible en inglés.

Moving from HubSpot to PanLuma

How the move works

PanLuma copies your HubSpot data across and keeps it up to date, so your team can run both systems side by side and switch HubSpot off when you’re ready. The sync is one-way: data flows from HubSpot into PanLuma, and nothing is ever written back to HubSpot.

The move has five stages:

  1. Prepare. Create a HubSpot Service Key and make sure your team is set up in PanLuma.
  2. Connect. Add the key in PanLuma, check who owns what, and turn the sync on.
  3. First import. PanLuma copies everything HubSpot holds.
  4. Parallel run. Your team keeps working in HubSpot. Every change they make there arrives in PanLuma within about 15 minutes. PanLuma sends nothing on its own during this time, so no customer is emailed twice.
  5. Cutover. You switch each sequence, workflow, scheduled email, social post, booking page and form over to PanLuma, then press Stop sync. From then on PanLuma is your system of record, and you can switch HubSpot off.

While the sync is on, HubSpot is the source of truth. If someone edits a record in PanLuma and HubSpot later changes the same field, PanLuma keeps your team’s edit and flags the clash for you to review.

Before you start

You need a HubSpot Service Key with the right read permissions, and your team’s PanLuma accounts active before the first import. Both take a few minutes and save rework later.

In HubSpot: create a Service Key

In HubSpot, go to Settings → Integrations → Service Keys and create a key. PanLuma only reads, so every scope it needs ends in .read (or is a read-only feature scope).

These scopes are required. PanLuma refuses a key without them and names the ones missing:

ScopeWhat it reads
crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.readContacts, companies, deals
crm.objects.quotes.read, crm.objects.line_items.read, crm.objects.products.readQuotes, deal line items, products
crm.objects.owners.readWho owns each record
crm.schemas.contacts.read, crm.schemas.companies.read, crm.schemas.deals.readCustom properties
settings.currencies.readYour portal’s currency
files.readAttachments on notes, calls and emails

These scopes are optional. Add the ones for what you use in HubSpot. Without one, everything else still syncs and PanLuma tells you which part it skipped:

ScopeWhat it reads
crm.objects.leads.readLeads
marketing.campaigns.readCampaigns and their members
crm.objects.marketing_events.readMarketing events (webinars, conferences)
crm.lists.readLists, and who is in each workflow
contentMarketing emails and their stats
automationWorkflows
automation.sequences.readSequences and enrollments
formsForms and their submissions
socialSocial posts
scheduler.meetings.meeting-link.readMeeting scheduling pages
crm.objects.tickets.read, conversations.readTickets and their conversation threads
cms.knowledge_base.articles.read, cms.knowledge_base.settings.readKnowledge base articles
crm.objects.orders.read, crm.objects.invoices.read, crm.objects.commercepayments.read, crm.pipelines.orders.readCommerce Hub orders, invoices and payments

Keep the key somewhere safe. You paste it into PanLuma once.

In PanLuma: set up your team first

  • You need to be a PanLuma tenant admin to connect HubSpot and manage the sync.
  • Invite your team, and make sure they accept. PanLuma gives each record to the PanLuma user whose email matches its HubSpot owner, but only users who have accepted their invitation are matched. Anyone still showing Invite pending can be mapped later, but it is easiest to have everyone active first.
  • Set a default owner for imported records. Records whose HubSpot owner has no PanLuma user go to this person.
  • Check your selling company. PanLuma needs to know which of your companies won a deal. With exactly one company set up, it is used automatically. With none or several, deals already Won in HubSpot are skipped until this is sorted.
  • Add a sell price list in your HubSpot portal’s currency (prices excluding tax) if you want product prices to come across.
  • For the cutover later: each person who will send sequence emails needs their mailbox connected in PanLuma, and each host of a booking page needs their calendar connected.

Step 1 — Connect HubSpot

You add the key once in Data import, then turn the sync on from the HubSpot page. Nothing imports until you have checked who owns what.

  1. Go to Admin → Data import and open the HubSpot card. Paste your Service Key and press Connect. If a required scope is missing, PanLuma names it; add it in HubSpot and try again.
  2. Go to Admin → Integrations → HubSpot. The connection card shows your HubSpot portal, the last four characters of the key, and that the sync is off.
  3. Press Turn on sync. Choose how far back to import closed deals (the default is the last 30 days, or choose all history). This window only applies to closed deals. Every company, contact, product and open deal comes across whatever its age.
  4. Check the owners before the first import starts. PanLuma reads your HubSpot owners and matches each one to an active PanLuma user by email. Open HubSpot owners and read each row:
    • Matched by email — done.
    • Invite pending — the person hasn’t accepted their PanLuma invitation yet. Once they do, they match automatically.
    • Not mapped — pick the right PanLuma user, or leave it and their records go to your default owner.
  5. When the owners look right, start the first import.
  6. If you use HubSpot leads or tickets, check the Lead stages map and the tickets’ Pipeline stages map on the same page, so each HubSpot stage lands on the right PanLuma stage or status. Deal pipelines and stages need no map: they are created exactly as they are in HubSpot.

Got a mapping wrong? Change it on the same page, and PanLuma offers to apply the correction to the records it has already imported. It leaves alone anything a person has changed in PanLuma since.

Optional: Data import also has Pull from HubSpot, a one-off migration you can review file by file before importing. You don’t need it to use the sync. If you do run it first, the sync recognises those records and updates them rather than creating duplicates.

Step 2 — The first import

The first import copies every live record of every object your key can read, in chunks, in the background. You can close the page; it carries on.

The First import card shows progress per object, and each row under What follows HubSpot reads how many records were imported and how many were skipped, with the reason. Sync history lists every run, and every created, skipped or failed record with its reason.

In HubSpotLands in PanLuma as
CompaniesOrganizations
Contacts (incl. their other companies, with association labels)Contacts
Deal pipelines, stages and deals (with line items)Pipeline pipelines, stages and deals
ProductsProducts (price onto your sell list in the portal currency)
QuotesQuotations in Sales
Notes, calls, meetings, tasks, logged emails, SMS, WhatsApp and LinkedIn messages, with attachmentsActivities on the contact, company or deal timeline
LeadsContacts on your lead funnel, at the mapped stage
Campaigns and members; marketing eventsCampaigns; event campaigns with registered / attended / cancelled members
Custom propertiesCustom fields, once you map them
Email subscription types and opt-outsSubscription types and suppressions — nobody who unsubscribed in HubSpot is emailed
ListsSegments (static, or dynamic where every filter translates)
Marketing emails, with per-recipient statsMarketing emails: sent ones as history, unsent ones as drafts
Workflows (contact-based)Marketing workflows, switched off, with each contact’s position
Sequences and enrollmentsSequences, paused, with each contact’s progress
Forms and past submissionsMarketing forms, unpublished; submissions on the contacts
Social postsSocial posts
Meeting scheduling pagesBooking pages, switched off
Tickets, threads and knowledge baseSupport tickets, messages and KB articles
Commerce Hub ordersSales-order history

A few things are skipped on purpose and named in sync history, for example a company with no name, a contact with neither a name nor an email, or a Won deal while PanLuma doesn’t know your selling company.

To check everything arrived, compare each count on the HubSpot page with HubSpot’s own totals. Any gap should be explained by a skip reason or a missing optional scope.

Step 3 — Run both systems side by side

During the parallel run your team works in HubSpot as usual, and PanLuma follows. Use this time to get the team comfortable in PanLuma before anything switches over.

What follows HubSpot. PanLuma checks HubSpot every 15 minutes; press Sync now to check straight away. New records, edits, stage moves, deletes and merges all come across:

  • A record deleted in HubSpot is archived in PanLuma: hidden from lists, restorable. If someone had edited it in PanLuma, it is kept and marked “Deleted in HubSpot”.
  • When HubSpot merges two records, PanLuma keeps one and folds the other into it.
  • A quote follows HubSpot until someone acts on it in PanLuma (sends, edits or decides it). From then on it is PanLuma’s.

What happens when both systems change the same field. If someone edits a field in PanLuma and HubSpot later changes it too, PanLuma keeps your team’s edit. The record shows a notice naming the field, and the record is listed under Changes PanLuma kept on the HubSpot page. Press Keep PanLuma’s version to dismiss it. To take HubSpot’s value instead, type it into the field. Fields nobody touched in PanLuma keep following HubSpot.

What PanLuma doesn’t do yet. Nothing PanLuma imports sends anything on its own:

  • Sequences, workflows, booking pages and forms come in switched off.
  • Scheduled marketing emails and social posts are held at HubSpot’s planned time, and can’t be scheduled in PanLuma.
  • Imported tickets send no emails and start no SLA clocks.
  • Lead follow-up reminders stay quiet, because your reps are still working those leads in HubSpot.

That is what keeps a customer from hearing from you twice.

Things to do during the parallel run:

  • Have reps open their contacts and deals in PanLuma and check they own the right records.
  • Connect each sender’s mailbox and each booking-page host’s calendar.
  • Write the email body for each automated sequence step that still has contacts to reach. HubSpot doesn’t share template bodies, so these steps arrive empty.
  • Open each imported workflow and fill in anything it flags, such as which board a “create task” step uses.
  • Read the review notes on each imported booking page, such as a time zone to confirm.

Step 4 — Cut over

Cutover is done item by item: for each thing that sends or publishes, you stop it in HubSpot, then switch it on in PanLuma. The HubSpot page lists everything still held in HubSpot, grouped by module, with a count and a link to each item, so you can work down it and see what’s left.

We recommend rehearsing once before the real day.

WhatWho can switch it overIn HubSpot firstThen in PanLuma
SequencesPipeline adminStop the sequence (unenroll or pause everyone)Open the sequence and press Continue in PanLuma. The preview lists each contact’s next step and when it will go out. Each contact carries on from where HubSpot left them, no earlier than HubSpot would have sent the next step. Paused contacts stay paused. If anyone has no sender, pick one. Several sequences can be continued at once.
WorkflowsMarketing adminSwitch the workflow offOpen the workflow and press Review switch-over. PanLuma checks with HubSpot that it is off, shows who will continue and where, then turns it on. Several can be switched at once.
Social postsMarketing adminDelete or unschedule any post still scheduledOn Social Posts, press Take over HubSpot’s posts. A post still scheduled in HubSpot can’t be picked. The rest are scheduled in PanLuma at HubSpot’s time.
Scheduled marketing emailsMarketing adminUnschedule the emailTake it over from the Marketing Emails list. PanLuma checks HubSpot no longer has it scheduled, then schedules it at HubSpot’s time or one you choose.
Booking pagesContacts & Organizations adminTurn off the meeting linkOn Scheduling Pages, read each page’s review notes, then turn the pages on. A host with no calendar connected stays switched off.
FormsThe form’s editor—Publish the form, copy the new embed snippet from Distribute, and replace the HubSpot embed on your website.
Open invoices (Commerce Hub)Tenant admin—Re-run the HubSpot migration in Data import. Invoices are not followed during the parallel run, so your books are opened once, at cutover.

Two things to know:

  • Stop sync is not the switch for these. Stopping the sync stops PanLuma reading HubSpot, but it doesn’t release anything held. Anything you haven’t switched over stays switched off in PanLuma.
  • PanLuma never re-sends what HubSpot already sent. Where it can’t tell whether HubSpot ran a step, it treats the step as done: a skipped step can be fixed, a double send can’t.

Step 5 — Stop the sync and switch HubSpot off

Pressing Stop sync is the moment PanLuma becomes your system of record. Every imported record stays, and HubSpot changes stop arriving.

  1. On the HubSpot page, check the list of items still held in HubSpot. Ideally it is empty. Anything left there stays switched off in PanLuma after you stop.
  2. Press Sync now once more so PanLuma holds HubSpot’s latest state.
  3. Press Stop sync and confirm. The confirmation lists anything still held.
  4. The page now reads that PanLuma is the source of truth. No further sync runs appear in the history.

Before you cancel your HubSpot subscription:

  • Compare record counts on the HubSpot page with HubSpot’s own totals, and read the skip reasons for any gap.
  • Check the notes on each module for anything that didn’t carry: sequence steps PanLuma couldn’t map, workflow steps listed as not carried over, filters a segment couldn’t translate, and booking-page review notes.
  • Confirm HubSpot has no sequences, workflows, scheduled emails, social posts, meeting links or form embeds still running.
  • Export anything from HubSpot that PanLuma has no home for (see below).

The Service Key stays stored in Data import after you stop. Turning the sync back on resumes where it left off. To remove the key entirely, erase it in Data import.

Limitations and FAQ

What doesn’t come across? HubSpot doesn’t make some things readable with a Service Key: sales email templates, and the bodies of sequence email templates. A few HubSpot objects have no PanLuma home yet, such as Projects, landing pages, sales documents and chat conversations that never became tickets; export those from HubSpot. Within workflows, time windows, blocked dates and goals are listed on the workflow as not carried over.

Can my team work in PanLuma during the parallel run? Yes. Their edits are kept, never overwritten by HubSpot. Just remember HubSpot is still the source of truth, so new records should still be created in HubSpot until cutover.

Does anything go back to HubSpot? No. The sync only reads.

Someone changed a record’s owner in HubSpot. Does PanLuma follow? For activities and open quotes, yes. For contacts, companies and deals, no: ownership is set once at import. Change it in PanLuma if needed.

A deal stage’s probability or Won/Lost type is wrong. Deal pipelines follow HubSpot exactly while the sync is on, so fix the stage in HubSpot and it comes across on the next check.

What about GDPR deletions in HubSpot? A record erased in HubSpot is archived in PanLuma within a day.

How long does the first import take? It depends on the size of your portal and HubSpot’s API limits. If HubSpot’s daily limit is reached, the page says so and the sync resumes the next day.

Can we start again from scratch? Yes. A Fresh Start in Admin wipes the imported records but keeps the connection and your mappings, and the next check re-imports everything.

Who do I contact? Your PanLuma onboarding contact, or support@panluma.ai.