(02) MIGRATION
Moving from spreadsheets or another planner? We bring the past over so the forecast starts honest.
DURATION
2 to 3 weeks
FORMAT
Remote, with a named lead
PRICE
From $900
BEST FOR
Teams leaving another planner
(01) OVERVIEW
What this
really covers.
A forecast is only as honest as the history behind it. If that history stays in an old tool, Tuna starts blind.
We clean and map your past plans, then bring them across with the slips and date changes intact, so the first forecast already knows how your team really ships.
Why history matters
Every team has a pattern. Some slip at handovers, some in review, some in the last week before a freeze. Tuna learns that pattern from past work, and the more of it it can read, the sooner its forecast is worth trusting.
Old plans are rarely tidy. Fields mean different things in different teams, dates were moved without notes, and some projects were never closed. Cleaning that up is most of the work, and it is the part we take on.
No leap of faith
Both systems run side by side for one cycle, so nobody has to trust the switch on faith. When the cycle ends, you compare the two and decide. Most teams switch early.
01
Spreadsheet import
Spreadsheets and exports brought in without retyping.
02
History cleanup
Duplicates, dead projects and orphan tasks cleared out.
03
Field mapping
Old fields matched to Tuna's, signed off by your team.
04
Parallel run
Both tools live for one full cycle before the switch.
(03) HOW WE WORK
Close to your team,
from day one.
We begin with an audit. A named lead goes through your old plans with one person from your side and agrees what comes across, what gets archived and what can be left behind.
Then we map fields in a shared sheet you can check line by line. Nothing is imported until you have signed that sheet off.
The import itself takes an afternoon. The parallel run that follows is where trust is built.
THE CHALLENGE
Tidepool had planned in a heavily customised tool for three years. Fields meant different things in different teams, and a third of the projects had never been closed.
Leaving that history behind would have meant a forecast with no memory of how the team really ships.
THE OUTCOME
Every live project and three years of history came across in a fortnight, with dates and slips intact. The first forecast already knew that reviews were where Tidepool usually lost time.
Both tools ran side by side for one cycle. The team switched a week early, because the new numbers matched what they saw on the floor.
(05) HOW IT RUNS
Three steps, then you run it.
1
We audit the old plans and agree what comes across.
2
We clean, map and import the history.
3
We run both tools for one cycle, then switch.
IN PRACTICE
Field mapping is agreed in a shared sheet before anything moves.
