Migrate from WP Project Manager to Asana

WP Project Manager Projects (wp_cpm_projects) map to Asana Projects. We extract project title, description, created date, and visibility setting. Project start and due dates from wp_cpm_projects map to Asana Project Start Date and Due Date fields. Projects are loaded first in the dependency order because all Tasks, Milestones, and Comments reference a project_id foreign key that must resolve at insert time.

WP Project Manager Milestones are stored as type=milestone records in wp_cpm_messages with a linked project_id. Asana has no native Milestone object; we map Milestones to Asana Sections within the parent Project. The milestone title becomes the Section name, and the due date is stored as a custom field on the Section. If the customer uses milestone-to-task dependency links, we document them as a task dependency map for manual Timeline configuration in Asana.

WP Project Manager Tasks are stored in wp_cpm_messages with type=task. We extract task title, description (from message body), due date, priority flag, and status. The project_id foreign key resolves to the Asana Project GID at migration time. Tasks without a matching parent Project are held in a reconciliation queue. Priority values (low, normal, high, urgent) map to Asana custom fields or Tags since Asana does not have a native priority field.

WP Project Manager Subtasks are stored in wp_cpm_task_relations linked to a parent task_id. We reconstruct the subtask hierarchy by reading the relation records, ordering children under their parent task, and inserting them as Asana Subtasks under the resolved parent Task. Subtask title, description, assignee, and due date migrate directly. Subtask depth beyond two levels maps to additional Asana Subtasks with the same parent-child chain preserved.

WP Project Manager Comments are stored in wp_cpm_task_comments linked to task_id. We preserve comment body, author (WordPress user ID resolved to Asana user), timestamp, and any attachment references. Author mapping uses the WordPress user-to-Asana user email resolution step. Comments on milestones and projects migrate as Project-level Comments in Asana.

File attachments referenced in task comments are stored as WordPress post attachments in the wp_posts table pointing to files in wp-content/uploads. The database contains the file path and attachment post record, but actual files must be transferred separately. We pair the database export with a file sync step that mirrors the uploads directory and re-attaches files to the corresponding Asana Task via the Asana Attachments API. If file path references contain absolute URLs with the source domain, we strip and normalize them during transfer.

Users in WP Project Manager are WordPress native accounts referenced by ID in wp_users. We export wp_users (user_email, display_name, user_registered) and match by email address to Asana workspace members. Any WordPress user without a matching Asana user goes to a reconciliation queue for the customer to provision accounts. WordPress role and capability assignments do not map directly to Asana's project permission model; we document the permission structure for manual rebuild in Asana Teams and Project sharing settings.

Time tracking entries are stored in a premium module sub-table with user_id, task_id, start/end timestamps, and notes. We extract time entries and load them as Asana time tracking entries on the migrated Tasks. Note that Asana's native time tracking requires a Premium workspace or Project Premium status; we confirm the destination workspace tier during scoping and flag any cost impact.

Custom Fields in WP Project Manager are stored as PHP-serialized arrays in wp_postmeta. We deserialize the data using a read-then-parse staging script, normalize field names to ASCII-safe slugs, and map values into Asana's custom field schema (text, number, date, enum, multi-enum). Field structure varies per project in WP Project Manager, so we build a per-project custom field map during discovery. If WordPress was upgraded across PHP versions, some serialized values may fail to parse; we flag any parse failures in the migration summary.

Gantt chart data in WP Project Manager is derived from task start dates, due dates, and dependency links stored in wp_cpm_task_relations. We extract dependency links (predecessor-successor pairs) and reconstruct them as Asana task dependencies using the Tasks API to add dependency relationships. Asana's dependency model supports finish-to-start, start-to-start, finish-to-finish, and start-to-finish types; we map from the WP Project Manager dependency type where available.

Recurring task rules are stored as serialized data in wp_postmeta for the Recurring Tasks premium module. We extract the recurrence pattern (daily, weekly, monthly, yearly) and next occurrence date, then configure equivalent Asana recurring tasks. Note that Asana's recurrence engine and WP Project Manager's recurrence rules are not identical; we document the mapped recurrence for the admin to validate in Asana after migration.

WP Project Manager task completion status (marked as done/not done) maps directly to Asana's Task completed status. We preserve the completion timestamp from wp_cpm_messages where available. Tasks completed before migration retain their completed_at date in a custom field for historical accuracy.

Invoice records in WP Project Manager are tightly coupled to WooCommerce and Stripe integrations with no clean export path. We do not migrate Invoice records. We recommend exporting invoices as PDF reports from WP Project Manager's UI before migration begins. Time tracking data migrates independently; financial invoice records must be re-created or imported manually in the destination accounting tool.

Kanban column positions and board visual state are stored in JavaScript-serialized format in wp_postmeta with no stable column-schema export. We do not migrate the visual board layout. Task data migrates to the Asana List view by default; the customer's admin configures Board view columns in Asana based on the source column names documented in the migration summary.