Every fax migration has the same fear at its center: that something important will stop working and nobody will notice until a clinician, a customer, or a regulator does. The old system, whatever its flaws, has a track record. The new one does not. Moving from one to the other is a leap unless there is a way to make it gradual.
Parallel operation is that way. It means running the existing system and the new platform at the same time, for long enough to confirm that the new one handles everything the old one did, before the old one is retired. It adds some effort and a bit of cost, and it removes most of the risk. This post explains how it works and how to use it well. It builds on the post on how to migrate from a legacy fax server to Passport without disrupting operations.
What Parallel Operation Looks Like
In a parallel run, both systems are live. Depending on the migration, that can mean:
- New users or pilot groups work on the new platform while everyone else stays on the old one
- Fax numbers are ported in stages, so some route to the new platform and others still route to the old one
- Outbound traffic is moved workflow by workflow, with the previous method available as a fallback
- Inbound numbers are tested on the new platform before the production cutover
The exact design depends on your environment. The principle is constant: at no point is there a gap during which a critical workflow depends on something unproven.
Why Number Porting Makes It Essential
Fax numbers are not just settings. They are embedded in the directories and systems of other organizations, as the post on why fax number porting matters explains. When a number is ported, the transfer happens between carriers over a period of time. During that window, you want to be certain that faxes sent to the number reach somewhere that someone is watching.
Parallel operation gives you that certainty. The old system stays available until you have confirmed that the ported number is receiving correctly on the new platform. Without it, an incomplete port can cause a silent gap: senders get no answer and have no idea where else to send.
What to Validate Before You Cut Over
The purpose of the parallel period is to gather evidence. A useful checklist:
- Inbound. Every number receives faxes on the new platform and routes to the correct queue. Test from multiple sources, including a traditional fax machine and a cloud sender, as the post on what happens when the receiving side has no internet connection describes for analog destinations.
- Outbound. Transmissions reach real destinations, including your highest-volume partners, with delivery confirmation recorded.
- Routing. Workgroup rules behave as designed for each workflow, including after-hours rules.
- Integrations. Connections to the EHR, LIS, or other systems send and receive correctly, using real or realistic documents.
- Failure handling. Failed transmissions are flagged and retried as expected. The post on how Passport handles failures and retries describes the behavior to test against.
- Access and permissions. Users see the queues they should and nothing else.
- Monitoring. Administrators can see activity in the Enterprise Status Manager.
- Peak periods. The platform performs correctly during your busiest hours, not just on a quiet afternoon.
Write down the results. That record becomes your evidence for the go or no-go decision and part of your compliance documentation.
How Long It Lasts
There is no universal answer, and a single number would be misleading. The duration depends on the number of sites, the number of fax numbers, the complexity of routing, the integrations involved, and how quickly the validation criteria are met. The FAQ Friday on how long it takes to onboard a new site to Passport covers the variables that affect timing. A sensible approach is to define exit criteria in advance, such as a set of validated workflows and a period of clean operation, and end the parallel period when those are met rather than on a fixed date.
Common Mistakes
A few patterns recur in migrations that go less smoothly:
- Cutting over too early because the project is behind schedule. The parallel period is not the place to save time.
- Testing only the easy workflows. The unusual ones, such as overnight results or a payer that uses an older fax machine, are the ones most likely to fail.
- Letting the old system drift. If users continue sending from the old system after the new one is meant to be primary, you end up with traffic in both places and an incomplete audit trail.
- Decommissioning without a rollback plan. Keep the old system recoverable for a defined period after cutover.
- Forgetting the people. Staff need to know which system to use and when. The post on how to configure Passport for a new site describes the onboarding process that supports that.
Compliance During the Overlap
During a parallel run, you are operating two fax environments, each of which carries PHI. Both need to meet your security and compliance requirements for the duration. That means confirming Business Associate Agreement coverage for the new platform before live traffic moves, maintaining access controls on both, and preserving the audit trail from the old system according to your retention policy. The post on how to create a fax retention policy that meets compliance standards is a useful reference for what to keep from the old environment.
Knowing When You Are Done
The cutover decision is easier when it is based on a short, specific list: all numbers confirmed on the new platform, all priority workflows validated, integrations working, failure handling proven, monitoring in place, users trained, and the rollback plan documented. When every line is checked, retiring the old system is a controlled step instead of a leap.
Schedule a strategy call with the Lane team to discuss how a parallel run would work in your migration.



