Migrate your Intervals data
Web-based time-tracking-first project management tool for small-to-mid teams. It lacks a mobile app and offers fewer collaboration layers than modern alternatives.
In its favor
Why people choose Intervals
The signal that keeps Intervals on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Project-count pricing instead of per-user — every paid plan above Lite includes unlimited users; you pay for active projects, which is unusual in PM SaaS and appealing to billable-hour firms that don't want to count seats.
Increases billable capture per the vendor's own customer data — Intervals cites typical billable-hours lift of 25-30% just from improved time tracking discipline, which justifies the spend for agencies, consultancies, and law firms.
Built specifically for billing-heavy workflows — per-task budget tracking, milestone date management, integrated invoicing, and consistent CSV/PDF exports cover the operational basics of professional services without extra tools.
20+ years of operation by Pelago and 5,000+ paying companies — Intervals has been continuously running since well before most modern PM tools, providing platform stability that startup-stage PM SaaS cannot match.
Documented public REST API with 30-day free trial — Intervals publishes API documentation at www.myintervals.com/api/ and offers a true trial without credit card, lowering evaluation friction.
No native mobile app — all time entry and task work must happen in a desktop browser, which rules out field-based or travel-heavy teams.
Dated UI compared to Asana, Monday, ClickUp or Hive — the vendor has publicly acknowledged the interface needs modernization but a new UI has been promised rather than delivered.
Limited collaboration depth — task comments and milestone notes exist but the platform has no real-time collaboration layer, @mentions, or rich document editing.
No bulk document export — documents must be downloaded individually from each task, which makes migration off the platform painful for any account with significant file attachments.
Access-level roles are limited to admin/member, with no separate project-manager, executive, or client-portal role tiers, frustrating larger or more hierarchical organizations.
Reasons to switch
Why people leave Intervals
The recurring reasons buyers give for replacing Intervals. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Intervals fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Intervals pricing overview
Intervals uses an unusual active-project-based pricing model where every paid tier (except Lite) includes unlimited users. Lite is $29/month with 3 users and 3 active projects. Basic is $49/month with unlimited users and 10 active projects. Not so Basic is $69/month, Professional is $99/month for 30 projects, Premium is $149/month, Top Shelf is $199/month, and Unlimited is $259/month. Annual billing offers a 20% discount, and a 14-day (some sources cite 30-day) free trial requires no credit card. 'Active project' is defined as in-progress — completed projects set to inactive do not count against the monthly cap.
Lite
Tier 1 of 7
$29/month
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Intervals's schedule — see our quote-based pricing →
What gets migrated
Intervals object support
Object-by-object support for Intervals migrations. Per-pair details surface during scoping.
Clients
Fully supportedClients are the top-level organizational units in Intervals. The schema is flat — a client name, status, and contact references — and maps cleanly to most destination CRM or PM platforms' account/client objects.
People
Fully supportedPeople are user accounts with timesheet permissions and roles. We migrate People as team members, preserving their assigned access level and whether they are active or inactive.
Projects
Fully supportedProjects belong to Clients and contain Tasks and Milestones. The Project object carries budget, start/end dates, and status. We preserve project-to-client ownership during migration.
Milestones
Fully supportedMilestones are date-driven checkpoints within a Project. Each Milestone has optional comments. We preserve the milestone sequence and target dates, and re-link them to their parent Project in the destination.
Tasks
Fully supportedTasks belong to Projects and optionally to Milestones. Each Task has its own comments. We preserve task ordering, status, assignees (People), and estimated vs. actual hours. Task-to-Milestone linkage is explicitly carried forward.
Task Comments
Mapping requiredTask-level comments are threaded text entries attached to Tasks. Most destination platforms store these as activity notes or discussion threads — we map them to the equivalent comment/note object and flag any formatting differences in the scoping call.
Milestone Comments
Mapping requiredLike Task Comments, Milestone Comments are threaded entries tied to Milestones. We apply the same comment-to-note mapping logic used for Task Comments.
Project Notes
Mapping requiredProject Notes are standalone text entries scoped to a Project but not tied to Tasks or Milestones. We map these to the destination project's notes or description field.
Custom Activity Fields
Mapping requiredCustom activity fields are user-defined properties attached to activities (time entries). These vary per account — we enumerate all active custom fields during the discovery phase and map each to a corresponding custom field in the destination.
Time Entries
Fully supportedTime entries are the primary data object in Intervals. Each entry records hours, a date, task association, and billable status. We preserve all entries chronologically and re-link them to their target Task records.
Documents
Not in this platformIntervals stores attachments as documents, but the platform explicitly states that documents cannot be bulk exported — only individually downloaded. We flag this as a manual-step gap and do not attempt bulk document migration.
| Object | Support | Notes |
|---|---|---|
| Clients | Fully supported | Clients are the top-level organizational units in Intervals. The schema is flat — a client name, status, and contact references — and maps cleanly to most destination CRM or PM platforms' account/client objects. |
| People | Fully supported | People are user accounts with timesheet permissions and roles. We migrate People as team members, preserving their assigned access level and whether they are active or inactive. |
| Projects | Fully supported | Projects belong to Clients and contain Tasks and Milestones. The Project object carries budget, start/end dates, and status. We preserve project-to-client ownership during migration. |
| Milestones | Fully supported | Milestones are date-driven checkpoints within a Project. Each Milestone has optional comments. We preserve the milestone sequence and target dates, and re-link them to their parent Project in the destination. |
| Tasks | Fully supported | Tasks belong to Projects and optionally to Milestones. Each Task has its own comments. We preserve task ordering, status, assignees (People), and estimated vs. actual hours. Task-to-Milestone linkage is explicitly carried forward. |
| Task Comments | Mapping required | Task-level comments are threaded text entries attached to Tasks. Most destination platforms store these as activity notes or discussion threads — we map them to the equivalent comment/note object and flag any formatting differences in the scoping call. |
| Milestone Comments | Mapping required | Like Task Comments, Milestone Comments are threaded entries tied to Milestones. We apply the same comment-to-note mapping logic used for Task Comments. |
| Project Notes | Mapping required | Project Notes are standalone text entries scoped to a Project but not tied to Tasks or Milestones. We map these to the destination project's notes or description field. |
| Custom Activity Fields | Mapping required | Custom activity fields are user-defined properties attached to activities (time entries). These vary per account — we enumerate all active custom fields during the discovery phase and map each to a corresponding custom field in the destination. |
| Time Entries | Fully supported | Time entries are the primary data object in Intervals. Each entry records hours, a date, task association, and billable status. We preserve all entries chronologically and re-link them to their target Task records. |
| Documents | Not in this platform | Intervals stores attachments as documents, but the platform explicitly states that documents cannot be bulk exported — only individually downloaded. We flag this as a manual-step gap and do not attempt bulk document migration. |
Gotchas
What to watch for in Intervals migrations
Issues we've hit on past Intervals migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No bulk document export in Intervals
Custom activity fields are account-specific and require enumeration
No native bulk-import format for inter-object relationships
| Severity | Issue |
|---|---|
| High | No bulk document export in Intervals |
| Medium | Custom activity fields are account-specific and require enumeration |
| Medium | No native bulk-import format for inter-object relationships |
Leaving Intervals?
Where Intervals customers move next
5 destinations Intervals can migrate to.
How a Intervals migration works
Four steps, Intervals-specific
Connect
API key (documented at www.myintervals.com/api/) into Intervals. Scopes limited to read-only on the data we move.
Map
We translate Intervals-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Intervals quirks before production.
Migrate
Full migration with Intervals rate-limit handling. Rollback available throughout.
FAQ
Intervals migration FAQ
Answers to the questions buyers ask most during Intervals migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Intervals migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Intervals.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Intervals setup and destination — written quote back within a business day.