Moving from LiquidPlanner to Jira: what happens to your timesheets?
LiquidPlanner Classic officially sunsets on December 31, 2026. After that date (or the end of your contract term, if earlier), access to the product and its stored data will be limited. If your team is heading to Jira, this page maps where each LiquidPlanner Classic capability lands — honestly, including the parts LogMyTime doesn't cover.
What's happening
Tempo, which acquired LiquidPlanner, is retiring the Classic product and recommends migrating to Jira together with its own module suite — Tempo Timesheets, Capacity Planner, Structure PPM, and Financial Manager. That stack is a genuine fit for organizations that used the full breadth of LiquidPlanner: portfolio roadmapping, predictive scheduling, and financial management.
Many teams, though, used LiquidPlanner mainly to track time, review timesheets, and get hours out for payroll or billing. If that's you, adopting a multi-module suite means paying for — and administering — a lot you won't use. LogMyTime covers exactly that workflow inside Jira, for $1 per user/month, free for teams of 10 or fewer.
Where each LiquidPlanner capability lands
| You used in LiquidPlanner Classic | In Jira it becomes |
|---|---|
| Projects and tasks | Jira projects and issues — this is Jira's core, no app needed. |
| Logging time on tasks | LogMyTime's weekly/monthly grid on Jira issues; time logged with Jira's own "Log work" button is picked up automatically. |
| Timesheet review and export | LogMyTime timesheets with submit/approve workflows — approved hours lock, and anything logged afterwards is flagged to both sides. One-click payroll-ready CSV export. |
| Availability, holidays and work schedules | LogMyTime shift patterns (including rotations and overnight shifts), holiday calendars, and per-person schedules that drive required-hours tracking. |
| Predictive scheduling and resource leveling | Not LogMyTime. Jira Plans (Premium) or a dedicated resource-management app — including Tempo Capacity Planner — covers this. |
| Portfolio roadmapping and financials | Not LogMyTime. Jira Plans, Tempo Structure PPM, or Financial Manager are the right tools if you need this depth. |
Which should you pick?
| Your situation | Honest recommendation |
|---|---|
| You need timesheets, approvals, schedules and payroll/billing export | LogMyTime. One plan, $1/user/month, free ≤10 users, 30-day trial. Nothing else to buy or administer. |
| You need portfolio management, cross-project resourcing and financial planning | The Tempo suite (or Jira Premium's Plans) is the fuller fit. LogMyTime doesn't do PPM and won't pretend to. |
| You're not sure yet | Start with Jira + LogMyTime — it's the smallest committed spend that keeps time-tracking continuity — and add planning tools later if you find you miss them. |
One more difference: where your data lives
If the sunset taught your team anything, it's that your records shouldn't be hostage to a vendor's roadmap. LogMyTime runs entirely on Atlassian Forge and carries Atlassian's “Runs on Atlassian” badge: every worklog is stored by Atlassian inside your own Jira site's region, we have no servers and no access to your data, and everything exports to CSV at any time. If you ever leave, the app becomes read-only on lapse — you can still view and export everything. See our privacy policy and security policy.
Migration checklist
- Export from LiquidPlanner Classic before December 31, 2026 — all three exports from their help guides: projects & tasks, collaboration content, and timesheet data (CSV). Do this even if you haven't picked a destination; the data stops being reachable after sunset.
- Set up Jira Cloud and recreate your active projects. (Historical projects can stay in the export archive.)
- Install LogMyTime from the Atlassian Marketplace — free for 30 days, and permanently free for 10 or fewer users.
- Set up teams, approvers and schedules — usually under an hour for a small team; our documentation walks through it.
- Historical timesheets — keep the LiquidPlanner CSV as your archive of record. A supported LiquidPlanner timesheet import is on our roadmap; if you'd like your history inside LogMyTime, email us — early migrators help us shape it and get first access.