Freshteam connector

Get your Freshteam data out of Freshteam before the lights go off.

Freshworks announced in early 2026 that Freshteam stops renewing on March 7, 2026, with existing customers running on the remainder of their contracts. Data Panda pulls your Freshteam candidates, jobs, employees, time-off and onboarding records into your warehouse, so the history that took years to build does not leave the building with the licence.

About Freshteam

Freshworks' HR and ATS product, now on the way out.

Freshteam was the HR and applicant tracking product inside Freshworks Inc. (NASDAQ: FRSH), the Chennai-founded software company that also runs Freshdesk, Freshsales and Freshservice. The product covered the lifecycle a small or mid-market HR team typically asks one tool to handle: posting jobs to boards like Indeed, LinkedIn and Glassdoor, moving candidates through hiring stages, onboarding new hires, holding the employee directory, departments, branches and teams, and running time-off requests and balances.

In 2022 Freshworks stopped selling Freshteam standalone and folded the product under Freshservice for Business Teams. In early 2026 the company confirmed the full sunset: renewals stop on March 7, 2026, existing customers keep access through the end of their current contract, and an extended one-year renewal window for contracts expiring before March 7, 2026 lets some tenants reach into April 2027. The official line is that the move has no material business impact. For the customers running real recruiting pipelines, employee records and onboarding workflows in there, the impact is concrete: pick a successor, and get the data out cleanly before the tenant closes.

This connector is built for that exit. It pulls the Freshteam REST API objects (candidates, job postings, candidate sources, new hires, employees with their custom fields, departments, sub-departments, branches, business units, teams, levels, roles, time-off types and time-off requests) into your warehouse, where they can be archived, reported on and replayed into whichever HRIS or ATS you migrate to next.

What your Freshteam data is for

What you get once Freshteam is connected.

HR and recruiting reporting

Headcount, hiring funnel, source effectiveness and time-off on one page, in a place you control after Freshteam closes.

Active headcount and FTE per department, branch and business unit, with the joiners and leavers of the period
Hiring funnel from posted job to offer accepted, per recruiter, role and source
Time-off balances and approved absences across teams, mapped onto delivery capacity

Migration and process automation

Replay Freshteam events into your next HRIS or ATS, while the existing tenant runs out the clock.

Mirror new candidates and stage moves into the successor ATS during the parallel run
Push hired candidates into the new HRIS as new-hire records on the day they sign
Provision identity and SaaS access from the migrated employee record, not from Freshteam

AI workflows on the historical record

Put the years of Freshteam hiring history behind AI that does not need a live tenant to answer.

Source-of-hire scoring on five years of candidate-source, stage-progress and offer outcomes
Talent-pool resurfacing: matching old archived candidates to today's open requisitions
Natural-language Q&A on the archived employee, candidate and time-off record

Custom apps on your data

Lightweight tools on the migrated record so the people who used Freshteam every day still have a workbench when it is gone.

Recruiter workbench reading from the warehouse instead of the closing Freshteam tenant
Manager view of team headcount, time-off and open roles after the migration
Audit-trail viewer for old hiring decisions, kept available beyond the contract end date

Use cases

Use cases we deliver with Freshteam data.

A list of concrete reports, automations and AI features we have built on Freshteam data. Pick the one that matches your situation.

Sunset data archiveFull Freshteam record snapshotted into your warehouse before the contract end date, queryable forever after.

Hiring funnel historyPosted-to-offered conversion per stage, role and recruiter across the years the tenant ran.

Source-of-hire effectivenessCost and quality per candidate source (Indeed, LinkedIn, referrals, agencies) over the full hiring history.

Time-to-hire by role familyDays from job posted to offer accepted, per role family and hiring manager, across cohorts.

Headcount and FTE reportingActive employees per department, branch and business unit, with joiner and leaver counts per period.

Time-off balances and patternsApproved time-off per type and team, with balance carry-over and absence concentration named.

Onboarding completion trackingNew-hire onboarding workflow progress per cohort, with the steps that consistently slip surfaced.

Talent pool resurfacingArchived candidates re-matched to today's open roles based on tags, sources and prior stages reached.

Recruiter workloadOpen requisitions, candidates in pipeline and offers out per recruiter, across the active hiring window.

Migration parallel runSide-by-side state of Freshteam and the successor ATS during the cutover, with diffs flagged.

Custom-field preservationFreshteam custom fields on candidates and employees mapped and kept in the archive, not lost in the move.

Audit trail beyond the tenantOld hiring decisions, offer history and onboarding outcomes still readable after the Freshteam licence ends.

Real business questions

Answers you will finally get.

Where will five years of Freshteam hiring history live once the contract ends?

Candidates, applications, stage moves, offers, sources and onboarding records all snapshotted into your warehouse before the tenant closes, with custom fields preserved. The HR lead can still answer 'who applied for the Antwerp role in 2023, what stage did they reach, and which source brought them in' two years after Freshteam is gone, instead of losing that history with the licence.

Which sources and recruiters delivered hires over the lifetime of our Freshteam tenant?

