Migrate from WiseTeam to Asana

WiseTeam Client records (company name, contact details, lifecycle stage) do not have a direct Asana equivalent because Asana has no native CRM or Contact object. We map Clients to Asana Teams (organizational grouping) and optionally add a Client Name custom field on Projects so that project-to-client relationships are preserved as project metadata. If the customer requires a full CRM view, we document a rebuild approach using Asana Portfolios or a third-party CRM integration as a separate post-migration step.

WiseTeam Projects map directly to Asana Projects. The project name, description, start date, and due date migrate intact. Custom fields on Projects map to Asana custom fields (created in the destination workspace before migration). We create each Project before importing its child Tasks so that the parent-project reference is satisfied at insert time. If WiseTeam Projects have a status workflow beyond Active/Completed, we map to Asana Project Sections or a custom status field.

WiseTeam Tasks map to Asana Tasks as direct children of the parent Project record. Task name, description, assignee, due date, and status migrate intact. Subtasks in WiseTeam map to Asana Subtasks, preserving the parent-child hierarchy. We resolve assignee email addresses against the Asana User table during import so that OwnerId references resolve correctly. Custom fields on Tasks map to Asana custom fields on the destination Project.

WiseTeam time tracking records (hours, date, description, linked Task or Project) have no native Asana equivalent. If the customer licenses the Asana Time Tracking add-on (Business and Enterprise), we map time entries to that add-on's logged time per task. Otherwise, we create custom numeric fields (wt_hours__c, wt_date__c, wt_description__c) on the Task object to store the migrated values. Time entry totals can be rolled up in Asana Dashboards using custom formulas on Enterprise plans.

WiseTeam Invoice records (line items, amounts, status, linked Client or Project) have no native Asana equivalent. Asana does not include a billing, invoice, or quoting object. We extract invoice headers and line items as structured CSV during scoping and deliver them to the customer for rebuild in a dedicated billing tool (FreshBooks, QuickBooks, Stripe, or similar). The invoice metadata (client reference, project reference, amount, status) can be stored as custom fields on the related Asana Project if the customer wants a partial record inside the PM tool.

WiseTeam Sales Opportunities (stage, value, close date, linked Client) have no direct Asana equivalent. We map Opportunities to a dedicated Asana Project with a Client Name custom field, a custom Opportunity Value field, and a custom Stage picklist mirroring WiseTeam's stage names. This gives the customer a pipeline view inside Asana using Project sections as stage columns and a custom dashboard chart for pipeline reporting. The customer's admin can also integrate with a CRM (HubSpot, Salesforce) post-migration to handle opportunity management outside Asana.

WiseTeam calendar events (title, date, attendee information) export via iCal or Outlook integration. We extract event data and map it to Asana's Calendar view by creating Task records with start dates and due dates corresponding to the calendar event times. Attendee information is stored as a custom text field on the task. Native recurring calendar event patterns are noted in the scope document for manual rebuild in Asana using Recurring Tasks.

WiseTeam Users and Task assignees map to Asana User accounts by email address. We extract every distinct user referenced on Task, Project, or Time Entry records and match against the destination Asana workspace User list. Any WiseTeam user without a matching Asana account is held in a reconciliation queue for the customer's admin to provision before record import begins. User roles and permissions (Admin, Member, Guest) are scoped separately and documented for manual rebuild in Asana Team settings.

WiseTeam custom fields on Projects are discovered during scoping and pre-created in the destination Asana workspace using the Asana Custom Fields API before any Project data loads. Field types are mapped: text to Asana text, number to Asana number, date to Asana date, picklist to Asana enum. Custom field values migrate as-is. Asana custom fields are created at the portfolio or workspace level and added to specific Projects, so we scope which Projects require which custom fields during discovery.

WiseTeam custom fields on Tasks are pre-created in the destination Asana Project before Task import. We create each custom field as a column in the Project and map field values during Task insert. If the same custom field name appears across multiple WiseTeam Projects with different value sets, we consolidate them as Asana multi-enum custom fields with the union of all possible values to avoid data loss during migration.

File attachments on WiseTeam Tasks and Projects are extracted and uploaded to the corresponding Asana Task or Project using the Asana Attachments API. We note any file size limits in Asana (250 MB per attachment) and flag files exceeding that limit for the customer's admin to host externally and link via URL. Attachment names and original upload timestamps are preserved in the Asana attachment metadata.

WiseTeam industry-specific workflow templates, stage configurations, and automated routing rules are not confirmed to be exportable via API or standard data export. We deliver a written inventory of every WiseTeam workflow and stage configuration discovered during scoping, with a recommended Asana equivalent (Asana Rules for task automation, custom fields for stage tracking, Portfolios for cross-project visibility). The customer's admin rebuilds these post-migration; this is not included in standard migration scope.