CDBAMImplementation Projects
The project

End-to-end implementation, with a single owner

HR projects usually fail at the seams: discovery belongs to one supplier, migration to another, validation lands on the client and support on a third party. We take the entire line — and we answer for it.

Phase 1

Technical discovery

Before configuring anything, a picture of what exists: processes as they are actually run, real volumes, live integrations and the exceptions nobody documented — which are precisely the ones that blow the schedule.

  • Process mapping across HR and payroll, including what is done manually today and why.
  • Technical inventory: source database, integrations, reports in use and customisations.
  • Risks and exceptions recorded before they become a surprise mid-implementation.
  • A plan with a defensible estimate, scoped by module and by phase.

Discovery delivers value on its own: many clients start there, even before deciding the rest.

Run on our own system

This phase is not run on spreadsheets. We use a system we built ourselves, where the discovery is recorded against a standard script and with a change history.

What the client receives is the outcome: the consolidated discovery document, which becomes the basis of the implementation plan.

Phase 2

Data migration

Employee records, history and payroll history moving from the legacy system to the new platform — whatever that legacy system is. Migrating means establishing correspondence between codes that do not exist in the target, and proving the result checks out.

Any readable source

We migrate from any system whose data can be obtained: database, export, text file or spreadsheet. If the data can be extracted, it can be migrated.

Scope by subject area

Reference tables, contractual data, events, job changes and payroll history — the largest volume in any migration.

Traceability

Every load has its own reconciliation, and at the end the client receives the dictionary explaining where each migrated field came from.

Phase 3

Configuration

The system set up with the company’s actual rules — not the vendor defaults. This is where collective agreements, benefit policies and organisational structure stop being documents and become system behaviour.

Payroll and contributions

Pay elements, calculation formulas, contribution bases and the payroll calendar.

Structure

Org chart, cost centres, legal entities, jobs and salary bands.

Policies

Benefits, eligibility, approval limits and workflow rules.

Integrations

Finance integration with the ERP, time and attendance, and whatever else needs to talk to the system.

Phase 4

Validation of everything delivered

This is the phase that usually gets squeezed — and the one we do not let anyone squeeze. Every task delivered comes with material proving the result, produced with the delivery and not after it.

  • Parallel payroll run: the old and the new system compared, pay element by pay element, until every difference is explained or eliminated.
  • Record checks by targeted sampling, focused on the exceptions mapped during discovery.
  • A test script per module, with the expected result written before execution.
  • Evidence filed separately from the production files.
A working session with metrics presented on screen
Nothing is accepted because it ran without errors. Running without errors is the minimum; what matters is matching what should have come out.
Phase 5

Go-live

The cutover with a plan, a defined window and objective criteria to proceed or roll back. No improvising at 3 a.m.

Cutover plan

Sequence of activities, owners and times, with the decision points marked.

Contingency

What to do if something does not reconcile — decided beforehand, not in the moment.

Training

The internal team ready to operate without depending on anyone else the next day.

Phase 6

Hypercare and advanced support

The period right after go-live is where real operations ask the questions no test anticipates. We stay through the first payroll close — the moment an HR project proves whether it worked or not.

  • Reinforced support through the first payroll cycles, with an agreed response time.
  • Fixes at the root. If the problem is a parameter or a mapping, we correct it there and regenerate — no manual patches that nobody remembers later.
  • Knowledge transfer to the internal team, with a record of what was done.

Already implemented by someone else?

We also serve companies already live that need advanced support, configuration changes, custom reporting or the rescue of a stalled project. You do not need to have started with us.

Talk about support

Where do you stand?

Choosing a system, midway through an implementation, or already live and needing breathing room. Each scenario calls for a different scope.