Migrate from Streamtime to Asana

Streamtime Jobs map directly to Asana Projects. We preserve the Job title, description, start and due dates, status (active, on hold, complete), and budget fields as native Asana Project fields or as custom fields on the Project. The Job's full To-Do hierarchy migrates as Task and Subtask under the Project. Note that Asana Projects have no native budget field—we capture the original budget as a currency-formatted custom field for the customer's admin to populate post-migration or connect to a budgeting add-on.

Streamtime To-Dos nested within a Job map to Asana Tasks under the corresponding Project. We preserve the To-Do title, description, assignees (mapped to Asana Members by email), due date, completion status, and the parent-child nesting depth. Streamtime's unlimited nesting flattens to Asana's two-level Subtask model; To-Dos nested beyond two levels are surfaced as flat Tasks within the Project with a custom field parent_to_do__c referencing the hierarchy for the admin to restructure.

Streamtime Time Entries—logged against a Job with duration, team member, date, and optional notes—map to Asana Tasks annotated with the time entry data. We create a placeholder Task with the Time Entry title as the Task name, assign it to the team member, and attach the duration and date as a custom field set (hours__c, date__c, notes__c). If the customer licenses Asana's native time-tracking add-on, we instead populate the built-in time-tracking fields. Rate Card multipliers do not carry forward; we document the original rate card values separately for the customer to configure in any connected billing tool.

Streamtime Companies map to Asana Organizations if the destination is a company-wide workspace, or to a client__c custom field on each Project if Asana is used as a multi-client workspace. We preserve the Company name, website, primary contact name, email, and phone. If the Company has an assigned Rate Card in Streamtime, we document that association as a rate_card_reference__c custom field value so the customer's team can reconnect it to any billing integration in Asana.

Streamtime Team Members map to Asana Members by email match. We extract the full team member list from Streamtime—name, email, role, and whether they are a billable or non-billable resource—and import them into Asana. Any team member without an Asana invite pending is flagged in the reconciliation report. Streamtime's role designations (creative director, designer, developer) are stored in a role__c custom field on the Asana Member profile.

Streamtime Schedules represent a team member's allocated time on a Job for a given date range. Asana does not have a native resource scheduling or capacity planning model. We map Schedule allocations to a scheduled_hours__c custom field on the Task, assigned to the team member, and preserve the start date, end date, and hours. The customer should evaluate Asana's resource management add-on or a third-party tool like Runrun.it or Resource Guru if capacity planning is a recurring operational need.

Streamtime Rate Cards define pricing tiers by role, item, or expense per client or project. Asana has no native rate card model. We create a rate_card__c custom field on Projects storing the JSON-serialized rate card structure (role, rate, currency) as a reference document. The customer's admin maps these to any connected billing tool (Harvest, Toggl, or an invoicing integration) post-migration. Rate card transformations are documented but not automated inside Asana.

Streamtime Quotes are commercial documents with line items, pricing, currency, and status generated from Job data. Asana has no native quoting object. We export Quotes as structured CSV records and deliver them alongside a schema specification for the customer to build a custom Quote object in Asana (using Asana's Custom Objects beta or a third-party quoting tool like Qatalog, Cube, or a custom-built integration). Line item data is preserved but requires manual reassembly in the destination.

Streamtime Invoices are tied to Jobs and Time Entries with line items, amounts, currency, and payment status. Asana has no native invoicing object. We export Invoice records as CSV with full line item detail, payment status, and the original Job reference. The customer should connect Asana to a dedicated invoicing tool (Wave, FreshBooks, QuickBooks, or a custom integration) post-migration; we provide the exported data and the data dictionary.

Streamtime Purchase Orders include vendor associations, line items, and amounts. Asana has no native PO object. We export PO records as CSV preserving vendor name, PO number, line items, total amount, and status. The customer's finance team uses this export to reconstruct POs in their accounting system or any connected procurement tool.

Streamtime Template Jobs are duplicated to create new Jobs with pre-configured To-Dos, rate card associations, and structure. Asana Project Templates exist but do not carry custom fields, rate references, or budget data. We export Template Jobs as standard Projects with a template__c boolean custom field set to true and a full To-Do structure. The customer's admin uses these as blueprints to create native Asana Project Templates. We provide a template mapping guide as part of the handoff documentation.

Streamtime file attachments linked to Jobs and commercial documents migrate as Asana Attachments linked to the corresponding Project or Task. We extract the file URL or blob, upload it to Asana via the API, and link it to the parent record. Large files (over 100 MB) may require chunked upload or an external storage reference if Asana's attachment size limits apply. We flag any oversized files in the pre-migration scan.