The three moments

Passing job changes and transfers from HR to the service desk and applications

A mover integration passes a new job, department or manager from the HR system on on the effective date: a change ticket for access and equipment in TOPdesk, ServiceNow or Freshservice, and the new manager or team in Simplicate, HubSpot and Slack. KoppelHet builds this from Visma Raet YouForce, Nmbrs, AFAS and Workday, among others.

What it is

The mover is the moment most often forgotten. For joiners and leavers everyone knows something has to happen; on a job change IT often does not hear about it, and old access, old teams and old approval routes stay in place.

HR often records a change weeks in advance, with an effective date. If it goes through too early, approvals already run through the new manager. If it does not go through, everything stays as it was.

How the integration handles it

  • A new job or department produces a change ticket, with the new job and the effective date. The service desk then knows when access and equipment must change, not just that they change.
  • Workday records changes with an effective date. KoppelHet only delivers a new department or manager to ServiceNow on that date, so approvals stay with the current manager until then.
  • On a Change Job in Workday KoppelHet submits a service request to Freshservice, so IT sees the job change.
  • If a unit in AFAS changes manager, KoppelHet sets the new manager for every employee of that unit in Simplicate.
  • If someone moves from sales to a job without HubSpot, the manager gets a handover list and the seat is released on the effective date of the new job.
  • After a reorganisation in Workday KoppelHet updates the membership of the user groups in Slack.

Edge cases we handle

  • A change of operating company gives a contract with a different company in Nmbrs. For the service desk that is a change, not a departure.
  • A change of legal entity in Personio is not a departure. KoppelHet submits a request for what differs per entity, such as the email domain.
  • Not every change belongs with the service desk. It does not need an address change, it does need a job change; the organisation decides which changes produce a ticket.
  • A job change that keeps old access for a transition period.

What KoppelHet does

In the design KoppelHet records which HR changes count as a move and which system has to respond. The effective date from HR leads: whatever is recorded in advance only goes through on that day. Expect two to four weeks to go-live.

Common integrations

Customer case

Gemeente Geertruidenberg logo

Gemeente Geertruidenberg

Public sector

Gemeente Geertruidenberg has Visma Raet YouForce create calls in TOPdesk automatically. Four weeks before a start date there is an onboarding call, a week before a departure an offboarding call, and a change call when someone gets a new role or department.

Read the customer story

Frequently asked questions

Which changes produce a ticket?

The organisation decides. By default a new job, department or team; an address change usually not.

What if the change only takes effect in a month?

Then the effective date is in the ticket, and the new department and manager only go to systems such as ServiceNow on that date.

How is this different from movers in IAM?

IAM handles accounts, groups and licences in Entra ID and Active Directory. This integration handles what has to happen outside them: tickets, teams, managers and seats in other systems.

More on Joiner, mover, leaver

Joiner, mover, leaver: the overview

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.