Occupational health

Switching occupational health systems: a checklist

Practical checklist for switching occupational health systems: what may be moved, data migration, parallel running and bringing client companies along.

By PortwayPublished Updated 7 min read

occupational health, system migration, checklist, switching

In this article
  1. Step 0: Separate the record from operations
  2. Step 1: Map the current state
  3. Step 2: Define requirements for the new system
  4. Step 3: Plan the data migration
  5. Step 4: Train the users by role
  6. Step 5: Run in parallel, briefly and with an end date
  7. Step 6: Go live and follow up
  8. What it looks like in Portway
  9. Frequently asked questions

Short answer: Switching the operational system in occupational health takes weeks, not days, and the length is set by the contracts and by how quickly client companies adopt new logins, not by the technology. What moves is the client register, agreements, price lists and upcoming bookings. Medical records normally do not move; they are archived under the Patient Data Act in the old record system. The most common cause of trouble is not technical: it is that the client companies' orderers did not get new logins and instructions in time.

Switching systems often feels bigger than it needs to be. The fear of downtime, lost data and unhappy clients keeps many providers stuck in systems they have outgrown, even as the cost of not switching grows every month. This checklist helps you plan a safe transition.

Step 0: Separate the record from operations

The most important decision comes before any technology. An occupational health provider is a care provider, and medical records are governed by the Patient Data Act: they must be kept for at least ten years after the last entry (Patientdatalagen, chapter 3, section 17, in Swedish, retrieved 20 October 2026), they cannot be weeded out because a system is replaced, and they are not moved casually.

So a well-planned switch separates two things:

  • The record system: where care documentation lives. If it is replaced, it needs its own plan for archiving or record transfer. If it is not replaced, nothing from the record should go into the new operational system.
  • The operational system: orders, booking, agreements, price lists, sick-leave and recovery reports, billing basis. This is the switch this checklist is about, and there is no legal requirement that prevents moving it.

If the two are mixed up, "we cannot switch, we have the records" becomes a reason to keep an operational system nobody likes. They are two different decisions.

Step 1: Map the current state

Before choosing a new system, you need to understand what you actually have:

  • Data inventory: client register, agreements and price lists per client company, upcoming bookings, open orders, ongoing absence cases
  • Integrations: record system, financial system, HR platforms at client companies
  • Processes: document the workflows, not just the system's functions. Who orders, who books, who invoices?
  • Contract position: the notice period in the current system agreement, and in what format the supplier hands over your data. Ask for a trial export early; it shows both the data quality and the willingness to cooperate.

Do you recognize the signs we describe in have you outgrown your occupational health system? Then you already have the answer to why the switch is needed.

Step 2: Define requirements for the new system

Based on your mapping, formulate clear requirements:

  • Functional requirements: what must the system handle from day one? Separate that from the wish list; on day one, orders, the booking calendar and absence reporting have to work.
  • Security requirements: health data is sensitive personal data under the GDPR: encryption, access control per role and organization, a clear answer on where data is stored, and a data processing agreement. Read our guide to GDPR and security in occupational health.
  • The client companies' experience: can they order on their own, with your logo, from the services their agreement covers? That determines how much administration disappears. What to ask is in the checklist for choosing a client portal.
  • Scalability: can the system handle more client companies and more locations without the structure breaking?

Step 3: Plan the data migration

Data migration causes the most concern, rightfully so. Approach it systematically:

  1. Export and review: extract all data from the old system and verify quality.
  2. Clean up: weed out duplicates, inactive client companies and personal data you no longer have a legal basis to keep. A switch is the right moment to meet the retention requirements instead of carrying the debt along.
  3. Map: chart how fields in the old system correspond to the new one. Agreements and price lists are what most often need hands-on work, because two systems rarely model discounts the same way.
  4. Test: run a trial migration with one client company before the full import.
  5. Validate: reconcile the number of clients, agreements and bookings against the source system after migration, and let someone who knows the business review samples.

Step 4: Train the users by role

A new system only works if people use it correctly:

  • Super users: one or two internal people who know the system before everyone else and support colleagues.
  • Role-based training: administrators, clinical staff and the client companies' orderers need different things. The orderers usually need only a short instruction and a login that works.
  • Feedback loop: collect input during the first weeks and adjust the configuration, not the processes.

Step 5: Run in parallel, briefly and with an end date

  • Start with a pilot client, not the entire client base at once.
  • Set a clear end date for the old system. Without an end date the parallel run becomes permanent and doubles everyone's work.
  • Communicate proactively with the client companies: new logins, one line about why ("we are upgrading", not "we have problems"), and who to contact if something chafes. This is the point where clients are actually lost: not because data disappeared, but because an orderer could not get into the new system on the day they needed to.

Want to simultaneously reduce administration and increase profitability? A system switch is the perfect occasion to review all processes.

Step 6: Go live and follow up

  • Monitor the first week extra closely and have support ready.
  • Measure what motivated the switch: time per order, missed bookings, number of support tickets.
  • Adjust the configuration based on actual use, and take the chance to review the administration at the same time.

What it looks like in Portway

In Portway you set up client companies with departments, your services, and which services each client company can order. The client company's administrator is invited by e-mail; the invitation is valid for seven days and login is by default a one-time link to the e-mail address, so no one has to remember a new password. You switch on the modules each client company should have: orders, project booking, surveys and Sjuk & Frisk (sick and recovery reporting). That lets you start with one pilot client and one module, and add the rest once it works.

Portway is not a record system. The record stays where it is, and no record data needs to move in.

Frequently asked questions

How long does a system switch take?

It depends on how many client companies and agreements you have and on how quickly the client companies adopt new logins. Plan for a parallel run of a few weeks with a fixed end date, and set the schedule together with the supplier once the data inventory is done.

What happens to the medical records?

They stay where they are. Medical records must be preserved under the Patient Data Act and are archived in or out of the old record system according to a separate plan. Replacing the operational and ordering system does not touch the records at all.

Do the client companies have to do anything?

Yes, one thing: start using the new way in. That is why communication to their orderers is the single most important point in the plan: new logins sent out in good time, and a clear first day when orders go through the new system.

See Portway in your everyday work.

We show Portway with what you do today, so you can see what would take care of itself at your place.