Migrate from Zoho Projects to Microsoft Project

Zoho Projects map to Microsoft Project plan files (MPP) or Project Online project records. We export project name, description, start date, end date, status, and owner from Zoho and create the corresponding project in Microsoft Project. If the destination is Project Online, we use the Project API; for desktop MPP delivery, we convert to XML and import via the desktop client or a conversion library. Custom project-level fields from Zoho migrate to Microsoft Project custom task fields scoped to the project summary row.

Zoho Task Lists sit one level below Project and contain ordered tasks. Microsoft Project has no Task List equivalent; we create summary tasks that serve as the grouping container. We preserve the Task List order using the WBS (Work Breakdown Structure) number or outline number sequence. If a Zoho project has multiple Task Lists, each becomes a summary task group with its tasks indented beneath.

Zoho Tasks map directly to Microsoft Project tasks. Name, description, start date, finish date, duration, priority, and status migrate to the corresponding Microsoft Project task fields. Task notes in Zoho become Microsoft Project task notes. Work (hours) migrates to the task's Work field if the Zoho task has time logged; otherwise Work defaults to the calculated value from duration and resource assignment.

Zoho subtasks (nested within tasks, up to two levels) map to indented tasks in Microsoft Project. We preserve the parent-child hierarchy by maintaining the outline indent structure. If a Zoho task has only one level of subtasks, the parent becomes a summary task with children indented beneath. Two levels of subtask nesting requires flattening into a single indented hierarchy per Microsoft Project's single-level nesting constraint.

Zoho Milestones are date-bound markers that can group tasks; they map directly to Microsoft Project milestones (tasks with zero duration). The milestone name, target date, and associated tasks migrate. In Microsoft Project, we set the task type to Fixed Duration with zero duration to render the milestone diamond on the Gantt chart. The relationship between milestone and contributing tasks is preserved as a milestone dependency link.

Zoho time logs linked to tasks map to Microsoft Project task assignments. Each time entry row (user, date, hours, billing info) becomes an assignment on the matching task with the logged hours recorded in the Assignment Work field. If the destination is Project Online, assignment data persists in the resource management view; for desktop MPP, hours are recorded on the task row. Zoho billing rates and cost fields do not have a native Microsoft Project equivalent and are stored as custom numeric fields on the task.

Zoho finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependencies map to Microsoft Project task dependencies. We export the dependency type and the predecessor task ID from Zoho and create the corresponding predecessor link in Microsoft Project. If the destination does not support all four dependency types, we convert non-finish-to-start links to finish-to-start with adjusted lag time to preserve the logical sequence.

Zoho Issues are tracked separately from tasks with their own status workflow. Microsoft Project has no native issue tracker; we map issues to tasks with a custom Issue flag field, or we document issues separately for the customer's admin to manage in a connected helpdesk tool. Issue severity and type picklists map to custom picklist fields on the task. This is a configuration decision made during scoping based on the customer's post-migration workflow.

Zoho project forums are discussion threads with replies, authors, and timestamps. Microsoft Project has no discussion thread feature in standard plan files or Project Online workspaces. We do not migrate forums as records. We deliver a written inventory of forum threads per project so the customer's admin can decide whether to archive them externally (PDF export) or notify users that discussions will not carry forward.

Documents and attachments in Zoho Projects are stored in Zoho's file store and referenced by file ID or URL. We export the attachment metadata (filename, size, upload date, uploader) as a document inventory spreadsheet. File binaries do not transfer automatically because Microsoft Project does not have a native document management store; we provide the metadata inventory and a set of upload instructions for the customer's admin to re-upload files to SharePoint, Teams, or the connected document library after migration.

Zoho custom fields on Projects, Tasks, and Issues map to Microsoft Project custom fields of equivalent type. Text fields map to Text custom fields; numeric fields map to Number custom fields; date fields map to Date custom fields; picklist fields map to Lookup tables or flag/Status custom fields. We extract the custom field definitions and values separately from the standard record export and apply them as a second pass after the base task structure is in place.

Zoho project users and team members map to Microsoft Project resources. We export the user email, name, and project-level role from Zoho and create matching resources in Microsoft Project. Resource types (Material vs Work) are configured based on the customer's use case during scoping. If the destination is Project Online, resources are provisioned in the Project Online resource plan; for desktop MPP, resources are stored in the resource sheet within the plan file.