Migrate from Visma Severa to Microsoft Project

Visma Severa Cases are the primary business-unit container for projects and map 1:1 to Microsoft Project as the top-level project record. We preserve Case number, Case name, Case status (Active, On Hold, Closed), responsible person, Business Unit assignment, Case start and end dates, and Case description. Case-level custom fields migrate as project-level custom fields in Microsoft Project Online or as columns in Project for the Web. The Case's project manager assignment maps to the Microsoft Project Owner field.

Visma Severa task rows within a Case export with parent-child relationships that we reconstruct using task Outline Level, WBS index, and predecessor links in Microsoft Project. Summary tasks in Severa become Summary tasks in Microsoft Project. We preserve task names, planned and actual start/end dates, duration, effort (hours), and percent complete. Milestones in Severa map to Microsoft Project milestone tasks (zero-day duration). Predecessor dependencies from Severa exports map to the predecessor field in Microsoft Project.

Visma Severa hour entries include quantity (hours worked), billing flag (billable/non-billable), hourly rate, approval status, date, and the assigned Case and person. We map these to Microsoft Project task assignments by person, where the Assignment Work field holds the logged hours and the Assignment Resource (person) is resolved via User reconciliation. Billable hours retain a custom field flag. Hourly rate from Severa is preserved as a custom Assignment Cost field if Project Plan 3 or above is used (which supports cost resources). Non-billable entries transfer as zero-cost assignments.

Visma Severa expense records include amount, currency, expense type, and linked Case. Microsoft Project has no native expense tracking object. We map expense amounts to a custom Project-level or Task-level numeric field (Expense Amount) with expense type preserved in a corresponding text field (Expense Type). If the organization uses Project Online with SharePoint integration, expenses can be routed to a linked SharePoint list. Organizations with complex expense reporting needs should plan to integrate a dedicated expense tool post-migration.

Visma Severa resource allocations define who is assigned to a Case and for what time window with start/end dates and allocation percentage. We map these to Microsoft Project Resources (named resources with capacity) and create Assignment records linking each resource to the migrated tasks. Start/end dates from Severa allocations set the resource's availability window in the Resource Sheet. Allocation percentage maps to Assignment Units in Microsoft Project. Calendar-view formatting differs between platforms and may require manual adjustment in Project after migration.

Visma Severa Customer records (company name, contact details, address) have no direct Microsoft Project object equivalent. We map the primary Customer name associated with each Case to a custom Project-level text field called Customer. If the organization also uses Dynamics 365 or a CRM connected to Project Online via the Microsoft Dataverse, we map to the corresponding Account lookup. Standalone Customer contact records (individual contacts, not just company names) do not migrate to Microsoft Project and should be managed in a separate CRM system post-migration.

Visma Severa Users and Employees with Business Unit and role assignments are reconciled against Microsoft Project Resources by email match. We extract the active user list from Severa and create Resource records in Microsoft Project for each person with a project assignment. Inactive users from Severa become inactive (greyed) Resources in Project. Role and Business Unit assignment from Severa are preserved as custom Resource fields (Role, Business_Unit) in the Resource Sheet for reporting and filtering.

Visma Severa Business Units/departments organize reporting across Cases, Users, and Projects. Microsoft Project Online uses Enterprise Resource Pool structures and SharePoint site organization rather than a native Business Unit concept. We map Business Unit assignment to a custom Project-level text field called Business_Unit. For organizations using Project Online with Microsoft 365 Groups, Business Units may map to separate Microsoft 365 Group sites post-migration.

Visma Severa invoices are PSA-generated billing records linked to Cases, hour entries, and expenses. Microsoft Project has no native invoicing or billing object. We do not migrate invoice headers, line items, or payment status to Microsoft Project. The raw source data (hour entries, expense records, billable amounts) transfers as described in other object mappings so that the customer can generate invoices in an alternative system (accounting software, ERP, or a dedicated billing tool) using the migrated project data. We flag this as a manual process in the migration handoff documentation.

Custom fields on Visma Severa Cases, Customers, and Hour Entries transfer as key-value pairs. For Microsoft Project Online, custom fields map to Enterprise Custom Fields (if using Project Web App) or custom columns in Project for the Web. We preserve the original field label from Severa and apply a corresponding display name in Microsoft Project. Field-level data types (text, number, date, currency) map to equivalent column types in Project. Complex picklist values from Severa custom fields become text or choice columns in Project.

Profitability margins, project health scores, utilization percentages, and forecast figures in Visma Severa are runtime-calculated from underlying transactions. These aggregated metrics have no underlying data rows to export and do not migrate. We preserve the raw source data (hour entries, expenses, billable items, resource allocations) so that equivalent metrics can be recomputed in Microsoft Project using custom fields, Power BI reports, or a connected analytics layer. Customers should be aware that pre-migration dashboard snapshots will not carry over.

Visma Sign signed documents are stored in Visma Sign's cloud archive and linked from Severa as file attachments. The actual signed PDFs reside outside Severa and have their own data portability constraints. We do not migrate Visma Sign documents. We document every Case and Invoice that had a linked Visma Sign document with the document title, date, and Visma Sign URL so the customer's team can retrieve originals directly from Visma Sign post-migration.