Migrate from Artemis 7 to Microsoft Project

Artemis 7 Projects map directly to Microsoft Project plan files (.mpp) or Project Online/Project for the Web projects. The Project Name, description, status, start date, and finish date transfer as core plan properties. For Project Online and Project for the Web, we create the project first and use the project ID as the parent reference for all subordinate records.

Artemis 7 Tasks map to Microsoft Project Tasks with the parent-child hierarchy reconstructed using summary tasks and WBS codes. Subtasks with a parent reference in Artemis 7 become child tasks under the corresponding summary task in Microsoft Project. Task Name, Start, Finish, Duration, Percent Complete, and Priority migrate directly. We flag any Artemis 7 tasks with missing start dates for manual date assignment during migration review.

Artemis 7 Milestones map to Microsoft Project Tasks with Duration set to zero days, which automatically displays them as milestone diamonds on the Gantt chart. The milestone name and due date transfer to Task Name and Finish Date respectively. Milestone-level custom fields map to Microsoft Project task custom fields.

Artemis 7 Resource records contain user name, role, and availability expressed as a percentage. Microsoft Project uses hours-based resource capacity calculated from the project calendar. We apply a ratio-based conversion using the project's working calendar: an Artemis 7 resource assigned at 50 percent availability to a 40-hour task becomes 20 hours of assignment in Microsoft Project. We flag any resources without a named User assignment for the customer's admin to provision in the resource sheet.

Artemis 7 task assignments (task tied to a resource) map to Microsoft Project Assignments with Work (hours) calculated from the Artemis 7 allocation percentage and task duration. Assignment start and finish dates derive from the parent task schedule. We use the project calendar to convert Artemis 7 allocation percentages to Microsoft Project hours so that resource leveling in the destination produces correct results.

Artemis 7 Time Entries record hours logged against a task and user. We map them to Microsoft Project Assignment Actual Work. Billable flags and billing rates in Artemis 7 require explicit customer confirmation because Microsoft Project does not have native billing rate fields; these values can map to custom fields on the assignment or task if the customer has a custom field slot available.

Artemis 7 custom fields exist per-project and are not centrally managed. This is the most common source of migration errors. We consolidate all unique custom field names across active projects, flag duplicate field names with conflicting data types for customer resolution, and map each to a Microsoft Project custom field. The customer confirms the target field name and type during scoping before any load begins.

Artemis 7 stores task dependencies as relationship metadata (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish). Microsoft Project supports the same four dependency types with explicit start-variant and finish-variant options for FS and FF. We map each Artemis 7 dependency type to its Microsoft Project equivalent and flag any unsupported relationship types with a severity note. Finish-to-Start is the default when an Artemis 7 dependency type cannot be determined.

Artemis 7 stores file attachments as URLs pointing to its own internal file service. These URLs expire or break when a user account is deprovisioned. We do not include attachment URLs in the migrated dataset. We deliver a structured flag list of all attachment references with the owning project, task, and file name so the customer's admin can manually re-upload to Microsoft Project's document attachment feature or a linked SharePoint document library.

Artemis 7 risk and issue records contain name, description, owner, likelihood, impact, and status fields. Microsoft Project does not have a native risk object, so risks map to task-level notes or to a custom fields block on the project summary task if the customer defines risk tracking fields. We deliver risks and issues as a structured CSV alongside the migration for the customer's admin to recreate in their preferred risk tracking tool or within Microsoft Project custom fields.

Artemis 7 project calendars define working days and hours that drive task scheduling. We map these to Microsoft Project Calendars attached to the project plan. Non-standard working patterns (compressed weeks, part-time resources) convert to Microsoft Project calendar exception entries. Standard Monday-Friday 9am-5pm calendars require no conversion.

Artemis 7 baselines are stored as portfolio-level snapshots and may not expose individual task baseline fields in a portable format. We map whatever baseline fields are present in the export (baseline start, baseline finish, baseline cost) to Microsoft Project BL1 baseline fields and flag the remainder for customer review. If no structured baseline export is available, we document this gap in the handoff inventory.