Migrate from web2Project to Asana

web2Project Projects map to Asana Projects. The source project name, description, start_date, end_date, priority, and color code all migrate. The web2Project project owner maps to an Asana Project member with Admin access. We preserve the project status (Active, On Hold, Completed) by mapping it to an Asana project field. Note that Asana does not have a native Project-level budget field; any web2Project budget values migrate as read-only custom fields in Asana.

web2Project Tasks map to Asana Tasks. The task name, description (migrated as rich text), start_date, due_date, priority, and percent_complete all transfer. The web2Project task owner (assigned user) maps to the Asana Task assignee. Subtasks in web2Project with a parent_task_id map to Asana Subtasks nested under the parent Task. Asana's Start Date field requires Premium or above—if the destination plan is Starter or lower, we migrate start dates as a custom field instead.

web2Project supports Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish dependency types. Asana natively supports only Finish-to-Start and Start-to-Start. We migrate Finish-to-Finish and Start-to-Finish as Finish-to-Start with an adjusted offset calculated from the task duration difference, and flag these in the mapping notes. Cycles are detected and broken at the earliest dependency in the chain.

web2Project User records (username, email, role, active/inactive status) map to Asana User accounts. We match by email address. The web2Project role (Project Manager, Developer, Viewer) maps to Asana Project membership levels (Admin, Member, Guest) based on a role-mapping table defined during scoping. Inactive web2Project users migrate as Asana Guests with no project assignments, preserving the historical record without consuming a seat license.

web2Project Companies are organizational entities distinct from Departments. Asana's equivalent organizational unit is the Team (inside a Workspace). We map web2Project Companies to Asana Teams, merging any Companies with duplicate names during import. If a web2Project Company has associated Departments, those map to Asana Sections within Projects or to Tags for cross-project grouping. The Company name becomes the Team name; Company contact information becomes a Team description or a dedicated Contacts integration if the customer uses Asana with a CRM.

web2Project Departments are sub-organizational units within Companies. Asana has no native Department object. We map Departments to Asana Sections within Projects (for project-scoped grouping) or to Tags (for cross-project tagging). The customer chooses during scoping. If the department hierarchy matters for reporting, we recommend Tags with a naming convention that preserves the hierarchy (e.g., Engineering > Backend, Engineering > Frontend).

web2Project v2.4+ custom fields use SOLID OOP storage with standard store and delete methods. We map text fields to Asana Text, number fields to Asana Number, date fields to Asana Date, dropdown lists to Asana Enum (single-select), and checkbox fields to Asana Enum (multi-select with checkbox UI). Custom field labels and option values transfer directly. Note that Asana custom fields require Starter tier or above—we confirm the destination plan during scoping and flag if a custom field reduction is needed for Starter plans.

web2Project pre-v2.4 custom fields used a different storage schema with the optionlist system reimplemented in v2.4. We detect the source version during database inspection and adjust field mapping logic. Pre-v2.4 optionlist values require a join across the old options table; we execute this at extraction time to produce a flattened dataset compatible with Asana's custom field enum values. Truncation risks are flagged before import.

web2Project Gantt chart data consists of task start dates, end dates, durations, and dependencies. We migrate these as Asana Timeline view data—the underlying task dates and dependency relationships drive the Asana Timeline rendering. The Gantt chart visual rendering itself does not migrate (it is a display artifact), but the data that populates it transfers 1:1. Timeline view requires Asana Premium; if the destination plan is lower, we migrate dates as custom fields and note that Timeline rebuild is a post-migration configuration step.

web2Project calendar events with start time, end time, and location map to Asana Tasks with start_date, due_date, and a location custom field. iCalendar export data (VEVENT components) is parsed and transformed during extraction. Recurring events in web2Project map to Asana recurring tasks if the recurrence pattern is simple (daily, weekly); complex recurrence rules are flattened into individual task instances with a recurrence metadata tag.

web2Project project forums contain thread metadata (author, timestamp, subject) and post content. Forum categories map to Asana Conversations at the Project level, and individual threads map to Conversation threads with posts preserved in chronological order. If the project forums are extensive (hundreds of threads), we may externalize them as linked Google Docs or Confluence pages with a link in the Asana Project description, per the customer's preference.

web2Project file attachments at the project and task level store file references and metadata. We migrate the file name, URL (if hosted externally), upload date, and uploader. For files under 100MB, we upload directly to Asana as native attachments. For files exceeding 100MB, we upload to Google Drive or SharePoint and link from Asana; the file reference migrates but the binary does not. We inventory all large files during discovery and confirm the externalization strategy with the customer.

web2Project budget fields exist in the schema but are explicitly documented as for documentation purposes only—they are not used for calculation or reporting. We migrate budget field values as Asana custom number fields with a note that they are informational. Any actual budget tracking logic (alerts, roll-ups, variance reports) must be re-implemented in Asana as a separate configuration or through an Asana-integrated budget tool.

web2Project v2.4+ activity logs are timezone-aware; pre-v2.4 logs store timestamps in server local time with no explicit timezone metadata. We extract activity log records as a reference dataset during migration but do not load them into Asana's native audit trail (Asana's audit log is an admin-visible feature separate from task history). Instead, we deliver a CSV inventory of activity log records grouped by user and date range, which the customer's admin can consult post-migration if historical activity review is required.

web2Project's modular PHP architecture allows community-added modules that extend the standard schema. During database inspection we identify any non-core tables. These tables are inventoried in the migration scope document with recommendations: if a community module has an Asana equivalent (e.g., a time-tracking module maps to an Asana time-tracking integration), we include it in the scope; if no equivalent exists, we note it for the customer to address post-migration.