Migrate from Intervals to Microsoft Project

Intervals Clients are top-level organizational containers carrying a name, status, and contact references. In MS Project desktop, clients map to a naming convention prefix on the Project name (e.g., ClientName_ProjectName). In Project Online, Clients map to a SharePoint site collection or a custom Enterprise Project Type that we configure before migration. Client-level contact information migrates as a custom Text field on the MS Project task or as a Project-level custom field.

Intervals People records (user accounts with timesheet permissions, access levels, and active/inactive status) map to MS Project Resources. We map the Person name to Resource Name, their email to the Resource Initials or email field, and their active/inactive status to the Resource Active flag. MS Project has no native timesheet approval workflow; if the customer requires approval chains, we document the current Intervals timesheet approval configuration for rebuild in Project Online's Timesheet features or Power Automate.

Intervals Projects (carrying budget, start/end dates, status, and a Client ownership reference) map directly to an MS Project file (MPP) or a Project Online Project. Project name, start date, finish date, and status migrate as-is. Budget information maps to the Project Summary Task's Cost fields or a custom Number field if the destination is MS Project desktop where budget fields are resource-cost derived. We preserve the project-to-client ownership relationship using a custom Project-level field (Text type) referencing the Client name.

Intervals Milestones are date-driven checkpoints with optional comments and a sequence within a Project. We map each to an MS Project task with Duration set to 0 days, the Milestone flag enabled, and the target date set as both Start and Finish. Task Name migrates as the Milestone name; comments migrate to a custom Text field or a Project note document. If Intervals Milestones have an order sequence, we preserve it using a custom Number field (Sort Order) for the customer to use in sorting or filtering.

Intervals Tasks belong to a Project and optionally to a Milestone, carrying name, status, estimated hours, actual hours, assignees, and comments. We create Summary Tasks in MS Project for each Intervals Project and promote Intervals Tasks with no parent-task relationship to top-level tasks; Tasks with a parent-subtask relationship in Intervals become Subtasks under a Summary Task. Estimated hours map to the MS Project Work field (assuming an 8-hour day resource unit); actual hours map to the Actual Work field. Task status (active, complete, on-hold) maps to Percent Complete or the Task Is Marked Complete flag.

Intervals Task Comments are threaded text entries attached to a specific Task. MS Project has no native threaded comment model on tasks — the Notes field (Text type) is the standard location for task-level notes. We migrate the most recent or highest-voted comment into the task Notes field. For threaded comment histories with multiple entries, we append them sequentially with timestamp and author attribution. If the destination is Project Online, we recommend a linked SharePoint task list with a modern comment experience as the rebuild target.

Intervals Project Notes are standalone text entries scoped to a Project but not tied to Tasks or Milestones. We migrate these to the MS Project Summary Task's Notes field or to a Project-level custom Text field. For Project Online destinations, we recommend storing them in the Project Site's Pages or a linked SharePoint document as a structured text file.

Intervals Time Entries are the primary billing object — each records hours, date, task association, and billable status. MS Project Desktop tracks work as Actual Work on resource assignments, not as independent time entries. We aggregate Intervals time entries by task and date and populate the MS Project Actual Work field for the assigned resource. The billable/non-billable flag from Intervals maps to a custom Flag or Text field on the task. If the customer uses Project Online with Timesheets enabled, we preserve time entry records in a custom list or integrate them via Power Automate rather than forcing them into the MPP data model.

Intervals custom activity fields (user-defined properties on time entries, scoped per account) are not visible in the standard CSV export — they appear only via the Intervals API. We enumerate all active custom activity fields during the discovery phase, identify their data types, and create corresponding MS Project custom task fields (Text1-30, Number1-10, Date1-10, or Flag1-10 depending on type). Each custom field on a time entry in Intervals becomes a custom field on the linked task in MS Project. If the destination is MS Project desktop (not Project Online), Enterprise custom fields are not available; we use the standard custom fields on the Task object.

Intervals Documents are attachments stored per task with no bulk export capability. We document every document URL during the discovery scan, organizing them by Project and Task in a structured checklist. For MS Project Online destinations, we provision SharePoint document libraries on each project site and provide the customer with a per-project download-and-upload checklist. For MS Project desktop destinations, documents cannot be natively embedded; we deliver the complete document inventory for manual re-association post-migration.