Source-of-hire conversion plotted per channel (Indeed, LinkedIn, agencies, referrals, careers site) and per recruiter, across every job we ever posted in Freshteam. The talent acquisition lead picks the channels and partners that deserve renewed budget in the successor ATS, instead of starting from a blank slate after migration.

Are we ready to migrate, and is the parallel run staying clean?

Side-by-side counts of candidates, jobs, employees and time-off records in Freshteam and in the successor system during the cutover window, with the diffs named per object type. The migration owner sees the day a stage move stopped propagating to the new ATS, instead of finding the gap in week three of the new system going live.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Headcount and FTE per legal entity from the Freshteam record, lined up with payroll cost and the headcount plan, kept in your warehouse after the tenant closes. Group close stops needing a live Freshteam login to confirm the personnel-cost line, because the source data already sits next to the GL.

For sales leaders

Open seller roles, ramp dates and territory assignments from the last weeks of the Freshteam tenant, replayed into the new HRIS so quota coverage does not break in the middle of a quarter. Sales leadership sees when the migration window risks losing a hired AE start date, before the forecast call surfaces it.

For operations

Hiring funnel, time-off and onboarding throughput in one capacity picture across the migration. The COO sees which office is letting joiner records drift past day-thirty during the cutover, and where the absence concentration falls in the weeks the team is short on Freshteam expertise.

Ideas

What you can automate with Freshteam.

Pair with HiBob

Migrate Freshteam employees and onboarding into HiBob

The Freshteam employee register, departments, branches, business units, teams, levels and custom fields land in the warehouse, mapped to the equivalent HiBob (Bob) shape, and replay as new worker, site and department records in Bob during the cutover. Onboarding workflows in flight at the time of switch keep moving in Bob with the stage they were already in, rather than restarting from scratch. The people lead sees a clean side-by-side count per object type, so the migration goes live on a known reconciliation, not a hopeful one.

Pair with Slack

Drive joiner and leaver Slack moments off the warehouse, not Freshteam directly

While the migration runs, joiner and leaver events flow from the warehouse (which holds both the Freshteam record and the successor HRIS record) into Slack rather than directly off Freshteam, so the welcome message and the access-revoke ping keep firing on day one regardless of which system the record lives in this week. People ops stops running a manual handoff queue across HR and IT through the cutover.

Pair with HubSpot

Match HubSpot recruitment-marketing campaigns to Freshteam source-of-hire

HubSpot careers-site visits, employer-brand campaigns and recruitment-newsletter performance lined up against the Freshteam candidate-source field, stage progress and final hire outcome over the full tenant lifetime. Talent acquisition sees which campaigns produced applicants that reached the offer stage, not just clicks, and uses that read to budget the equivalent campaigns in the successor ATS instead of guessing.

Pair with Salesforce

Reconcile Salesforce seat plan against the Freshteam-staffed sales org

Active sellers, hire dates and ramp windows from the Freshteam employee record (and from the successor HRIS once the migration is in flight) joined to Salesforce user assignments, territories and quotas. Revenue operations sees the AE roles that hired in Freshteam but never made it into Salesforce as a user, and the Salesforce seats still active for people who left the company before the tenant cutover.

Pair with monday.com

Drive monday.com onboarding boards off the warehouse Freshteam record

New-hire records and onboarding workflow steps from Freshteam land on the monday.com onboarding board for the receiving manager, with the same checklist items the Freshteam workflow held. After the migration the same board reads from the successor HRIS instead, with no change at the manager's end. The receiving team does not feel the system change, only the people lead does.

Pair with Exact Online

Tie Freshteam headcount to Exact Online payroll and personnel cost

Active headcount and FTE per legal entity from the Freshteam employee record joined to the personnel-cost lines in Exact Online, with joiners and leavers per period and the cost variance against the headcount plan. Group finance sees the entity where two leaver records closed in March but the payroll line did not yet drop, before the next monthly close runs.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Freshteam data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Freshteam to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Freshteam connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

When exactly does Freshteam stop, and what does that mean for our data?

Freshworks stops renewing Freshteam contracts on March 7, 2026. Existing customers keep access through the end of their current term, and a one-year renewal extension is available for contracts expiring before that date, which can carry access into April 2027. After the term closes the tenant is gone. The point of this connector is to land the Freshteam record in your warehouse before that date, so the candidate, hire and onboarding history outlives the licence.

Which Freshteam objects land in the warehouse?

Through the Freshteam REST API the connector pulls Employees with their custom fields, Departments, Sub-departments, Branches, Business Units, Teams, Levels and Roles on the org-chart side, and Job Postings, Candidate Sources, New Hires and Time-off requests with their types and policies on the people-flow side. Authentication runs through a Freshteam API token scoped to your tenant. Custom fields on candidates and employees are preserved in the archive.

What if we have not picked the successor HRIS or ATS yet?

The warehouse archive is independent of the successor choice. We pull Freshteam into the warehouse first; the migration into HiBob, BambooHR, Workday, Personio or whichever tool you land on can run against that archive on its own timeline. That removes the pressure to pick fast and migrate fast in the same window, which is the combination that loses data.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Freshteam setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors