Migrate from WiseTeam to Microsoft Project

WiseTeam Client records (company name, contact details, lifecycle stage) have no native Microsoft Project object. Project Desktop and Project Online lack an Account or Contact entity. We scope this data separately during discovery: clients can be written to a custom Text field on each Project (displayed as Client Name), or held in a companion CRM (Microsoft Microsoft Dynamics 365 Sales , HubSpot, or a spreadsheet). We deliver a Client-to-Project mapping table that links each WiseTeam Client to the migrated Project records so that the relationship is preserved for reference even without a native CRM object.

Each WiseTeam Project maps to one Microsoft Project file (MPP) or one Project Online Project record. We extract the Project name, description, start date, target end date, status, and any custom fields. The Project becomes the top-level container in the MPP hierarchy. If the customer uses Project Online, we load via the Project Online REST API with batch chunking. If Project Desktop is the destination, we export via CSV and import through the Project Desktop Import Wizard, noting that custom fields require manual mapping per the TFS Field Mapping XML pattern.

WiseTeam Tasks nested under Projects map directly to Microsoft Project Tasks with the outline hierarchy preserved as Summary Tasks and Subtasks. We extract Task name, description, start date, finish date, assigned user (mapped to a Resource), duration, and status. Dependencies between Tasks are reconstructed as Microsoft Project predecessor-successor links (Finish-to-Start by default). Custom fields on WiseTeam Tasks migrate to Microsoft Project custom fields (Text, Number, or Date types) if the destination is Project Online; desktop imports require manual field mapping.

WiseTeam Time Entries linked to Tasks carry hours, date, and description. Microsoft Project has no native time-tracking object. We scope the handling strategy during discovery: the most common approach is to create per-task Assignment records in Project Online with the logged hours as Assignment Units or Actual Work, or to write a summary of time entries as a Note on the parent Task. A separate time-tracking companion (Microsoft Dynamics 365 Project Operations, Harvest, or Toggl) is sometimes the right long-term answer for teams that depend heavily on WiseTeam's time billing.

WiseTeam Sales Opportunities (with stage, value, and close date) have no Microsoft Project analog. Project Online supports Enterprise Custom Fields (ECF) of type Cost and Number that can store opportunity value, and Text fields for stage names. We scope whether Opportunity data maps to Project-level ECFs for reference, or whether the Opportunity pipeline is handled separately in a CRM the customer retains. If a Microsoft Microsoft Dynamics 365 Sales or HubSpot instance is in scope alongside the PM migration, we coordinate the Opportunity-to-Deal handling in parallel.

WiseTeam Invoices (headers, line items, amounts, status) have no Microsoft Project object. Project Online is a scheduling and resource management tool, not a billing or financial system. We scope invoice data for archive export as a CSV file (preserving all line items, amounts, and client references) and flag it as out-of-scope for Project migration. If the customer needs invoice data accessible post-migration, we recommend a separate ERP or billing system integration.

WiseTeam calendar events synced from Outlook, iCal, or Gmail carry title, date, and attendee information. We extract calendar events and map them to Microsoft Project Tasks with the original date preserved as Start and Finish. Note that calendar attendees do not map to Project Resources unless the WiseTeam calendar event is linked to a WiseTeam Task with an assigned user; orphaned calendar events migrate as tasks with no resource assignment.

WiseTeam custom fields on Projects and Tasks require discovery during scoping. We extract field names, data types, and values, then map to the closest Microsoft Project custom field type: TEXT fields become Text ECFs, numeric values become Number ECFs, dates become Date ECFs, and currency values become Cost ECFs in Project Online. Project Desktop custom field mapping requires manual configuration using the TFS Field Mapping XML pattern or manual column mapping in the Import Wizard. We deliver a written custom field inventory as part of the migration scope document.

WiseTeam users assigned to Tasks map to Microsoft Project Resources. We extract user email addresses and names from WiseTeam's task assignee list, deduplicate to a Resource pool, and map Resource names to the assignee name. Note that Microsoft Project Resources are project-scoped in desktop MPP files and stored in an organization-wide Resource Pool in Project Online; we recommend pre-creating the Resource Pool in Project Online before task import so that Resource assignments resolve correctly at load time.

WiseTeam file attachments on Tasks and Projects are extracted from the export. For Project Online destinations, we upload files to the associated SharePoint document library linked to the Project site and create a hyperlink on the Task Notes field pointing to the document. For Project Desktop destinations, files are zipped and delivered alongside the MPP file with a filename convention matching the parent Project and Task names. We flag any file size limits (SharePoint defaults to 250 MB per file) and compress or split files as needed.