Migrate from Husky to Asana

Husky Projects map to Asana Projects as the primary container. Project name, status, start/end dates, description, and owner assignment transfer directly. Custom project fields in Husky (tenant-specific) are enumerated during discovery and mapped to Asana custom fields created in the destination workspace before migration. If a Husky custom field has no Asana equivalent, we flag it during scoping for the customer to decide whether to create a new Asana field or consolidate.

Husky Tasks map to Asana Tasks with project membership, assignee, due date, and status preserved. Subtasks in Husky migrate as Asana subtasks, preserving the parent-child hierarchy. Task descriptions migrate as the task body. Completed-at timestamps transfer to Asana's Completed field to preserve completion history.

Husky Client records (contact details, billing address, tax settings) split across Asana Organizations and Teams depending on structure. Billing address and tax settings have no direct Asana field; we preserve them in a custom text field client_billing_address__c on the Organization record. The customer chooses during scoping whether clients map to a single Organization with multiple Teams or to individual Team records. Inactive clients are flagged for customer review before import.

Husky Time Entries link a user, a project or task, and a duration or start/end time. We map these to Asana Tasks with custom numeric fields for duration (in minutes) and a date field for the entry date. Date-range scoping is applied to avoid importing mid-billing-cycle entries; the customer defines the scope window during discovery. Billable vs non-billable flags preserve as a custom boolean field billable__c. Time entries without a parent task map to the parent project as a task with a time-tracked flag.

Husky Recurring Jobs store a frequency, interval, and last-run date. We export the job template name, description, frequency metadata, and last-run date. Recurrence rules do not transfer as active schedules in Asana because the recurrence trigger logic cannot be reconstructed from the exported metadata. We document each recurring job as a task with the frequency details in a custom field recurrence_notes__c so the customer's admin can recreate the recurrence in Asana's Rules or Calendar Sync manually.

Finalized Husky invoices are locked financial records and are not imported to avoid duplicate entries in the customer's accounting system. We export invoice history as a reconciliation CSV report (invoice number, client, date, amount, status) for the customer's accounting team or CPA to handle financial record continuity. This is a hard exclusion agreed during scoping.

Husky project-level custom fields are enumerated during discovery with their data types (text, number, date, picklist). Each is created in Asana as a typed custom field on the Project object before record migration begins. Picklist options are mapped exactly; new options added after discovery require a supplemental mapping pass.

Husky task-level custom fields follow the same enumeration process as project fields. We create matching Asana custom fields on the Task object, preserving picklist values and date formats. Numeric fields map to Asana number fields; text fields map to Asana text fields.

Husky client custom fields migrate to Asana Organization custom fields. The same type-enforcement rules apply. Fields that reference Husky-specific concepts (e.g., tax rate, billing terms) are mapped to text fields in Asana with the original value preserved.

Husky Users (active and inactive) map to Asana Users resolved by email address. Active users are invited to the Asana workspace during migration setup. Inactive or archived Husky users are flagged for the customer to decide whether to import as inactive Asana members or omit. Owner assignment on Projects and Tasks resolves to the matching Asana User by email.

Husky project status values (Active, On Hold, Completed, Archived) map to Asana project status values with the same semantics. Status change timestamps transfer to a custom field status_changed_at__c for audit.

File attachments on Husky Tasks are extracted by URL or downloaded during the extraction phase, re-uploaded to the corresponding Asana Task, and linked via Asana's attachment object. Large attachments (>25MB) may require a separate transfer step; we flag these during scoping if they exist in the source account.

Husky task comments migrate to Asana task comments with author, timestamp, and rich text body preserved. The comment author resolves to the matching Asana User by email. Comments on tasks that are themselves being omitted (e.g., tasks belonging to excluded projects) are not migrated.