Short answer: technically, moving from a fax machine to online fax takes an afternoon. In human terms, allow four weeks for a team of five or six administrative staff to stop walking down the corridor to the dead machine. The plan comes down to four milestones: week 1, map who sends what and to whom; week 2, write a one-page procedure and hand out access; week 3, run the new tool alongside the old one, with a designated champion; week 4, unplug the old machine and handle the remaining edge cases. What makes a migration fail is almost never the technology — it is the absence of a written procedure and shared access to a mailbox nobody checks.
Most guides stop the moment the first fax goes out from a browser. That is precisely where the real problems begin: the assistant who sends from her personal address and goes on holiday with the entire history, the accountant who cannot find the transmission report for a disputed invoice, the intern who scans a whole file at 600 dpi in colour and clogs the sending queue. Nothing dramatic, but enough for someone to say "it was simpler before" after three weeks — and for management to seriously consider buying another fax machine.
What the fax machine did without anyone noticing
Before training anyone, you need to understand what you are taking away. A paper fax machine sitting in a corridor performed four invisible functions that online fax does not reproduce on its own.
It was a physical collection point. Everyone knew where to go and pick up an incoming document. Nobody needed a login. The output tray acted as a shared inbox, with its advantages (zero friction) and its major flaws (anyone could read anything — which, in 2026, no longer passes muster under the GDPR).
It produced tangible proof. The transmission report came out printed, you stapled it to the file, case closed. Online, the proof exists but it sits in an email or an account history: you still have to tell the team where it is and what to do with it.
It enforced a format. One A4 sheet, in black and white, fed through a document feeder. Sending a 40 MB colour PDF was impossible. The physical constraint acted as a safety rail; online fax, by contrast, will accept anything you throw at it and then fail silently.
It concentrated institutional memory. Frequently used numbers were programmed into speed dial, often by a single person who has long since retired. That list disappears with the machine if nobody copies it out before disposal.
A successful migration means rebuilding those four functions through explicit rules. That is what the training is really about.
Week 1 — Map actual usage
Don't start from the hardware, start from the flows. For five working days, ask everyone to log every send and every receipt — on a simple sheet taped next to the fax machine or in a shared spreadsheet: recipient, document type, urgency, page count.
The results are almost always surprising. At an insurance brokerage we worked with, out of 63 outgoing faxes in one week, 41 went to just four recipients (two insurance companies, a claims department, a loss adjuster). The remaining 22 were scattered. The operational conclusion: training should first industrialise the four recurring recipients; the rest is handled case by case.
Also ask three questions out loud in a team meeting:
- Who receives what? A fax from occupational health should not land in the same inbox as a supplier purchase order.
- What delay is acceptable? An urgent information request does not follow the same rules as a monthly statement.
- Who needs access to the history? This is the question that determines access rights, and it is rarely asked before a dispute arises.
Use this week to copy out the machine's directory. On most models, you can print the list of speed-dial numbers from the configuration menu; failing that, photograph the screen, number by number. This thankless little task saves you six months of "you wouldn't happen to have the court registry's fax number, would you?".
Week 2 — A one-page procedure, not a 40-page manual
Documentation that works fits on one side of A4, posted near the workstations and saved in the shared drive. Beyond that, nobody reads it.
Structure it in four blocks.
1. Sending
Log in to the service → enter the country code then the number without the leading zero → attach the PDF → check the cover page → send → file the transmission report in the client folder.
Two details deserve to be spelled out because they cause 80% of failures: international dialling (country-code errors remain the leading cause of failed sends outside France, a topic we cover in our guide to sending faxes abroad) and file quality. Restate the rule: PDF, black and white, 200 to 300 dpi, no full-page images.
2. Receiving
Specify the shared functional mailbox address — never a personal address — and the person responsible for checking it, plus a backup. A mailbox along the lines of fax@your-firm.com fed by the service, with two or three internal recipients, instantly solves the holiday problem.
3. Filing
Where does the document go? Under what name? How long do you keep it? A simple convention such as YYYY-MM-DD_sender_subject.pdf is enough, provided everyone uses the same one.
4. What to do when it fails
Three lines: check the number, retry once, then switch to another channel and inform the recipient by phone. Without that last instruction, a failed send can sit unresolved for days.
Print the procedure and slip it into a wall-mounted A4 document holder above the workstation: what is posted gets read, what sits in a shared folder gets forgotten.
Week 2b — Access rights, the part everyone rushes
This is where a GDPR audit invariably finds something. The paper fax machine was a confidentiality hole, but a visible one. Online fax shifts the risk onto accounts and mailboxes, where it becomes invisible — and lasting.
Three simple rules.
A functional mailbox, not a personal address. If incoming faxes arrive at marie.dupont@…, you have created a dependency on one individual and a risk of uncontrolled access the day she leaves the company.
Named accounts for sending. Every employee who sends must be identifiable in the history. That helps in a dispute, and it lets you revoke access in a minute when someone leaves.
A written retention period. Data protection authorities regularly remind organisations that retention must be limited to what is necessary for the purpose of the processing: a summons received by fax has no business lingering in a mailbox for three years. Set a duration per document category and purge accordingly.
If incoming documents contain sensitive data — health information, ID documents, bank details — reading them on screen in an open-plan office is a genuine problem. A privacy screen filter on reception workstations costs about as much as lunch and settles the over-the-shoulder issue. We cover the other obligations in our article on fax and the GDPR.
Week 3 — The parallel run, with a designated champion
For one full week, both systems run side by side. The fax machine stays plugged in, the online service is live, and the instruction is clear: send via the online service first, keep the old machine as a safety net.
This week serves three purposes.
Spotting problem correspondents. Some recipients have ageing or poorly configured VoIP setups. Within a few days you will identify the two or three numbers that cause trouble, and you can handle them separately.
Bringing out the "silly" questions. "Do I need to put +33?" "What if the document is 30 pages?" "How do I know it went through?" These questions never come up during a demo; they come up on a Tuesday at 5:40 p.m. with an urgent send to make. Hence the second point.
Appointing a champion. One person on the team — not necessarily the most tech-savvy, rather the one people already turn to — becomes the internal point of contact. They test, they answer, they escalate blockers. Change lands far better when the answer comes from a colleague than from a management memo.
On the hardware side, week 3 almost always exposes a weak link: the scanner. An older multifunction device produces heavy, grey PDFs that fail in transmission. If your volumes are steady, a compact duplex scanner with automatic document feeder radically improves send quality — and eliminates the main cause of unreadable faxes. Failing that, a mobile scanning app on a smartphone, with perspective correction and black-and-white output, does the job perfectly well for a few pages.
Week 4 — Cut the cord and handle what's left
Unplug the fax machine. Not "put it on standby": unplug it, and remove the line from the wall if it is still active. As long as the machine is there, part of the team will keep using it on the sly — that's human nature, and it's what drags migrations out to eighteen months.
Three categories of cases then remain.
| Case | Symptom | Fix |
|---|---|---|
| Unreachable correspondent | Consistent failure on one specific number | Call them, ask for an alternative channel, record the solution in the shared directory |
| Oversized document | Send rejected or extremely slow | Rescan in black and white at 200 dpi, split into two sends |
| Unchecked inbox | An incoming document goes unprocessed | Appoint a backup checker and add a daily reminder |
Above all, send a letter or email notice to your regular correspondents: "our fax number remains 0X XX XX XX XX; our outgoing faxes now come from an online service". Two lines that prevent a surprising number of verification calls, particularly from administrative departments used to recognising a machine header.
Finally, don't just bin the old device: its memory may still hold pending pages. Wiping the memory via the configuration menu, then dropping it at a WEEE collection point or handing it back to the reseller — as environmental agencies recommend for professional electronic equipment — is the only clean way out.
The four mistakes that crop up in every migration
Training only the "main users". The day the assistant is away, it's the accountant or the manager who has to send. Train everyone, even superficially.
Not writing the procedure down. A twenty-minute verbal demo evaporates in three days. A posted A4 sheet survives for years.
Mixing fax with personal email. This is the most tempting shortcut and the most expensive. A functional mailbox from day one, no exceptions.
Forgetting mobile. A share of sends happens off-site: a construction site, a courthouse, someone's home. Make sure everyone knows how to send from a phone, and pack a smartphone power bank in the bags of your mobile staff — the urgent send from a car park at 6 p.m. with 4% battery is a classic of the genre. We have devoted an entire guide to sending faxes while working remotely.
Frequently asked questions
How long does it really take to train a small team?
Allow 45 minutes for a group presentation followed by informal support spread over three weeks. The presentation alone is not enough: it's the five or six questions asked in real situations that embed the habit. For a team of more than fifteen people, run the session twice and appoint a champion per department.
Should you keep the fax machine "just in case"?
No, and this is the most common mistake. Keeping an analogue line costs a monthly subscription, creates a false sense of security and slows adoption. If you really want a safety margin, keep the device unplugged for a month, with no line, then dispose of it.
How do you prove a document was actually transmitted?
Keep the transmission report (date, time, number dialled, page count, status) and file it with the document sent, in the same folder. It is that pairing — document plus report — that carries evidential weight in a dispute, as we explain in our analysis of the legal validity of fax.
What if a correspondent refuses online fax?
Technically, they cannot tell it apart from a conventional send: the document arrives on their fax machine in exactly the same way. Refusals actually come down to the header or the number displayed. Check that your sending number is genuinely yours and that the header shows your registered company name.
What about the fax numbers stored in the old machine?
Print the list from the configuration menu before unplugging it, then copy it into a shared directory in spreadsheet format, with a "last used" column. You will discover that half the entries are obsolete.
Summary
- Week 1: measure actual flows over five days, copy out the machine's directory.
- Week 2: write a single-side A4 procedure (send / receive / file / what to do if it fails), create a functional mailbox and named accounts.
- Week 3: parallel run with both systems, a designated champion, fix the scanning chain.
- Week 4: unplug for good, handle residual cases, notify regular correspondents.
- Three permanent rules: never a personal address for incoming faxes, always file the report with the document, a written retention period per document category.
- The number is portable, the machine gets scrapped, but the procedure is what gets passed on: it is what makes the migration irreversible.
To check coverage before rolling out more widely, see the list of supported countries, and try a first send from the home page form. The most common questions are gathered in our FAQ, and receiving setup is detailed on the receive a fax page.
Tagsfaxplatformpaperlesssecurity
