Finance or ERP system migration

A finance system migration has a lot in common with an HR one: a business case, a vendor, data to move, processes that change, a period of testing against the old system, and a cutover date tied to the calendar. HRjects was built for the HR version. This page is plain about how much of it applies to Finance.

What you would use

Create a project from the General project template. It has four phases, Plan, Design, Build, Launch, each ending in a gate with exit criteria. Workstreams are Planning, Design, Delivery and Communications. There is no finance-specific template.

What carries over

Workspace	Use in a finance migration
Business case	Current yearly cost against each option, with payback in months and three-year net, and the sponsor's decision recorded
Roadmap and gates	Exit criteria you write, such as "Chart of accounts mapping approved by the Controller". Ticking records who and when
Tasks	A board by status, filtered by workstream and team
Process maps	Current and future steps for processes such as month-end close, purchase to pay and expense approval, with gaps turned into tasks
Issues	Defects from testing and problems after cutover, with severity and owner
Go-live readiness	A weighted checklist with a Go or No-go at 90% and no open critical issues

What is not relevant, and one thing that is missing

The HR-specific pieces are not part of the General template: the parallel payroll tracker, the HR workstreams and the HR process library.

Finance migrations often include a parallel close, where a period is closed in both systems and the results are compared. HRjects has no tracker for that. You can cover it with readiness checklist items of your own, such as "Parallel close for September reconciled and signed by the Controller", and give them heavy weights. That records the outcome and who ticked it. It does not check a variance for you the way the payroll tracker does.

A sensible setup

1. Plan. Build the business case. Add exit criteria for budget approval and for agreeing the cutover period.
2. Design. Map the close, purchase to pay and reporting processes. Log gaps: a missing approval rule, a report that has no equivalent, an integration with the bank or the payroll system.
3. Build. Track configuration, data migration and integration work on the board. Mark tasks Blocked when they wait on a third party, so they show on the Overview.
4. Launch. Use the readiness checklist for parallel close results, user testing, training, cutover plan approval and a named support owner.

Keep financial records out

HRjects stores project information: plans, tasks, process steps, checklists and issue descriptions. It is not a place for ledgers, bank details or vendor records. Describe issues without account numbers.

Where another tool is the better choice

HRjects is new and narrow. It has no Gantt chart, task dependencies, file attachments or integrations today. If your migration has hundreds of dependent tasks, or your auditors expect evidence files attached to each control, a general project tool will serve you better. See the comparison pages.

It is a reasonable fit for a smaller migration where the main needs are recorded sign-offs, mapped process changes and a clear cutover decision.

Next steps

Read how gates work, or start a free project and try the General template with example data.