Migrate from Streamtime to Microsoft Project

Streamtime Jobs map to Microsoft Project as Projects. Job name, description, start date, and due date migrate to Project Name, Project Summary, Start, and Finish. Job status (active, on hold, completed) maps to Project Custom fields since Microsoft Project does not have a native status concept beyond percent complete. Budget burn data from Streamtime Job financial fields does not migrate to Project because Project lacks native budget fields outside of Project Online cost resource tracking.

Streamtime To-Dos map to Microsoft Project Tasks. Each To-Do's Job parent becomes the Project parent so that task hierarchy is preserved. To-Do name maps to Task Name, assigned Team Member maps to Resource Names, and completion status maps to Percent Complete. To-Dos without a date map to undated Tasks in Project; To-Dos with a deadline map to Tasks with a Constraint Type of Finish No Later Than.

Streamtime Time Entries map to Microsoft Project as Actual Work on the corresponding Task. We resolve the Time Entry's Job and To-Do parent to identify the destination Task GUID, then post the hours as a TaskUpdates through the Project Online REST API (Plan 3/5) or legacy MPP import (Project Desktop). Duration per Time Entry converts to hours; multiple entries for the same Task accumulate as Total Actual Work. This preserves budget burn data in the destination but requires the destination project to be checked out for edit in Project Online.

Streamtime Team Members map to Microsoft Project Resources. We resolve each Team Member by email as the Resource name and assign them to Tasks based on their To-Do assignments in Streamtime. Resource type defaults to Material unless the customer specifies Work-type resources. If Streamtime tracks hourly rates per Team Member, those map to Resource Cost Rate tables in Project Desktop or Project Online if the customer has cost tracking enabled in Plan 5.

Streamtime Schedules represent allocated time for a Team Member on a Job. These map to Microsoft Project Resource Assignments on Tasks with Units set to the allocated percentage and Work calculated from duration. Schedule notes and allocation rationale do not have a native Project field; we write them to the Task Notes field during migration. Customers using Project Online can surface allocation data in the Resource Center view post-migration.

Streamtime Companies represent clients and have no direct Microsoft Project equivalent. Project is a scheduling container without a native account or client object. We map Companies to a Project-level custom text field (Client Name) populated from the Job's linked Company. If the customer uses SharePoint Online alongside Project, we can optionally create a SharePoint List of Companies and link them via a Project detail page; this requires separate configuration outside migration scope.

Streamtime Rate Cards define pricing tiers by role, item, or expense. Microsoft Project does not have a rate card object. If the customer enables Resource cost tracking in Project Online Plan 5, we map Rate Card role entries to Resource Cost Rate Table rows (per-hour rates by date range). Non-role rate items (expenses, line items) do not migrate because Project lacks an expense line object; we export them as CSV for the customer's finance team.

Streamtime Quotes have no Microsoft Project equivalent. Project is a scheduling and work-management tool, not a commercial document system. We export Quotes as structured CSV with line items, pricing, and status so that the customer's finance team can import into their accounting tool. We document the Quote export format during scoping and include it in the handoff package. Customers planning to use Microsoft Dynamics 365 Project Operations alongside Project can configure Quote mapping in that system separately.

Streamtime Invoices are commercial documents tied to Jobs and Time Entries with no Microsoft Project equivalent. We export Invoices as CSV with vendor associations, line items, amounts, currency, and payment status. This export is included in the handoff package for reconciliation in the customer's accounting tool. We do not recommend recreating invoices inside Project because Project lacks invoice generation, payment tracking, and accounts receivable fields.

Streamtime POs represent vendor commitments against a Job and have no Microsoft Project equivalent. We export POs as CSV with vendor, line items, amounts, and status. Customers using Project Online with Microsoft Dynamics 365 Project Operations can import these into the Project invoicing module; standard Project Plan 3 and Plan 5 do not include PO functionality.

Streamtime Template Jobs store repeatable project structures with pre-configured To-Dos. Microsoft Project stores templates as .mpt files (Project Template) that must be created manually in Project Desktop or through the Project Online template library. We cannot programmatically create .mpt files because the format requires local desktop tooling. We deliver a written template map: for each Streamtime Template Job, we document the To-Do structure, default durations, and Resource assignments so the customer's PM can recreate them as Project templates post-migration.

Streamtime Attachments linked to Jobs and commercial documents do not have a native Microsoft Project attachment system. Project Online files attach to SharePoint, and Project Desktop files attach locally. We map Attachment file references and metadata, but actual file transfer depends on the destination SharePoint library or local file storage configuration. We export attachment URLs and metadata in a reconciliation CSV for the customer's admin to re-attach post-migration.