A single-site organization with four fax numbers does not need a roadmap. It needs a plan, and the migration article is that plan.
A roadmap is for the other case: several sites, numbers spread across carriers, a records system in the middle, and a decision that has to survive a budget cycle and a couple of people changing jobs. This sets out what such a roadmap contains, what each phase has to produce before the next one starts, and where the decision points genuinely are.
Start with the decision, not the plan
The first question is not how to move. It is whether to.
There are three honest answers, and only one of them leads to a fax program:
Retire the channel. If every counterparty would accept a portal or secure email and fax persists from habit, the right project is removing fax, not modernizing it. It is a bigger project and a better one.
Keep it and modernize it. The usual answer. Counterparties in healthcare, legal, financial services and government require fax, and that is not yours to overrule.
Do nothing yet. A legitimate answer if the machines work, the lines are cheap and nothing is changing. It stops being legitimate the moment a phone system moves to VoIP, because that is when fax reliability degrades on its own.
Write down which of the three you are choosing and why. Six months later, when someone asks why this is on the plan at all, that sentence is the whole justification.
The four phases
Each produces something specific. A phase that produces a status update rather than an artifact has not finished.
Phase 1: Establish the facts
Produces: an inventory and a volume baseline.
Every number, where it terminates, what it is used for, whether it appears on anything printed or filed, and which carrier account it sits on. Two months of page volumes, inbound and outbound counted separately. The counterparties that matter most. Where each document has to end up.
This phase is unglamorous and it determines everything downstream, including the timeline: because it is what tells you how many carriers you are negotiating ports with.
Phase 2: Establish the constraints
Produces: a shortlist and a signed-off requirement.
Constraints first, cost second. Anything that cannot port your numbers, cannot sign the agreements you need, or cannot say how it handles fax over IP is out rather than cheaper. Retention policy is decided here, not later, because it sizes storage and it is a policy question rather than a technical one.
The output is a short requirement your legal, clinical or compliance people have actually read. What to Look For in Electronic Fax is the question set.
Phase 3: Prove it on your own traffic
Produces: evidence, or a changed decision.
A proof of concept on one site, with real documents to real counterparties. It must include a long document and a poor-quality scan, because those are what fail and they fail at the far end, which no demonstration environment reproduces.
This is the phase most often skipped and the one that most often changes the plan. It is also where an integration reveals whether it is a product or a project.
Phase 4: Roll out in waves, retire last
Produces: ported numbers and canceled lines.
Sites or functions in waves, receiving before sending, porting behind that, hardware retired deliberately at the end. A wave that goes wrong should affect one group and be recoverable.
The program is not finished when the service is live. It is finished when the analog lines are canceled, and that step is the one that quietly never happens.
Decision gates worth defending
Three points where it is reasonable to stop, and naming them in advance is what makes stopping possible rather than embarrassing.
After Phase 1. If the inventory shows fax volume is negligible and the counterparties would accept another channel, retire instead. Finding this out costs two weeks.
After Phase 2. If no provider meets the constraints at a tolerable price, the honest outcome is to keep the machines and revisit. That is a result, not a failure.
After Phase 3. If the proof of concept fails on the counterparties that matter, do not roll it out and hope. It fails the same way at scale, with more numbers already ported.
What tends to be underestimated
Porting lead time. The only item on the plan whose date is not in your gift.
The last mile. Getting faxes into the system where the work happens. Email delivery is included everywhere; anything else is scoped work and belongs on the plan as its own line with its own estimate.
The retirement. Canceling lines requires knowing which account each sits on, which is Phase 1 again, and why Phase 1 is worth doing properly.
Retention. Turning a paper channel into a document archive creates a records obligation. Cheap to plan, awkward to discover.
Who has to be in the room
Fewer people than a typical program, but the specific ones matter: whoever owns the telephony accounts (they hold the porting information), whoever owns the records or clinical system (they own the last mile), and whoever signs the agreements, a Business Associate Agreement or a data processing agreement is not an IT signature. The people who actually send faxes should see Phase 3, because they will tell you within a day what the workflow gets wrong.
A note on the numbers in a business case
A roadmap usually needs a cost justification, and this is where these documents most often go wrong, a benchmark saving gets borrowed from a vendor page and becomes a commitment somebody is later held to.
Use your own figures. Measuring the Value of Electronic Fax sets out which are collectable and which are not, and the plan prices are published on the pricing page. We will not supply a benchmark saving for your organization, because we would be inventing it.
Where to go next
Migrating from Fax Machines to Cloud Fax is the execution detail behind Phases 3 and 4. Electronic Fax Security and Risk covers the constraints that shape Phase 2, and Guide to Electronic Fax is the overview.
Our own next step is deliberately Phase 3 shaped: we will put together a proposal against your inventory and run a proof of concept on real traffic before anyone commits. Tell us what you are working with.
Sources
- 47 CFR Part 52, Subpart C: number portability, Electronic Code of Federal Regulations.
- ITU-T Recommendation T.38: real-time Group 3 facsimile over IP networks.