Switching to CompetenceFlow
Check the data before you change the way you work.
Move to CompetenceFlow in stages: agree the scope, test your data, connect the required systems and pilot a course workflow with your team.
One checked step at a time.
Agree the scope. Prove the workflow.
1. Map the work you need to carry over
Walk through a typical course and an awkward exception. Decide which records, templates and integrations are needed for the first release.
- Course dates, participants and company buyers.
- Trainer records, certificates and expiry dates.
- Open bookings, billing references and planned messages.
2. Review a trial import
Import a sample into a test environment. Check record counts, required fields, dates and relationships against the source. Resolve duplicates and missing information before agreeing the final migration.
3. Connect and pilot
Test a course from booking through attendance and follow-up. Include the coordinator, trainer and finance team, and check the data passed to connected systems. Add an MCP workflow if your team plans to work in Claude.
4. Agree the go-live plan
Set the cutover date, responsibilities and support arrangements together. Keep a clear record of which system is used for each task during the transition. The schedule depends on your data and agreed scope.
Questions from training providers
How long does implementation take?
The timeline depends on your data quality, workflows and integrations. We agree a schedule after scoping the work, with checkpoints for the trial import and pilot.
Do we have to switch everything at once?
A phased rollout lets you start with an agreed course line or workflow. We plan the transition with you, including how existing bookings and records will be handled.
See it with your own workflow.
Tell us how you run your courses today. We’ll walk through the relevant features together.