Skip to content

← HubSpot CRM

New to HubSpot?

HubSpot Onboarding.

Set HubSpot up properly from the start. We plan the portal, move your data, build the first workflows and train your team.

  • Top 27 HubSpot expert on Upwork
  • 100+ clients
  • 16 countries
  • 12 industries
  • 100% Upwork Job Success

Where you're starting from

Three ways teams come to us.

  1. 01

    Starting with HubSpot

    You've bought HubSpot, or you're about to. You want it set up around how you sell before anyone starts entering data.

  2. 02

    Moving from another CRM

    Your contacts and deals live in a tool such as ActiveCampaign or Zoho. You need it moved across without disrupting sales.

  3. 03

    Adding a hub

    You already use HubSpot for marketing or sales and want to bring in another team, such as sales or service, without breaking what works.

One HubSpot portal

Already running HubSpot, but it isn't working for you? Start with a review instead. HubSpot Portal Audit

Why a specialist

Guidance, or the work itself.

HubSpot's own onboarding shows your team how to set the portal up. The decisions and the build are still yours: how your data is structured, how it moves across, how leads are routed and how each team is trained. That is the part we do with you.

Outcome Setting it up yourself With AI Digital
Avoid rebuilding later Settings get decided one at a time, as questions come up One plan for properties, pipelines and lifecycle stages before the build
Bring your data across cleanly Data is imported first and cleaned up later Data mapped, tested on a sample and checked before go-live
Workflows that fit how you sell Workflows are copied from templates, not from your process Workflows built from how your team actually sells, tested with real scenarios
Get people using it Training stops at how the software works Training on your own portal, plus written documentation of what was built and why

You can use both: HubSpot's onboarding for learning the product, and us for planning and building your portal.

How it works

A call first. Then clear, paid work.

HubSpot's own onboarding runs 60 to 90 days for one hub. We usually finish in about a month. For large teams we plan about six weeks, to get the details right.

  1. 01

    First call

    In 30 minutes, tell us how your team sells and markets today, and what you want HubSpot to do.

    You getWhether onboarding is the right step, and which hubs it should cover.

  2. 02

    Plan and quote

    We map your process, data, tools and priorities, then agree the scope, price and timeline before any paid work starts.

    You getA written plan, price and timeline to approve.

  3. 03

    Set up and migrate

    We configure the portal, test the data move on a sample, then move the rest and check real scenarios with your team.

  4. 04

    Train and hand over

    Your team learns the portal in live calls, with recordings and documentation of what was built and why.

    You getA trained team and written documentation.

Onboarding at a glance

First call, before any paid work
30 min
Typical timeline; about 6 weeks for large teams
About 1 month

Scope

What onboarding can include.

We scope each onboarding to the hubs you use and how your team works.

"It was great working with Dalibor: very responsive, dedicated and careful. He submitted his work with detailed explanation and notes."ecomDNA, Hong Kong
  • Portal setup and configuration
  • Data migration from your current tools
  • Properties, pipelines and lifecycle stages
  • Your first workflows and lead routing
  • Forms, email templates and website connection
  • Integrations with your other tools
  • Reports and dashboards
  • Team training and documentation

Marketing, Sales, Service, Data (formerly Operations) and Content Hub. See what we do in each hub

Moving from another tool

A migration is more than an import.

Most migration problems come from copying the old setup as it is. We move everything HubSpot supports, and agree with you how each field maps before anything moves. The price depends on your account, the scope and how many automations need rebuilding.

  1. 01Your current toolActiveCampaign, Zoho, Keap, WordPress
  2. 02Field map agreed
  3. 03Sample test
  4. 04Cutover checks
  5. Checked at each stage
  6. HubSpot
  • CRMs such as ActiveCampaign, Zoho and Keap (formerly Infusionsoft)
  • Websites from WordPress to HubSpot CMS
  • Contacts, companies, deals, notes, email history and lists
  • Automations rebuilt as HubSpot workflows
  • Field mapping agreed before anything moves
  • A test migration on a sample first
  • Cutover and rollback checks agreed before the switch
  • Your team keeps using the old tool until HubSpot is ready, unless you need to switch it off earlier, for example to save on its cost

Handover

A team that can run it without us.

We train each team (marketing, sales, service) on the parts they'll use every day, in your own portal. You also get written notes on how the properties, workflows and reports work, so later changes don't depend on us.

