Recruitment CRM & ATS · Sales Hub

Manatal to HubSpot

Cloud applicant tracking system and recruitment CRM with an Open API.

In short

Manatal data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (Organizations (Clients/Departments) and Contacts (client contacts)); 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-14 weeks for a large one.

Last reviewed 2026-10-29 · Also relevant to Marketing, Service, Data hubs · 8 sources

1 · Checklist

Migration checklist for Manatal

Three phases, specific to this system. Tick steps off as you go.

0 of 15 steps doneTick steps off as you go. Your progress stays in this browser.

Before

0 of 5 done

During

0 of 5 done

After

0 of 5 done
2 · Cost

What 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.

How many records?
Custom objects?
Automation to rebuild?
History to bring?

A planning aid built from the three scenarios below. It is not a quote.

The three scenarios

low complexity

Small migration

2-4 weeks

Up to 5k candidates and 200 clients

CSV-based import.

medium complexity

Mid migration

4-8 weeks

5k-50k candidates and 1k clients

API extraction and a custom-object decision.

high complexity

Large migration

8-14 weeks

50k+ candidates, multiple teams

Partial replacement with parallel running.

What moves the number

Candidate volume and number of attachmentsCandidate and job data-model designWhether Open API is available (plan-dependent)Association rebuild between candidates and jobsPipeline and automation rebuildDuration of parallel running with Manatal

Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.

3 · Where to begin

Access, mapping and limits

Start with how data leaves Manatal: what you need to get in, what lands in HubSpot, and what will not.

API

REST (Open API v3)

Credentials needed

An Open API token generated by an Administrator.

Admin permission

Admin is needed to generate tokens and to run exports.

Choose your route

How will you move the data?

No native connector was found.

  • You need: An Open API token generated by an Administrator.
  • Permission: Admin is needed to generate tokens and to run exports.

Native imports often bring over only some data, so check coverage per object in the mapping below.

Where each object lands

yes movespartialmanualno

In Manatal

In HubSpot

Contacts
Companies
Deals
Custom objects
Files
Notes
Select an object

Hover or tap anything on the left to see where it lands.

What to expect

ATS resume parsing and AI candidate recommendations

These are Manatal product features with no HubSpot equivalent. Only the resulting data moves.

Job-board and career-page distribution

HubSpot has no ATS multiposting. Keep Manatal or another tool for this.

4 · Governance

Data governance and compliance

Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.

0 of 5 agreed
Method

How we researched this page

How much to trust each section, and where it comes from.

InsufficientPartialVerified

Export paths and Open API access are backed by Manatal docs. The HubSpot object mapping, rate limits, certifications and residency are not sourced. The mapping is category-level analyst knowledge. No Manatal-specific HubSpot connector was found.

Sources

Related migrations

Quick answers

Frequently asked questions

How do I migrate Manatal to HubSpot?

1. Confirm the Manatal plan and ask support to enable Open API if the API route is wanted. 2. Run a UTC-aware export test of Candidates, Jobs, Organizations and Contacts as an Admin. 3. Choose the candidate data model (Contacts vs Custom object) and the job model (Deals vs Custom object). 4. Decide whether Manatal stays live for parsing and job-board posting during a partial replacement.

What data can move from Manatal to HubSpot?

These objects move directly: Organizations (Clients/Departments) and Contacts (client contacts). Check the mapping table for partial and manual items.

What does not move from Manatal to HubSpot?

ATS resume parsing and AI candidate recommendations and Job-board and career-page distribution. Plan to rebuild or retire these.

How long does a Manatal to HubSpot migration take?

Small (Up to 5k candidates and 200 clients): 2-4 weeks. Mid (5k-50k candidates and 1k clients): 4-8 weeks. Large (50k+ candidates, multiple teams): 8-14 weeks. These are planning estimates, not a quote.

What access do I need to export from Manatal?

An Open API token generated by an Administrator. Admin is needed to generate tokens and to run exports.

What compliance issues apply when moving Manatal data?

Check: Candidate data may include sensitive information such as diversity data or right-to-work documents, Salary data and Possible minors in internship or graduate hiring. Agree consent, retention and access rules before exporting.

Talk to a partner

Moving Manatal 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
Talk to a partner