Migrate from Visma Severa to Trello

Visma Severa Cases map 1:1 to Trello Boards, preserving Case number as the Board name or description, Case status (Active, Completed, On Hold) as Board background color or a List named by status, and Business Unit assignment as a Workspace or as a Board label taxonomy. Each Case's sub-tasks and project-level tasks become Cards in the Board. If the customer uses multiple Business Units, we create a separate Workspace per Business Unit and one Board per Case inside it.

Severa Customer records map to Trello Workspace members. Company name becomes the member's display name or is recorded in a custom field on Cards where the customer is relevant. Individual contact persons at each Customer become Members assigned to Cards. We preserve the Customer-Case linkage by assigning the relevant Members to the Board representing that Case. Note that Trello has no native Account or Company object; all customer context lives in card metadata.

Severa's project-level tasks and sub-tasks within a Case export as rows with parent-child relationships. We reconstruct the hierarchy in Trello by creating parent Cards with child Cards attached as a Checklist, or by using Trello's Card aging and Cover features to visually distinguish priority. Task status from Severa maps to List position (To Do, In Progress, Done) or to Card labels.

Hour Entries (billable and non-billable) transfer as structured text appended to the Card description or as Checklist items on the Card representing the relevant task. Each entry carries the date, hours logged, billable flag, and hourly rate as text. Trello has no native time-tracking object; the billing flag and rate are informational only and do not generate invoices. We recommend the customer evaluates Trello time-tracking Power-Ups (Tempo, Clockify) separately.

Severa Resource Allocations define who is assigned to a Case and for what time window. We map these to Trello Card Members (the assigned person) and set a Card due date from the allocation window. Trello has no native resource calendar or capacity view; the customer uses Trello Calendar view or a Power-Up for visual scheduling. Multi-person allocations within the same time window map to multiple Members on the same Card.

Severa Business Units organize Cases, Users, and reporting across departments. We map them to Trello Workspaces (if the team prefers full separation) or to Board Labels (if cases from different Business Units share a Workspace). The customer chooses during scoping. Note that Trello Workspaces are separate billing units; if Business Units represent separate legal entities, separate Workspaces may carry separate Trello subscription costs.

Active Severa Users become Trello Workspace members. We map by email address with role assignment preserved in a custom field or Card label. Inactive Severa users (historical employees with logged time) do not receive Workspace invites but appear in historical Hour Entry text for audit trail purposes. Trello guest pricing applies if the customer uses guests across multiple Boards.

Severa custom fields on Cases, Customers, and Hour Entries transfer as Trello Custom Fields (text, number, date, dropdown, checkbox types). The Custom Fields Power-Up is required, which means the destination Workspace needs Trello Standard ($5/user/month) or Premium. Free Workspaces do not support custom fields; we flag this requirement during scoping. Custom field options in Severa dropdowns map to Trello dropdown options.

Invoices generated in Severa (sent to Visma.net Financials or via Maventa) do not transfer to Trello because Trello has no invoice object, no payment status tracking, and no integration with accounting systems. Invoice headers, line items, and payment status are preserved in a CSV export delivered alongside the migration. The customer reconciles open invoices in their accounting system before cutover.

Expense records with amounts, currency, expense type, and linked Case do not transfer as structured data. Trello has no expense object, no currency fields, and no expense reporting. We deliver expense data as a structured CSV export with Case reference for the customer's finance team to process in their accounting tool.

Profitability margins, utilization percentages, and forecast metrics are computed at runtime by Severa and have no underlying data rows to export. These dashboard figures cannot migrate. We preserve the raw Hour Entries, Expenses, and Billable Items so the customer can configure equivalent reports in Trello using third-party reporting tools or a connected BI platform if needed.

Approval workflows, custom field configurations, master/product settings, and Visma Business integration settings are Severa-internal and cannot be exported. We document every active workflow, approval chain, and billing automation in a written inventory delivered as part of the migration package. The customer's admin rebuilds these using Trello Automation (free) or Butler (paid) post-migration.