Consolidating HR from two systems into one — without losing a record.

Two HR systems, one missing source of truth.

Like many growing organizations, TCP had layered on HR tools over time. WorkBright held the onboarding workflows and the historical document packets — I-9s, E-Verify records, and the forms that come with each new hire. Zoho People was already in the building, partially configured, and clearly intended to be the long-term home for HR operations. It just wasn't there yet.

That left the HR team doing double work: checking two systems to answer one question, maintaining two sets of records, and relying on memory to reconcile the gaps. Clearance expirations were tracked in spreadsheets. PTO was governed by policy documents that did not fully match what either system could enforce. None of this was unusual. All of it was slowing the team down.

Consolidate to one platform — carefully.

The goal was to make Zoho People the single, authoritative home for HR at TCP, and to do it without losing a record, misfiling a document, or surprising anyone mid-onboarding. That meant migrating active employees, archiving former ones in a read-only form, rebuilding onboarding workflows inside Zoho, standing up proper clearance tracking, and configuring PTO to match TCP's actual policies — including the distinction between support staff and missionaries, and the July 1 fiscal-year reset.

Equally important: the engagement had to have a clear scope and a clear end. HR migrations can sprawl. This one was priced as a fixed-fee SOW precisely so that everyone knew what was in and what was out from day one.

Engineering discipline, applied to HR operations.

I treat a migration the way I'd treat a data migration in production software: map the source, prove you can read it, prove you can write to the destination, migrate a small slice first, validate, then move the rest. The tooling is different — HR platforms rather than databases — but the habits are the same.

1. Review & preparation

   Reviewed existing onboarding workflows through client-provided Loom walkthroughs and direct inspection of both WorkBright and Zoho People. Confirmed the employee group structure: support staff, missionaries, and contractors each have slightly different rules.

2. Zoho configuration

   Stood up onboarding end-to-end inside Zoho: invitation, form completion, HR approval and rejection flows, secure document storage on each profile, and role-based visibility so employees see only what they should while HR and admins see everything.

3. Pilot migration

   Migrated a small pilot cohort first, validated it with TCP's HR administrators, and adjusted before touching the remaining records.

4. Full migration & validation

   Migrated the remaining active profiles, converted former-employee records to read-only archives, attached historical onboarding and HR documents to each profile, and walked the HR team through the result before signing off.

What was in scope — and what wasn't.

Migrations go off the rails when scope is fuzzy. The SOW named five areas of work, and I'll list what was inside each of them as honestly as I can. Anything not on this list was explicitly out of scope and priced separately if it came up.

In scope

• Onboarding workflows rebuilt in Zoho: invitation, forms, HR approval or rejection, document storage with role-based visibility.
• Employee & document migration for approximately fifty active profiles, plus read-only archives for former employees.
• Clearance tracking: clearance types, status and expiration dates, automated reminders to employees, HR visibility into outstanding or expired clearances — tracked prospectively going forward.
• PTO configuration matched to TCP's handbook: support-staff vs. missionary distinctions, fiscal-year reset on July 1, accrual and carryover rules — enforced prospectively.
• Pilot & validation: a small pilot onboarding, followed by a structured walkthrough with TCP's HR administrators before handoff.

Explicitly out of scope

The rule I held myself to: if material complexity appears — missing records, undocumented workflows, extensive manual reconstruction — pause the work and propose a scope adjustment before continuing. No one likes a surprise invoice, least of all me.

The technology involved.

Tool selection was largely set before I arrived — TCP had already decided on Zoho People as the long-term platform. My job was to make it earn that decision.

Two to four weeks, billed plainly.

Timeline depended on access, validation turnaround on the client's side, and the volume of active hiring happening during the window. The commercial structure was intentionally simple.

One system. One source of truth.

At the end of the engagement, TCP's HR team had a single platform to open in the morning. Active employees lived in Zoho with their documents attached. Former employees lived there too, as read-only archives, which meant historical record requests stopped requiring a second login. Onboarding a new hire ran through one workflow with defined approval steps. Clearances had expirations, and expirations sent reminders on their own.

None of that sounds dramatic written out. That is the point. Good migrations are quiet. The right outcome is that HR stops thinking about the system and gets back to thinking about people.

• One HR platform instead of two, with clear primary-of-record.
• Onboarding flows end-to-end in Zoho with HR approval gates.
• Clearance tracking with automated employee reminders and HR visibility.
• PTO policies configured to match the handbook, including the July 1 reset.
• Documented, transferable configuration — the “lottery metric” satisfied.

What this says about how I work.

A few principles guided this engagement that apply to every small-business IT project I take on. If you are considering a migration of your own — HR, CRM, file systems, email, anything — these are the commitments you can expect.

Scope is written down. Changes pause the work.

Every project has a fixed, named scope before any billable work begins. If we discover something material mid-project, I stop, write up the change, and wait for a decision. You are never surprised by an invoice.

Pilot before you migrate.

Moving all fifty employees in one pass is how migrations fail. Moving two, validating, and then moving the rest is how they succeed. This adds days, not weeks — and it prevents the category of problem that makes a migration feel like a gamble.

A single point of contact on each side.

On TCP's end, Jillian was the named point of contact and Greg had final sign-off. On my end, you talk to me. That structure keeps decisions crisp and response times short.

Financial data is not my lane.

I do not store or process payment or donation data, full stop. That work belongs with the platforms built for it — Virtuous, in TCP's case — and I coordinate around those boundaries rather than crossing them.