Migrate from Blueprint to Asana

Blueprint Projects map directly to Asana Projects as the root container. Project name, description, created date, and modified date migrate as text fields. Start date and due date map to Asana's Start Date and Due Date fields. Blueprint project-level custom fields migrate as typed Asana custom fields on the Project object. Projects are imported first to serve as the parent container for all downstream objects.

Blueprint Scopes represent AI-generated work breakdown within a Project. We assess the Scope depth and structure during discovery. Single-level Scopes map to Asana Sections within the Project. Multi-level or nested Scopes may map to a Section hierarchy plus a custom field scope_name__c to preserve the full original Scope label. Scope descriptions migrate as Section descriptions or task notes depending on which object carries the description in Blueprint.

Blueprint Tasks map directly to Asana Tasks. Task name, description (notes), status, assignee, start date, due date, and created/modified timestamps migrate as standard Asana Task fields. Blueprint's task-level custom fields map to Asana custom fields on the Task object. Task dependencies map to Asana's Dependencies feature (predecessor and dependent tasks).

If Blueprint Tasks contain nested sub-tasks within a Scope, those nested items map to Asana Subtasks attached to the parent Task. Asana Subtasks inherit the parent Task's Project and Section context. The mapping preserves the parent-child relationship by setting the parent Task gid during import. Subtask ordering is preserved by the sort_order field.

Blueprint's role-based access control maps to Asana's team membership and project-level permission roles. During discovery, we inventory every Blueprint Role (Editor, Reviewer, Admin, etc.) and map it to an equivalent Asana team or project permission level (Viewer, Member, Editor, Admin). Guest access in Asana maps from Blueprint's external stakeholder roles. We configure Asana Teams before migration so that User assignments can be resolved.

Blueprint Task assignments (hubspot_owner_id equivalent) map to Asana Task assignees. We resolve assignments by email match against the destination Asana organization's user list. Unresolved assignments (user without an Asana account) are held in a reconciliation queue for the customer's admin to provision before import resumes. The mapping preserves the original assignee as a custom field original_assignee__c for audit.

Blueprint automation rules are stored as structured configuration, not as data records. We document every active Blueprint automation rule during discovery, capturing its trigger conditions, action types, and target objects. We deliver a written inventory with trigger-action pairs mapped to equivalent Asana Rules (available from Asana Starter+). Asana Rules use a trigger-action model that differs from Blueprint's configuration schema, so the inventory includes recommended Rule configurations for the customer's admin to apply post-migration. We do not build the Rules inside the migration scope.

Blueprint attachments referenced by URL or stored object ID migrate to Asana Attachments on the corresponding Task. We extract the attachment URL or object ID from Blueprint and attach it to the mapped Task in Asana. If Blueprint attachments are stored in a third-party content system (Google Drive, S3, SharePoint), we preserve the original link as a custom field or task note so that users can re-link in Asana's native attachment interface. File content download and re-upload is handled separately as part of the attachment migration workflow.

Blueprint custom fields on Projects require schema discovery before migration because field names and types vary by customer configuration. We extract the full custom field schema (name, type, options) from Blueprint, map each to an equivalent Asana custom field type (text, number, date, dropdown, multi-select, people), and pre-create the fields in Asana before data import. Picklist and multi-select options from Blueprint migrate as dropdown and multi-select option lists in Asana.

Blueprint custom fields on Tasks follow the same discovery and type-mapping process as project-level fields. We inventory all task-level custom fields, map to Asana custom field types, pre-create in the destination project, and import field values alongside task records. Enum-style custom fields in Blueprint with specific option sets become dropdown or multi-select fields in Asana with the same option list.

Blueprint's AI scope generation produces structured task descriptions, milestone estimates, and planning context. We assess the AI-generated content volume during discovery. High-value AI content (milestone estimates, acceptance criteria) migrates as formatted notes on the corresponding Task. Low-value or redundant content (auto-generated summaries that duplicate task names) is mapped to a custom field ai_scope_notes__c for admin review rather than polluting task descriptions.

Blueprint project-level settings (visibility, notification preferences, archived status) map to Asana project settings. Archived Projects in Blueprint become Archived Projects in Asana. Project-level default view settings map to Asana's default view preference per project. We configure project privacy and notification settings during the project import phase.

If Blueprint stores explicit task dependencies (Task A must complete before Task B), we map these to Asana Dependencies using the dependency_type field (predecessor). We resolve the dependent task GIDs at migration time and create the Asana dependency records after all Tasks are imported. Circular dependency detection runs before insertion to avoid Asana import errors.

Blueprint task comments migrate to Asana Stories with story_type = comment on the corresponding Task. Comment author, timestamp, and rich text body transfer directly. Attachments on comments migrate as separate Attachment records on the Task. Comment ordering is preserved by created_at timestamp.

Blueprint tags or labels attached to Tasks migrate as Asana Tags. We extract distinct tag values from Blueprint, create the corresponding Tags in Asana, and link them to Tasks via TagAssignment records. Tag colors and naming conventions are preserved where Blueprint exposes this metadata. Multi-value tags (checklist-style) become separate Tags rather than a multi-select field unless the customer specifies a consolidated field strategy.

Blueprint milestones or timeline entries map to Asana Tasks with the milestone toggle set to true. The milestone name, due date, and description migrate as standard Task fields. Milestones that reference parent Scopes map to the corresponding Project-level Section in Asana. Start date and duration from Blueprint timeline entries map to Asana Start Date and the computed due date.