Training comes as live calls, recordings and written documents.

Want us to stay on? We offer ongoing HubSpot support.

Clients & brands

Trusted by teams at

View all clients →

Your next step

Tell us what HubSpot should do for you.

Let's talk.

Tell us what you need help with. A sentence or two is enough.

We use these details only to reply to your inquiry, as explained in the privacy policy.

Your message comes straight to us.

In 30 minutes we'll cover

  • How your team works today
  • What you want HubSpot to do
  • Which hubs you have or need
  • What data and tools have to move
  • What paid onboarding would cover

Any paid work is agreed with you first.

FAQ

Questions before we start.

Can't see your question? Ask us on a call.

Onboarding covers planning, building and handing over your HubSpot portal, scoped to the hubs you use (Marketing, Sales, Service, Data or Content Hub) and how your team works. A typical scope includes:

  • portal setup: users, teams, permissions, properties, pipelines and lifecycle stages;
  • data migration from your current tools, with the field map agreed and a sample tested first;
  • your first workflows and lead routing;
  • forms, email templates and the connection to your website;
  • integrations with your other tools;
  • reports and dashboards;
  • training for each team in your own portal, plus written documentation of what was built and why.

Everything in your written scope is included, at a fixed price agreed before work starts. Outside it as standard: your HubSpot subscription, which you buy from HubSpot; a new website or theme, which Website Development scopes separately; custom integrations with systems that have no native HubSpot app, and custom CRM cards, which are add-ons; and ongoing admin after handover, which our HubSpot packages cover. If something new comes up mid-project, we quote it before we do it. See what we do in each hub.

The same things decide both: how many hubs we set up, how much data moves and how clean it is, how many integrations need connecting, how many automations from your old tool have to be rebuilt as HubSpot workflows, any custom development, and how many teams need training. On the first call we check whether onboarding is the right step and which hubs it should cover. Then we map your process, data and tools, and you get a written scope with a fixed price and a timeline to approve before any paid work starts. HubSpot's own onboarding runs 60 to 90 days for one hub. We usually finish in about a month, and for large teams we plan about six weeks. The timeline also depends on how quickly your team can review the field map, check the test migration and join training. The pricing page shows what makes a HubSpot project bigger or smaller.

Everything. Whatever your HubSpot subscription can hold, we migrate: contacts, companies and deals with their associations, plus notes, calls, meetings, tasks, logged one-to-one emails, lists, tickets, products and custom objects, along with attachments where your old tool lets us export them. Unsubscribes and consent records move with each contact, and we check them in the test batch. Custom fields become HubSpot properties, and tags become properties, lists or lifecycle stages, whichever fits how you'll use them.

Some data depends on your subscription, for example custom objects need an Enterprise hub. Some has no native place in HubSpot, such as opens and clicks on past campaigns, which can't go into HubSpot's email reports. Where HubSpot can't store something natively, we keep it on the records or build a custom application for it. Automations don't convert one to one, so we rebuild the ones that matter as HubSpot workflows. Before anything moves, we agree the field map with you, including outdated records you'd rather leave behind. See the ActiveCampaign to HubSpot migration.

We have moved teams to HubSpot from CRMs and marketing tools including ActiveCampaign, Salesforce, Pipedrive, Zoho, Apollo and Keap (formerly Infusionsoft). Website moves from WordPress to HubSpot CMS are a separate kind of migration, covering pages, posts, URLs and redirects, and we handle those too. If your tool isn't listed, that doesn't rule it out. What matters is what the tool lets you export, or what its API exposes. Tell us on the first call and we'll check. Whatever the source, the procedure is the same: list what's in the old tool and what's connected to it, map the fields, clean the data, test on a sample, then move the rest. See the ActiveCampaign to HubSpot migration example, platform and connected-system migration and, for websites, content migration and URL continuity.

Yes. Your team keeps using the old tool until HubSpot is ready, unless you need to switch it off earlier, for example to save on its cost. While your team keeps working, we set up the portal and run a test migration on a sample, which you check with us before the full move. Before the switch we agree a cutover plan with a timeline and rollback checks: what must be true before we switch, and how we go back if a check fails. Records created or changed in the old tool after the full migration are covered by that plan, usually with a final top-up import of those changes, or a short pause on edits on switch day. Forms, integrations and workflows are reconnected or rebuilt in HubSpot as part of the move, so less breaks on the day you switch. See platform and connected-system migration.

