How to Use WestFax as Your RightFax Fax Transport Layer
Keep the RightFax server your team already knows. Move only the transport to WestFax and retire the fax boards and analog lines — no rip-and-replace.
You can keep your RightFax server exactly as it is and change only what carries the faxes. In a transport-only migration, the fax boards, analog or PRI circuits, or cloud transport service you use today drop out of the picture and your faxes ride the WestFax Transport Network instead. RightFax, your users, your routing rules, and every workflow built around them stay exactly where they are.
There is no WestFax software to install on the fax server and no additional WestFax product to license. It is a configuration change, and our team walks you through it. This guide covers what a transport-only migration changes, what it leaves alone, and how to start one.
Next step See what this looks like on your setup. Tell us what you’re running todayWhy organizations move the transport first
Most RightFax administrators we talk to are not unhappy with RightFax. They are unhappy with what sits underneath it.
- The hardware is aging out. Fax boards fail, spares get harder to find, and the servers they live in come due for replacement on a cycle nobody enjoys budgeting for.
- The copper is going away. Analog and PRI circuits are being sunset by carriers across the country, and renewal quotes keep climbing for a service that is being retired.
- Cloud transport is expensive. Getting off the hardware should not mean signing up for a transport bill that costs more than the boards did.
- A full migration is a big project. Replacing a fax server means retraining staff, rebuilding integrations, and re-validating workflows. That is a real project with real risk, and it is rarely the first thing an IT team wants to take on.
Moving the transport first solves the urgent problem of the hardware and the phone lines without taking on the big project. The fax server stays. The workflows stay. Only the path the faxes take changes.
What stays the same
A transport-only migration is deliberately narrow. These do not change:
- Your RightFax server and version. No upgrade, no reinstall, no migration of the fax server itself.
- Your users and their clients. Nobody learns a new tool, a new address, or a new process.
- Your routing rules and DID mapping. Inbound faxes keep landing where they land today.
- Your integrations. Whatever hands documents to RightFax today keeps doing it: your EHR, ERP, document management system, MFPs, scripts, or print paths.
- Your administration and reporting. Same console, same queues, same audit history.
- Your fax numbers. Numbers can be ported to WestFax as part of the move; we port as an FCC-licensed carrier, not as a reseller.
What changes
One thing: how faxes get from your fax server to the outside world, and back.
Outbound faxes leave over the WestFax Transport Network. Inbound faxes arrive over it and are handed to RightFax the same way they are today. Once that path is live and proven, the fax boards, gateways, and analog or PRI circuits can be taken out of service on your schedule, not ours.
What you get on the WestFax Transport Network
The transport is our core competency, not a feature bolted onto a SaaS app. We have been building and operating it for more than 26 years.
- Two transports, one decision engine. We run the largest TDM fax network in the world alongside an elastic SIP network, and we choose between them per recipient based on 26 years of delivery history. Most providers run a single transport and hope for the best.
- No baud-rate caps. Many cloud fax providers cap transmissions at 9,600 baud. We run all the way up to full Group 3 and V.34 super-G3 speeds of 33,600 baud. Faxes spend less time on the line, so more of them complete, and long, dense documents that would otherwise time out get through.
- No least-cost routing. We own and operate the network and connect as a carrier, with direct interconnects rather than a chain of resold wholesale gateways. We never degrade a transmission to protect our own margin.
- Reliability you can put in a contract. A 99.999% uptime SLA, redundant carrier paths, geographic redundancy, and automatic reroute if a route degrades mid-flight.
- Greater than 97% first-attempt deliverability on valid fax numbers, with retry counts, intervals, and timing you control.
- Built for compliance. HIPAA compliant with a BAA available, HITRUST R2 certified, SOC 2 Type II audited, and PCI DSS. See Security & Compliance for the full list.
There is more detail on all of it on the WestFax Transport Network page.
Prove it first Run your own traffic before you commit. We’ll test a slice against your current transportMove in stages, or stop after the transport
Transport-first is a complete answer on its own, and it is also a safe first phase if you expect to modernize further later.
Phase one: the transport. Retire the boards and the phone lines. Keep RightFax. This is the phase that solves the hardware and circuit problem, and for a lot of organizations it is the only phase they ever need.
Phase two, if and when you want it. If you later decide to move off the fax server, Cloud Fax Toolkit can pick up the integration patterns that ran through it (drop folders, AutoPrint, MFP workflows, directory synchronization, inbound file delivery) so you can retire the server without rebuilding every workflow.
To be clear: phase two is optional. Staying on RightFax indefinitely and using WestFax purely as the transport underneath it is a supported, permanent arrangement, not a waypoint. Plenty of organizations have made significant investments in RightFax customization and have no reason to walk away from them.
What setup looks like
This is a guided setup, start to finish. You are not handed a PDF and wished luck.
- A short discovery call. We go over your RightFax version, roughly how many channels you run, your volume, and how faxes leave the building today.
- We confirm the right configuration for your environment. Our team determines exactly what needs to change on your side and what we provision on ours.
- We provision your numbers and routes. Including porting existing numbers where that applies.
- We test against real traffic. We can run a slice of your actual fax volume alongside your current transport and compare completion rates, transmission speed, and cost per delivered fax on your destinations, not a demo.
- You cut over on your schedule. Then the boards and circuits come out of service whenever you are ready.
Because the specifics depend on your version, channel count, and environment, we work through them with you directly rather than publishing a one-size-fits-all procedure.
Ready when you are Get your transport migration scoped. Send your RightFax version and channel countFrequently asked questions
Yes. That is exactly what a transport-only migration is. Your RightFax server, users, routing rules, integrations, and administration stay as they are; only the path faxes take to and from the public network changes.
No. Retiring fax boards, gateways, and the analog or PRI circuits behind them is the usual reason organizations do this. Once the WestFax transport is live and proven, that hardware can be taken out of service.
No. There is no WestFax software to install on the fax server and no additional WestFax product to license for a transport-only migration.
They should not. Users keep the same client, the same process, and the same fax numbers. There is nothing to retrain.
Both are supported. Many organizations move the transport and stop there permanently. If you later want to retire the fax server itself, Cloud Fax Toolkit can preserve the integration patterns that ran through it so you do not have to rebuild every workflow.
Yes. WestFax is HIPAA compliant and a BAA is available on every plan. WestFax is also HITRUST R2 certified, SOC 2 Type II audited, and PCI DSS compliant.
It depends on your environment and whether you are porting numbers. The configuration work itself is short; number porting is usually what sets the timeline. We give you honest dates during discovery rather than optimistic ones.
Transport pricing depends on your volume and channel count, so we quote it after discovery. For most organizations the comparison that matters is real cost per delivered fax against what fax boards, circuit renewals, and maintenance cost today. Talk to our team for a number on your volume.
Trademark and affiliation notice. RightFax and OpenText are trademarks or registered trademarks of Open Text Corporation. WestFax is not affiliated with, endorsed by, sponsored by, or otherwise associated with Open Text Corporation, and this guide is not official OpenText documentation. Product names are used solely to identify the systems this guide applies to.
Compatibility depends on your environment. Not every RightFax version, configuration, or deployment supports a transport-only change, and some environments may need an upgrade or a different approach. We confirm what is possible for your specific setup during discovery, before anything changes.
Changing how your fax server connects to the public network may affect your existing support, licensing, or maintenance agreements. Review your agreements with your fax server vendor or reseller before making changes.
All other product names, logos, and trademarks are the property of their respective owners.
