Moving from fax machines to a cloud service is not a software rollout. Most of the work is in the numbers, the counterparties and the habits, and the part that determines your timeline is almost entirely outside your control.
This is how the migration actually goes, including the failures that are common enough to plan around.
What actually has to move
Four things, and only one of them is technical.
The numbers. Every fax number you publish is a dependency you do not own outright. Some can be retired; the ones printed on forms, referral pads, contracts or a license have to keep working, which means porting them rather than replacing them.
The workflows. A fax arrives and then something happens to it. It goes in a chart, a case file, a claims queue, a folder on a shelf. Cloud fax changes where the document lands, so every one of those onward steps needs a new starting point.
The hardware. Machines, the analog lines they sit on, and whatever maintenance contract covers them. Retiring these is where the saving is, and it is the step most often left half-done.
The habits. People who currently walk to a machine will need a different action. This is not a training problem so much as a “where did my fax go” problem, and it is worth answering before it is asked.
Before you start
Four inventories. None takes long, and skipping any of them is what turns a two-week migration into a two-month one.
Every fax number, and what depends on it. Number, location, what it is used for, and whether it appears on anything printed or filed with anybody. Mark which must port and which can be retired. That distinction sets the critical path.
Real page volumes, inbound and outbound separately. Two months of transmission logs or line bills. This selects the plan, and estimates are routinely wrong by a factor of several.
The counterparties that matter most. The hospital, the claims processor, the court, the county office. These are the transmissions you will test with, because they are the ones that fail.
Where each document has to end up. If the answer is email, you are done. If it is a records system or a line-of-business application, that is an integration and it needs scoping as its own piece of work rather than assuming into the go-live date.
Number porting is the critical path
Porting is a request to a losing carrier, and it moves at their pace. In the United States local number portability obligations sit in 47 CFR Part 52, Subpart C; in practice what governs your date is the state of the account the number sits on.
Three things reliably delay it, and all three are avoidable:
- The account details do not match. The port request has to match the losing carrier's records exactly: account number, service address, authorized name. A mismatch is rejected and the clock restarts.
- The number is bundled. A fax line sold as part of a package can need the package unpicked first.
- Nobody knows who the account is with. More common than it sounds where a line has been in place for a decade.
Start porting first, and sequence everything else behind it. A number cannot be hurried, and every other step can.
A sequence that works
Receive before you send. Point inbound faxes at the service while the machines are still in place. Nothing is at risk: if the service is misconfigured, you find out on a document you can also collect from the machine. This single ordering removes most of the fear from the project.
Then send, from a small group. A handful of people, sending real documents to real destinations, for a week or two. Include a long document and a poor-quality scan: those are what fail, and they fail at the far end where no demonstration environment reproduces them.
Then port, in waves. Numbers grouped by site or by function, not all at once. A wave that goes wrong affects one group and is recoverable.
Then retire the hardware. Deliberately, and last.
Run both in parallel through at least one full cycle. If your volumes are seasonal: open enrollment, term start, month end, overlapping the busy period is worth the duplicated cost.
What goes wrong
The machine stays plugged in. Faxes keep arriving on it, nobody notices for weeks, and the line rental keeps being paid. Unplug on a planned date, not when someone gets round to it.
An unlisted number. Discovered when a counterparty says they have been faxing for a month with no reply. This is the inventory step earning its keep.
Delivery to a person, not a role. Faxes routed to an individual's mailbox stop when that person leaves or takes leave. Route to a shared destination from the start.
Silent failures. With a machine, a failed fax produced a piece of paper somebody saw. If nobody is watching the transmission reports, the same failure is now invisible. Decide who reads them before go-live.
The last mile is a project. “It also needs to go into our records system” arrives late and is treated as a small ask. It is not.
Retention was never decided. Every fax is now a stored document, and storage without a retention policy is an obligation accumulating quietly.
Retiring the hardware
Cancel the analog lines only after the numbers on them have ported and settled, canceling a line with an unported number on it can lose the number permanently. Then the machines, the maintenance contract and the consumables.
One thing worth doing properly: a fax machine has a memory and often a hard drive, and it has been storing documents. Dispose of it the way you would dispose of any device that has held sensitive material, not the way you would dispose of a printer.
How long it takes
Setting up the service is same-day. Testing is a week or two. Porting is the variable, and it is measured in weeks rather than days for reasons that sit with the losing carrier. Integrations are scoped separately and can be the longest item on the list.
We are not going to put a single number on your migration, because it depends on how many carriers your numbers are spread across, which is not something either of us knows until the inventory is done.
Where to go next
What to Look For in Electronic Fax is the list of questions to ask before you commit, several of which are about migration. How Much Does Electronic Fax Cost? covers the budget, and Guide to Electronic Fax is the whole subject.
If you would like the inventory done with you rather than by you, send us your number list and page volumes and we will tell you what ports, what does not, and what sits on the critical path.
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.