Migrate from Goplan to Asana

Goplan project workspaces map to Asana Projects. We preserve project name, description, start and end dates, member assignments, and collaboration settings. If Goplan's project count limits caused projects to be archived or never created, we document the gap in the migration inventory and note it for the customer to reconcile before or after migration. Each Goplan project becomes a separate Asana Project within the customer's designated Team structure.

Goplan tasks map to Asana tasks within the corresponding project. Task title, description (rich text), status, assignee, due date, and created/modified timestamps migrate directly. Goplan task dependencies (if any) map to Asana dependencies using the Dependents add-on or custom field workaround depending on the destination Asana edition. Completed and incomplete status maps to Asana's Mark as Complete action.

Goplan timesheet entries record hours logged per user against specific tasks and date ranges. Asana has no native timesheet object. We convert time entries to one of two approaches: task duration fields (start date to end date) if the entry represents elapsed work time, or a custom number field capturing total hours that we create as a custom field on the Task object in Asana. The approach is chosen during scoping based on whether the customer needs time-tracking for billing or just historical record of effort.

Goplan user accounts and collaborator roles migrate to Asana Users. We extract user email, name, and role or permission level from Goplan and provision corresponding Asana User invitations or admin-managed accounts. Project-level member assignments become Team memberships in Asana. If a Goplan user has no email domain match in the destination Asana organization, they enter a reconciliation queue for the admin to provision before record assignment proceeds.

Goplan report configurations and historical output exports migrate as static data exports. Report definitions themselves cannot be rebuilt as live Asana Portfolios or Dashboards because the visualization logic does not transfer. We deliver a written report inventory listing every Goplan report with its data source, filters, and intended audience, along with a recommended Asana Portfolio or Dashboard structure for the customer's admin to reconstruct post-migration.

Goplan custom fields on tasks and projects map to Asana custom fields of equivalent type. Text fields map to Asana text, numeric fields to number, date fields to date, and picklist or multi-select fields to Asana picklist or multi-select. We pre-create the custom field schema in the destination Asana project before data import to ensure field IDs are available for lookup during the Task insert phase.

Task-level comments and discussion threads have not been confirmed as a separately exportable object in Goplan's available documentation. We flag this during discovery and attempt extraction via any available export mechanism. If comments are not exportable, we document the limitation in the migration inventory and recommend that the customer use Asana task descriptions or a linked document as a fallback for critical discussions. This is a pair-specific limitation, not a general Goplan platform characteristic.

File attachments on tasks or projects have not been confirmed in Goplan's available data. We verify attachment availability during scoping. If present, attachments require a separate media migration step beyond standard record import, as they must be downloaded from Goplan and uploaded to Asana via the ContentDocument API. We assess this scope separately and price it as an add-on if needed.

Goplan task groupings or sections within a project map to Asana Sections within the corresponding Project. Section names and task ordering within sections preserve during migration. If Goplan uses a different grouping concept (such as buckets or labels), we map those to Asana Sections or Subtasks depending on the customer's preferred structure.

Goplan labels or tags attached to tasks map to Asana Tags if the destination organization has the Tags feature enabled. If labels represent structured categorical data, we map them to Asana custom fields instead for better filtering and reporting. The customer chooses the strategy during scoping based on how tags are used in Goplan.

Goplan project hierarchies or parent-child project relationships map to Asana Teams containing Projects. Nested sub-projects in Goplan become separate Asana Projects within the same Team or a designated parent Project if the customer prefers a containment model. We preserve the hierarchy relationship as project description or a custom parent-project lookup field.

Goplan created date, modified date, and any completion timestamps on tasks and projects migrate to Asana using the created_at and modified_at fields on the corresponding objects. We set these during import using the Asana API's created_on and modified_on parameters to preserve the original creation context and avoid Asana defaulting to the import date.