Migration from old time tracking tool to Operating Hours
Step by step instructions for how to test, configure and start using Operating Hours
Written By Matti Parviainen
Last updated 6 months ago
Critical Success Factors:
Thorough planning before touching any data
Parallel operation to ensure nothing is lost during transition
User training to minimize adoption friction
Data validation at every step to ensure accuracy
Timeline Considerations:
Plan for 4-8 weeks depending on data volume and team size
Include buffer time for unexpected issues
Time tracking may be easier to get right than invoice creation
Preparation steps
Pilot test phase: realistic time tracking & invoice creation
Pick a group of ~10 pilot users that are working across 3+ billable projects and track some time on internal projects as well. Use your old system to find who these could be – or use Operating Timeline.
All-company roll-out
The longer you run two systems in parallel, the more likely it is that some reports (manual exports from the old system, for example) are incomplete and cause trouble.
If you find Operating to be less-than-ideal way of tracking time, we provide support exporting the work your pilot group has done so that you can revert back to the old system. At the time of writing (September 2025), this has never happened, but we want you to have a great experience even if you choose not to go with us.
(To be expanded as we learn more.)