Migrate your Visma Severa data

Cases are Severa's primary business-unit container for projects. We map them 1:1 to the destination Project object, preserving Case number, status, responsible person, and Business Unit assignment. Sales Cases (pre-project prospects) are handled as a separate pipeline-stage mapping.

Customer records transfer cleanly including company name, contact details, and associated Case assignments. We preserve the Customer-Case linking and any custom address data attached directly to project records.

Sub-tasks and project-level tasks within a Case export as rows with parent-child relationships. We reconstruct the task hierarchy in the destination system using the Case/task parent reference.

Billable and non-billable hour entries include quantities, allocated Case, approval status, and date. We preserve the billing-flag, hourly rate, and approver context during migration.

Expense records with amounts, currency, expense type, and linked Case transfer as line items. We map expense categories to the destination's taxonomy or create custom categories as needed.

Allocations define who is assigned to a Case and for what time window. We preserve start/end dates and person assignments, but calendar-view formatting may differ between source and destination UI.

Invoices are generated in Severa and sent to Visma.net Financials or via Maventa. We transfer invoice headers, line items, and payment status, but invoice PDF attachments require separate file migration handling.

Business Units/departments organize reporting across Cases and Users. We map Business Unit assignments but note that the destination may use a different organizational structure (e.g., Teams, Departments) requiring name or ID reconciliation.

Users and Employees are always synced bidirectionally in Severa's Visma Business integration, but for migration we treat them as a user list with role and Business Unit assignment. Active/inactive status must be preserved.

Signed documents are stored in Visma Sign and linked from Severa as files. The actual signed PDFs reside in Visma Sign's cloud archive, which has its own data portability constraints and is not exportable through Severa's Reporting feature.

System settings, approval workflows, custom field configurations, and master/product settings are Severa-internal and cannot be exported. We document these as manual reconfiguration items in the migration runbook.

Custom fields on Cases, Customers, and Hour Entries transfer as key-value pairs. We map them to equivalent custom properties in the destination or preserve them as structured JSON blobs if the destination schema supports it.

Machine-calculated profitability margins, utilization percentages, and forecast metrics are computed at runtime by Severa and have no underlying data rows to transfer.

Address records not linked to a Customer or Case project are not included in Severa's standard export. Customers must contact Severa support separately to retrieve this data manually.