Platform migration to Asana
Data and processes migrated from Collaborative Work Management platforms into Asana — with fixed scope, fixed fee, fixed timeline and evidence before cutover.
Monday.comClickUpJiraSmartsheetWrikeScreendragonOther platforms on request
Service overview
| Scope | Migrated from source | Lands in Asana as |
|---|---|---|
| Work data | Projects, tasks, custom fields, comments, attachments, dates | Projects, tasks, field library |
| Work structure | Hierarchy, dependencies, milestones, templates, views | Sections, dependencies, templates |
| Process logic | Automations, approvals, intake forms, routing conditions | Rules, approvals, forms |
| Identity and access | Users, guests, roles, permissions, legacy identifiers | Members, teams, ID crosswalk |
| Integrations | Native connectors, custom and third-party integrations | Asana apps, iPaaS workflows |
Native terms mapped
Monday.com · boards, groups, items, updates
ClickUp · spaces, lists, tasks, subtasks
Jira · projects, epics, issues, workflows
Smartsheet · sheets, rows, child rows, workflows
Wrike · spaces, folders, blueprints, tasks
Screendragon · jobs, briefs, tasks, workflows
Delivery approach
Workstream one
Data migration
- Scripted extraction and load through platform APIs
- Deterministic, repeatable runs with field-level mapping
- Every record keeps its source identifier
No AI capability processes customer content.
Workstream two
Process migration
- AI-assisted analysis of automations, schemas, roles, event logs
- Undocumented processes surfaced and documented
- Each process kept, redesigned or retired by customer decision
AI analyses configuration and event metadata only.
01Assess
02Design
03Build
04Validate
05Cutover
Inventory, complexity profile, fixed quote
Automated API scan, no interviews
Target model and mapping, signed off
Productised work-domain models
Staged load, rules rebuilt
Reusable connectors and rule patterns
Reconciliation, rule tests, acceptance
Automated test harness
Delta load, go-live, hypercare
Rehearsed runbook, same scripts
Accelerator applied at each phase. Duration by package below.
Engagement options
Starter
Self-service, single team
£1,000
Fixed fee · 1–2 days
- Data migration only
- One source platform
- Up to 10 projects, 30 users
- Projects organised in Portfolios
- Rules and automations excluded
- Evidence pack, then cutover
- Free trial on one project
Advanced
Department
£15,000
Fixed fee · four weeks
Everything in Starter, plus
- Process migration
- Up to 50 projects, 200 users
- Up to 10 rules and automations
- Intake forms and approvals
- Up to 5 native integrations
- AI use cases + 3 AI Teammates built
- 15 days hypercare
Enterprise
Organisation or group
from £35,000
Fixed fee per wave · 6–8 weeks
Everything in Advanced, plus
- Unlimited volume, in waves
- Full organisational replica
- Identity and permission model
- Non-native integrations
- Up to 10 AI Teammates / programme
- Parallel run
- 20 days hypercare
RUN IT YOURSELF — FREE
For skilled in-house IT teams: run a Starter-scope data migration on your own n8n instance with our mapping logic. No fee, no sign-up. Get the workflow
Data volume included, not metered. AI Teammates require the customer's Asana AI Studio entitlement. Fees exclude VAT, invoiced on acceptance.
Delivery assurance
UK data residency. Customer data is processed and held in the UK throughout.
UK GDPR compliant. Standard DPA; data deleted at acceptance, with written confirmation.
Least-privilege access. Read-only tokens, encrypted in transit and at rest, revoked at acceptance.
Staged, then live. Full rehearsal in the customer's Asana; the source stays untouched for rollback.
Three-level validation. Counts per object, field-level sampling, a test case for every rule.
Cutover gate. Go-live only after customer sign-off; failed checks rerun within the fee.
Migration evidence pack — issued before every cutover
- Source-to-Asana reconciliation by object
- Field-level sample check with pass rate
- Rule and automation test log
- Exception register with reason for each item
- Identifier crosswalk file for legacy reporting
- Cutover sign-off record and audit log of writes
