search
How to Move Applications Between Vacancies

Last Updated:

Product Area Workday Integration
Sync Direction Workday → Beamery (WD → BM)
Prerequisites WD pull enabled
Fix Type Forward fix — applies from point of enablement only

Support for Moving Applications Between Vacancies

This article describes an improvement to how Beamery handles Workday applications that are moved between vacancies. Previously, a moved application would appear as a new, duplicate application in Beamery. With this fix, Beamery correctly identifies and moves the existing application, keeping your CRM data clean and accurate.

A single application in Workday can be moved between multiple Vacancies. Moving forward, when this happens, Beamery will reference the Application ID to ensure the application is not duplicated on the contact profile. 

When a move is detected, Beamery will:

  • Update the existing application to point to the new vacancy,  rather than creating a new application.
  • Retain all existing application data (stages, notes, and other fields) on the moved record.
  • For bidirectional customers: push updates to the correct, current vacancy in Workday.
  • Eliminate duplicate applications, improving the accuracy of reporting.

This is a forward fix. Beamery will correctly handle application moves from the point of enablement onwards. We are unable to retrospectively correct historic data created before enablement.

This feature is enabled via Beamery's phased roll out process. No action is required from customers to trigger the move logic, it activates automatically once your tenant has been included in the roll out wave.

  • You will receive direct communication from Beamery when your tenant is being enabled.
  • There is no historical sync associated with this feature.

Find information on the relevant testing scenarios here