Migrate from .STUDIO to Asana

Projects in .STUDIO map directly to Asana Projects. The project name, description, status (active/archived), start date, and due date migrate to Asana's name, notes, archived flag, and start_on/due_on fields. Budget fields in .STUDIO are optional and many workspaces leave them blank; we preserve budget values as a numeric custom field in Asana and flag any nulls during scoping so the customer can set defaults or accept nulls.

Tasks in .STUDIO map to Asana Tasks. The assignee, due date, estimated hours, status, and custom fields migrate as typed values. Task hierarchy (parent task and subtasks) maps to Asana's subtasks using the parent task GID resolved after the parent record is created in Asana. Dependencies are preserved as notes in the task description because Asana's dependency feature requires a paid Advanced plan.

.STUDIO Clients have no native Asana equivalent. We offer two normalization strategies during scoping: Option A maps Client records to Asana Companies (Company object) and then links Projects to the appropriate Company via the project-company association. Option B drops the Client entity and instead adds a client_name custom field on each migrated Project. Option A is recommended for agencies that bill clients and need company-level reporting; Option B is recommended if client records are primarily label-based. The customer chooses during scoping.

Time entries in .STUDIO carry task_id, user_id, duration, date, billable flag, and hourly rate, rounded to 6-minute increments. Asana's native time tracking requires an Advanced tier subscription ($24.99/user/mo) and uses a timesheet add-on. For Starter and lower tiers, we map time entries to a structured custom field on the linked Task (e.g., 'Logged Hours: 3.5h, Billable: Yes, Rate: $120/hr') as a text block and flag this limitation in the migration manifest. For Advanced tier destinations, we configure the time tracking add-on before migration and populate time entries directly.

Projects and tasks in .STUDIO support custom field definitions that vary by workspace. Asana's custom fields are organization-wide. We read the active custom field schema at export time and map each field by type: .STUDIO text maps to Asana text, number to Asana number with the same decimal precision, date to Asana date, and drop-down to Asana drop-down. Formula fields or fields referencing other custom fields in .STUDIO fall back to plain-text storage with a note in the migration manifest. If a drop-down value exceeds Asana's 255-character label limit, we truncate and flag it.

User accounts in .STUDIO store name, email, role, and hourly rate. We map these to Asana Users by email match. Any .STUDIO user without a matching Asana account goes to a reconciliation queue for the customer's admin to provision before task assignee resolution proceeds. Hourly rate from .STUDIO migrates as a custom field on the Asana User profile for use with billing calculations if the customer enables the time tracking add-on.

Tags in .STUDIO are flat string labels applied to tasks and projects. Asana uses a flat tagging model. We upsert tags individually and attach them to the migrated task records using Asana's tag association endpoint. If a task in .STUDIO has multiple tags, all tags migrate to the same task in Asana. Tag count and tag names are preserved verbatim.

Attachments in .STUDIO carry filename, URL, size, and type. We export attachment metadata and re-upload files to Asana using the Asana Attachments API. Files are associated with the migrated parent task or project. Storage location context from .STUDIO is not preserved; the file becomes an Asana-hosted attachment. Note: Asana limits attachment size to 100 MB per file.

Comments in .STUDIO attach to tasks and carry author, timestamp, and text body. We export all comment records and recreate them as Asana Stories on the migrated task. The author name maps to the Asana user if an email match exists; otherwise the author name is stored as plain text in the story body. Timestamps are preserved using the created_at field on the Asana Story.

Project templates in .STUDIO export as template structure (task list skeleton, placeholder field names, and layout) without populated data. We map the template schema to Asana's duplicate-from-template feature and deliver a manifest of which records are templates versus active projects. The customer manually creates a corresponding Asana project template in their workspace post-migration.

Client records in .STUDIO store billing address, tax ID, payment terms, and invoice history. Asana has no native billing submodule. We preserve billing contact information as a structured text custom field on the Company record (for Option A customers) or on the project record (for Option B). Invoice history and payment records do not migrate and are flagged in the scoping report as requiring export from .STUDIO's billing submodule for archival purposes.

.STUDIO's workspace-level settings (brand colors, logo, client portal white-labeling) have no direct Asana equivalent. We document the workspace configuration during discovery and deliver a configuration checklist for the customer's admin to reapply in Asana (workspace name, member permissions, notification preferences, and custom field library) manually post-migration.