Migrate from Allfred to Asana

Allfred Projects map to Asana Projects as the top-level container. Project name, description, status, start date, and due date migrate directly. Allfred's project-level team assignments map to Asana Project Members. If the Allfred project uses custom fields, we extract the per-project custom field definitions during discovery and map them to Asana custom fields scoped to that project's sections or as organization-wide fields if the field name is consistent across projects.

Allfred Tasks map to Asana Tasks with title, description, assignee, due date, priority, and status. Subtasks in Allfred migrate as Asana Subtasks (native subtasks within a parent task) rather than independent linked tasks. Task status values in Allfred (e.g., In Progress, Done) map to Asana section membership or completion state. Due dates and start dates transfer to Asana's Start Date and Due Date fields.

Allfred Client records (company name, primary contact, email, phone, address) map to Asana Organizations if the agency wants centralized client tracking, or to Projects as custom field values if client records are primarily used for project tagging. We recommend Organization mapping for agencies with more than 20 active clients or those needing cross-project client reporting. The customer's preference is confirmed during scoping.

Allfred Brands are sub-entities under Clients storing brand name, logo URL, color palette, and guidelines. Since Asana has no native Brand object, we map Brands to Asana Tags (if the agency uses tags for brand attribution) or to a custom Brand Name field on the Client or Project. Logo URLs migrate as text fields or as attachments; color palette and guidelines migrate as task descriptions or attachments on a Brand reference project.

Allfred Contractor records contain name, contact details, hourly rate, and assignment history. Asana has no native Contractor object. We map active contractors to Asana Team Members (Users) if the agency wants them visible in the team roster, or to a Contractor Tag on task assignments if contractors should be separated from full-time team members. Hourly rate migrates as a custom numeric field on the User record or as a tag value depending on the agency's reporting needs.

Allfred Kanban boards export as column names and task-to-column assignments. We map each Allfred column to an Asana Section within the corresponding Project. Column order is preserved by ordering sections in the same sequence as the exported board. If Allfred boards use WIP limits per column, we note these as section descriptions or task count thresholds for the customer's admin to enforce manually post-migration since Asana does not natively enforce WIP limits.

Allfred allows per-project custom field creation without enforcing a global schema, meaning the same logical field (e.g., Client Budget) may exist with different names or data types across projects. We extract all custom field definitions during discovery, build a per-project field map, and present the mapping to the customer for approval before migration. Fields with consistent names and types across all projects can be promoted to organization-wide Asana custom fields; fields that vary by project require project-scoped custom fields or custom field groups in Asana, which may require Asana Advanced or Enterprise for the field group feature.

Allfred Team Member records (name, email, role, avatar) map to Asana Users. We match by email address. Archived or deactivated Allfred team members migrate as inactive Asana Users at the customer's request. Role information migrates to the User's display name suffix or to a custom Role field.

Allfred file attachments stored on the platform's native unlimited storage migrate as native Asana attachments linked to the corresponding task or project. Files are downloaded from Allfred's export bundle and uploaded to Asana via the Asana API. Files exceeding Asana's attachment limits (500 MB per file) are chunked or noted for manual handoff. If the exported file is a placeholder (e.g., a SharePoint reference rather than a binary), we flag it for manual resolution.

Allfred SharePoint integration files store only a reference URL rather than a hosted blob. We export these URLs as-is and attach them as URL-type links to the corresponding Asana task or project, rather than attempting to re-host the file. We alert the customer to any SharePoint-linked files and recommend migrating those files separately via SharePoint's native export tools before cutover if the destination Asana workspace does not have SharePoint access configured.

Allfred workspace settings, notification preferences, and integration configurations export as a JSON bundle per the 'You own your data' policy. We extract this bundle and deliver it as a structured inventory document rather than migrating settings directly, since Asana workspace configuration differs fundamentally from Allfred's settings model. The inventory covers workspace name, default project templates, notification rules, and any active SharePoint or third-party integration references requiring manual reconfiguration in Asana.

Allfred task-level activity (task creation, status changes, assignment changes) migrates as Asana Task activity history. Task comments migrate as Asana Comments on the corresponding Task. The activity timestamp ordering is preserved by setting the comment or story creation date to the original Allfred timestamp. If Allfred stores a separate engagement log for client interactions, we map that to a custom Task description or attachment rather than a native Asana object.