mondayfoundThe scenario
Imagine a small agency managing vacancies across several spreadsheets. Recruiters maintain different status labels, candidates appear twice and client updates depend on whoever last edited a file. This is an illustrative situation, not a reported MondayFound client engagement. The objective is one trustworthy pipeline with a named owner for every active search.
Clean before importing
Choose a small set of stages and document what each stage means. Separate candidate identity from applications: one person can legitimately apply to several roles. Review potential duplicate records rather than merging on a matching name alone. Preserve useful history, but do not bring obsolete columns into the new system simply because they exist.
Move one workflow first
Pilot with a limited group of active vacancies. Reconcile candidate counts, application counts and attachments against the source. Keep the original export available to the authorised migration team, and record corrections. Give recruiters a short daily review of missing owners, overdue actions and records that failed import. Expand only after the pilot is understood.
Evaluate the change
Useful checks include duplicate records requiring review, client reports needing manual edits and active applications without a next action. Set target values after measuring the starting point. The proposed outcome is a reliable shared process; no percentage improvement is claimed here. Retire the old editing workflow once the team has accepted the replacement.