No. You can talk to us before you buy. On the first call we look at how your team sells and markets today and what you want HubSpot to do, and we tell you which hubs and which subscription level the plan needs, so you buy for what you'll actually use. If you already have a subscription, we check the plan against it. Anything your subscription doesn't support is flagged in the scope, with the upgrade or an alternative, before you approve it.

We do. HubSpot's standard onboarding gives you a specialist who guides your team through the setup. With us, the same team that plans your portal also builds it: properties, pipelines, lifecycle stages, data migration, workflows, forms, integrations and reports. Your part is the decisions only you can make, such as how you sell, who owns which leads and what each stage means, plus the reviews and training described below. A few steps need someone with access to your domain or IT systems, such as adding the DNS records that connect your email-sending domain and website to HubSpot. We send the exact records, or make the change ourselves if you give us access. If you'd rather have your own people build part of the portal, for example to keep the cost down or to learn it, we guide them and check their work. We agree that split in the scope.

Mainly a few sessions and reviews. We need your decisions, not your hands, for the build. Expect to give time at four points:

  • a planning session where we map how you sell and market, your data and your tools;
  • a review of the field map and the cleanup rules before anything moves;
  • a check of the test migration and real scenarios with us before go-live;
  • the live training calls for each team.

Recordings and written guides mean nobody has to remember everything from one session. It helps to name one person on your side who makes decisions, answers our questions and owns the portal after handover. The timeline depends partly on how quickly these reviews happen.

We clean the data before it moves, in the old system or in the import file, so problems don't travel into HubSpot. First we review contacts, companies and deals for duplicates, gaps, invalid values and records nobody uses, and count each type of problem. Then we propose cleanup rules and you approve them before anything changes: which records count as duplicates, which version wins when they merge, what is archived or left behind, and how formats such as names, countries and phone numbers are standardized. HubSpot matches contacts by email address and companies by domain, so we map those keys deliberately and the import updates the right records instead of creating copies. Deals and other records have no built-in match key, so we store the old system's ID on each record and never re-run a full import. After the test batch and the full import, you get before-and-after counts to check against the source. See HubSpot data cleanup.

While we work with the data in your HubSpot portal or your old CRM, we act as your data processor under the GDPR. You stay the controller: we follow your documented instructions, keep the data confidential and never use it for our own purposes. We sign a data processing agreement whenever you ask for one.

In practice:

  • Access. You invite us as users in your own accounts, with only the permissions the project needs, and only the people working on your project use them. We don't hold your passwords. We use strong passwords and two-factor authentication on our side where available. When the project ends, you remove our access.
  • Files. Exports and documents are shared through Google Drive, and only you and the people you name get access. Nothing is sent by plain email or chat.
  • During the move. The field map and a test on a sample come first, so problems show up on the sample, not in the full import. Your old system stays as it is until the switch.
  • If something goes wrong. If a breach affects your data, we tell you without undue delay, so you can meet your own obligations.

How we handle client data is described in our privacy policy, under client work.

Against checks we agree with you in the plan, before any work starts. A good onboarding should leave you with a working portal that people use. It can't promise sales results on its own. We suggest four kinds of check:

  • Data: record counts in HubSpot match the source after the agreed cleanup, and sample records keep their fields, associations and consent status.
  • Processes: test inquiries and deals pass through every form, routing rule and workflow, including edge cases such as existing customers and incomplete forms, and land with the right owner.
  • Integrations and reports: connected tools sync, and the agreed dashboards show the numbers you need.
  • People: each team can do its everyday tasks in the portal after training, and you have written documentation of what was built.

If you also want to judge the portal's effect later, we record a baseline at the start, such as response time to new leads.

You choose. Every onboarding ends with training and written documentation, so your team can run the portal without us. If you want us to stay on, our HubSpot & Automation packages cover the ongoing work month to month, with no minimum term. Depending on the level, that includes admin requests, new and changed workflows, data upkeep, error checks on connected apps, reports, and regular training and review calls. For occasional needs there are add-ons, such as a single team training session or care for a custom integration we built, as well as blocks of extra hours and one-off consulting for a specific question. What each package includes and costs is on the pricing page.