Migrate from Husky to Microsoft Project

Husky Projects map to a Microsoft Project plan file or Project Online project. We extract project name, status, start and end dates, description, and Owner assignment from Husky and write them to the project-level fields in the destination. Active versus archived status in Husky maps to IsActive in Project Online or a Project Plan flag. If the customer maintains multiple active Husky projects, each becomes a separate Project plan on the destination side.

Husky Tasks map to Microsoft Project Tasks with task name, start date, finish date, duration, and percent complete preserved. Parent-child subtask hierarchy in Husky maps to the Outline Level and Summary Task structure in Microsoft Project. We set Summary tasks for parent records and convert them to collapsed outline groups in the destination. Task-level Owner assignments from Husky map to the Project Online Resource pool or desktop Resource names.

Microsoft Project has no native client or account object. Husky Client records (name, contact details, billing address, tax settings) do not map directly into a standard Project field. We export Client data as a structured CSV and recommend hosting it as a SharePoint list or a Power Apps lookup table connected to the Project Online site. We document the field mapping between Husky Client columns and the SharePoint columns so the customer's admin can configure the lookup or hyperlink in the project plan.

Husky Time Entries link a user to a project or task with a duration or start/end timestamp and a billable/non-billable flag. Microsoft Project does not have a native time entry object; instead, task effort is tracked as Work and Duration at the task level with Resource assignments. We aggregate Husky time entries by task and populate the Work field in Microsoft Project, preserving the total hours and the billable flag as a custom flag field on the task. Non-billable hours are noted separately for reconciliation.

Husky Recurring Jobs store a frequency, interval, and last-run date as template metadata. This data does not recreate an active recurring schedule in Microsoft Project because Project has no native recurrence engine for tasks. We export the job template name, the recurrence rule (daily, weekly, monthly, interval), the last-run timestamp, and the associated task list as a structured CSV. The customer recreates the recurrence logic manually using Power Automate or a scheduled task reminder. We document this as a post-migration step in the handoff checklist.

Husky allows per-tenant custom fields on Projects with non-standard names and data types. We enumerate all custom project fields during the discovery pass, classify each by type (text, picklist, date, number), and configure matching custom fields in the Microsoft Project plan or Project Online enterprise custom fields. Text picklists map to outline codes or flag fields; dates map to deadline or baseline date fields; numbers map to number custom fields. Any custom fields added after discovery require a supplemental mapping pass.

Husky task-level custom fields vary by tenant configuration and can include flags, text notes, or numeric cost fields. We map these to Microsoft Project task custom fields: text fields become Notes or flag fields; numeric fields become number custom fields; date fields become deadline or baseline fields. We do not automate the recreation of custom picklist values if the destination plan uses a fixed enterprise field definition; the customer's admin configures the enterprise custom field in Project Online PWA settings before migration.

Husky Client custom fields (billing tier, account manager, contract status) are exported as additional columns in the Client CSV and mapped to SharePoint list columns on the destination client lookup list. We document the type mapping for each custom field so the SharePoint column types are configured correctly by the customer's admin during the SharePoint list setup phase.

Husky Owner records map to Microsoft Project Resources. We resolve each Husky Owner by email, extracting display name, role, and active/inactive status. In Project Online, resources must be added to the PWA Resource Center before they can be assigned to tasks. We export a resource import CSV with Name, Email, Type (User or Material), and Max Units for the customer's admin to bulk-provision before task assignment migration. Archived Husky users are flagged for deferred provisioning.

Husky finalized invoices are locked financial records under the customer's accounting jurisdiction and are not imported into Microsoft Project, which has no invoice object. We export invoice history as a structured reconciliation report (CSV) containing invoice number, client name, date, amount, and status. The customer routes this to their accounting team or CPA for continuity. This is documented as a manual step outside the migration scope.

Husky project attachments are exported from the platform and linked to the corresponding Project Online site or SharePoint document library. We identify all attachment URLs or files during the extraction pass, download them, and organize them by project into a folder structure matching the Husky hierarchy. The customer provisions the SharePoint destination library before migration; we deliver the file manifest and a folder mapping document.

Husky recurring job templates with a defined task structure are exported as template metadata. They do not become live project templates in Microsoft Project automatically, but we provide a template conversion document that maps the Husky template task list to a Project plan outline. The customer's admin uses this document to build a reusable MPP or Project Online template manually, which can then be applied to new projects going forward.