Technology Advice for Small Businesses

powered by Pronto Marketing

The hidden costs of cloud migration: Why data portability matters on day one

The real price of a cloud platform includes the cost of leaving it. If you wait until your contract ends to test your exports and tally exit fees, you may already be locked in. Find out how to check your data formats, spot what you depend on, and estimate switching costs before you make your next cloud investment.

What is cloud data portability?

Cloud data portability means you can move your data from one cloud service to another, or back to your own systems, and still use it when it gets there. Getting your files out is only half the job. They also have to work in the new system. The international standard ISO/IEC 19941 breaks portability into three parts:
  • Format: Can the new system open the files?
  • Meaning: Does the new system understand what each piece of data represents?
  • Rules: Do the policies attached to your data, such as how long you keep it and who can see it, come along too?
A move can pass the first test and still fail the other two. Your data arrives, but it’s confusing, incomplete, or less secure than before.

Why should portability be a selection criterion?

The cost of leaving a cloud provider is part of the cost of choosing one. If you only compare today’s prices, you’re missing part of the bill. NIST, the US standards body, makes this point in its cloud guidance. It says you can only know whether the cloud saves you money once you count all the costs, including the cost of moving away later. UK regulators agree that leaving can be hard. In July 2025, the Competition and Markets Authority concluded that fees for moving data out, along with systems that don’t work well together, make it harder for customers to switch providers or use more than one. In short, a platform that’s cheap to join can be expensive to leave.

Which export formats should you ask about?

Ask each provider exactly what format your data will come out in. Then ask whether that format is open, well documented, and usable without the provider’s own software. This matters because an export can meet the wording of your contract and still be hard to use anywhere else. NIST warns that export formats often don’t match between software platforms. It also notes that custom workflows, business rules, settings, and scripts are often built for one provider only. Don’t take the provider’s answer at face value. During your trial, export a sample of your data and load it into another tool. You’ll quickly see what makes it through and what gets lost.

Will your metadata survive an export?

Metadata is the information that describes your data, and it can decide whether your exported data is still useful. Think of timestamps, owners, permissions, version history, tags, and the links between records. Lose these details and you can lose your audit trails and access controls too. That leaves you with gaps in your records and weaker security on the new platform. Lawyers at DLA Piper note that in complex cloud services, the line between your data, its metadata, your settings, and system logs isn’t always clear. So get it in writing. Ask the provider which metadata you can export and in what format, then check it in your test export.

How to map migration dependencies

Your data rarely stands alone. It’s usually tied to other tools, logins, automations, and services that only work on one provider’s platform. Every one of these will need to be rebuilt or replaced if you leave, which means together they decide how long and how hard a move will be. Start by listing:
  • Every integration with other software
  • How users sign in and get access
  • Automated tasks and workflows
  • Any services unique to the provider
NIST adds two more things to watch. Providers usually keep the right to change or remove the connections other systems rely on. Also, large exports can take a long time over a slow network. Write down which of your systems connect to the provider, and estimate how long a full export would take on your connection.

How to estimate future switching costs

To estimate switching costs, add up everything it would take to leave: transfer fees, staff time, months of paying for two platforms, contract penalties, and retraining. Doing this before you sign gives you a fair way to compare providers whose prices look alike today.
Cost What to check
Data transfer fees Exit fee waivers and their conditions
Notice and transition How long the contract allows for exit
Early termination Penalties for leaving mid-term
Parallel running Months of paying for both platforms
Labor Rebuilding integrations and testing
The rules are starting to change in some markets. According to DLA Piper, the EU Data Act will stop providers serving EU customers from charging switching fees, including fees for moving data out, from January 12, 2027. But DLA Piper also points out that providers’ own fee waivers often come with conditions. Read the fine print closely. Before you sign, ask every provider on your shortlist to answer your questions on formats, metadata, and exit costs in writing.

Keep your options open

The best time to plan your exit is before you commit. Our cloud advisory team can help you test your exports, map what your data depends on, and estimate the true cost of switching, so you can choose a platform without getting locked in. Talk to our team today to check your portability before you sign.

Assessing cloud portability: Your migration and exit strategy checklist

Moving your data out of the cloud should be part of your buying decision, not an afterthought. Before you sign, look at what you’ll be able to take with you, what leaving will cost, and how long you’ll pay for two systems at once. New rules such as the EU Data Act will remove some switching fees by 2027, so compare vendors carefully. Use this checklist to evaluate portability before you sign.

What is cloud data portability?

Cloud data portability means you can move your data from one cloud service to another, or back to your own systems, and still use it when it gets there. Getting your files out is only half the job. They also have to work in the new system. The international standard ISO/IEC 19941 breaks portability into three parts:
  • Format: Can the new system open the files?
  • Meaning: Does the new system understand what each piece of data represents?
  • Rules: Do the policies attached to your data, such as how long you keep it and who can see it, come along too?
A move can pass the first test and still fail the other two. Your data arrives, but it’s confusing, incomplete, or less secure than before.

Why should portability be a selection criterion?

The cost of leaving a cloud provider is part of the cost of choosing one. If you only compare today’s prices, you’re missing part of the bill. NIST, the US standards body, makes this point in its cloud guidance. It says you can only know whether the cloud saves you money once you count all the costs, including the cost of moving away later. UK regulators agree that leaving can be hard. In July 2025, the Competition and Markets Authority concluded that fees for moving data out, along with systems that don’t work well together, make it harder for customers to switch providers or use more than one. In short, a platform that’s cheap to join can be expensive to leave.

Which export formats should you ask about?

Ask each provider exactly what format your data will come out in. Then ask whether that format is open, well documented, and usable without the provider’s own software. This matters because an export can meet the wording of your contract and still be hard to use anywhere else. NIST warns that export formats often don’t match between software platforms. It also notes that custom workflows, business rules, settings, and scripts are often built for one provider only. Don’t take the provider’s answer at face value. During your trial, export a sample of your data and load it into another tool. You’ll quickly see what makes it through and what gets lost.

Will your metadata survive an export?

Metadata is the information that describes your data, and it can decide whether your exported data is still useful. Think of timestamps, owners, permissions, version history, tags, and the links between records. Lose these details and you can lose your audit trails and access controls too. That leaves you with gaps in your records and weaker security on the new platform. Lawyers at DLA Piper note that in complex cloud services, the line between your data, its metadata, your settings, and system logs isn’t always clear. So get it in writing. Ask the provider which metadata you can export and in what format, then check it in your test export.

How to map migration dependencies

Your data rarely stands alone. It’s usually tied to other tools, logins, automations, and services that only work on one provider’s platform. Every one of these will need to be rebuilt or replaced if you leave, which means together they decide how long and how hard a move will be. Start by listing:
  • Every integration with other software
  • How users sign in and get access
  • Automated tasks and workflows
  • Any services unique to the provider
NIST adds two more things to watch. Providers usually keep the right to change or remove the connections other systems rely on. Also, large exports can take a long time over a slow network. Write down which of your systems connect to the provider, and estimate how long a full export would take on your connection.

How to estimate future switching costs

To estimate switching costs, add up everything it would take to leave: transfer fees, staff time, months of paying for two platforms, contract penalties, and retraining. Doing this before you sign gives you a fair way to compare providers whose prices look alike today.
Cost What to check
Data transfer fees Exit fee waivers and their conditions
Notice and transition How long the contract allows for exit
Early termination Penalties for leaving mid-term
Parallel running Months of paying for both platforms
Labor Rebuilding integrations and testing
The rules are starting to change in some markets. According to DLA Piper, the EU Data Act will stop providers serving EU customers from charging switching fees, including fees for moving data out, from January 12, 2027. But DLA Piper also points out that providers’ own fee waivers often come with conditions. Read the fine print closely. Before you sign, ask every provider on your shortlist to answer your questions on formats, metadata, and exit costs in writing.

Keep your options open

The best time to plan your exit is before you commit. Our cloud advisory team can help you test your exports, map what your data depends on, and estimate the true cost of switching, so you can choose a platform without getting locked in. Talk to our team today to check your portability before you sign.

Trapped in the cloud: How to avoid vendor lock-in before you sign

Don’t let your cloud provider hold your data hostage. Most platforms let you export it, but that doesn’t mean you can actually use it elsewhere. Proprietary formats and missing details, such as permissions and audit trails, can leave your data useless and your security exposed. Learn how to spot these risks and check your exit options before you commit.

What is cloud data portability?

Cloud data portability means you can move your data from one cloud service to another, or back to your own systems, and still use it when it gets there. Getting your files out is only half the job. They also have to work in the new system. The international standard ISO/IEC 19941 breaks portability into three parts:
  • Format: Can the new system open the files?
  • Meaning: Does the new system understand what each piece of data represents?
  • Rules: Do the policies attached to your data, such as how long you keep it and who can see it, come along too?
A move can pass the first test and still fail the other two. Your data arrives, but it’s confusing, incomplete, or less secure than before.

Why should portability be a selection criterion?

The cost of leaving a cloud provider is part of the cost of choosing one. If you only compare today’s prices, you’re missing part of the bill. NIST, the US standards body, makes this point in its cloud guidance. It says you can only know whether the cloud saves you money once you count all the costs, including the cost of moving away later. UK regulators agree that leaving can be hard. In July 2025, the Competition and Markets Authority concluded that fees for moving data out, along with systems that don’t work well together, make it harder for customers to switch providers or use more than one. In short, a platform that’s cheap to join can be expensive to leave.

Which export formats should you ask about?

Ask each provider exactly what format your data will come out in. Then ask whether that format is open, well documented, and usable without the provider’s own software. This matters because an export can meet the wording of your contract and still be hard to use anywhere else. NIST warns that export formats often don’t match between software platforms. It also notes that custom workflows, business rules, settings, and scripts are often built for one provider only. Don’t take the provider’s answer at face value. During your trial, export a sample of your data and load it into another tool. You’ll quickly see what makes it through and what gets lost.

Will your metadata survive an export?

Metadata is the information that describes your data, and it can decide whether your exported data is still useful. Think of timestamps, owners, permissions, version history, tags, and the links between records. Lose these details and you can lose your audit trails and access controls too. That leaves you with gaps in your records and weaker security on the new platform. Lawyers at DLA Piper note that in complex cloud services, the line between your data, its metadata, your settings, and system logs isn’t always clear. So get it in writing. Ask the provider which metadata you can export and in what format, then check it in your test export.

How to map migration dependencies

Your data rarely stands alone. It’s usually tied to other tools, logins, automations, and services that only work on one provider’s platform. Every one of these will need to be rebuilt or replaced if you leave, which means together they decide how long and how hard a move will be. Start by listing:
  • Every integration with other software
  • How users sign in and get access
  • Automated tasks and workflows
  • Any services unique to the provider
NIST adds two more things to watch. Providers usually keep the right to change or remove the connections other systems rely on. Also, large exports can take a long time over a slow network. Write down which of your systems connect to the provider, and estimate how long a full export would take on your connection.

How to estimate future switching costs

To estimate switching costs, add up everything it would take to leave: transfer fees, staff time, months of paying for two platforms, contract penalties, and retraining. Doing this before you sign gives you a fair way to compare providers whose prices look alike today.
Cost What to check
Data transfer fees Exit fee waivers and their conditions
Notice and transition How long the contract allows for exit
Early termination Penalties for leaving mid-term
Parallel running Months of paying for both platforms
Labor Rebuilding integrations and testing
The rules are starting to change in some markets. According to DLA Piper, the EU Data Act will stop providers serving EU customers from charging switching fees, including fees for moving data out, from January 12, 2027. But DLA Piper also points out that providers’ own fee waivers often come with conditions. Read the fine print closely. Before you sign, ask every provider on your shortlist to answer your questions on formats, metadata, and exit costs in writing.

Keep your options open

The best time to plan your exit is before you commit. Our cloud advisory team can help you test your exports, map what your data depends on, and estimate the true cost of switching, so you can choose a platform without getting locked in. Talk to our team today to check your portability before you sign.

Making sense of workplace computer energy costs

Energy savings on office computers are often promised and rarely measured. Before buying new equipment or changing power settings, it helps to know what the current fleet actually draws in each state: off, asleep, idle, and busy.

Start with the arithmetic

The calculation is simple. Multiply a device’s power draw in watts by the hours it runs, divide by 1,000 to get kilowatt-hours, then multiply by the electricity rate. A 100-watt device running 10 hours a day, for example, uses one kilowatt-hour daily. U.S. Energy Information Administration data put the national commercial average near 14 cents per kilowatt-hour in early 2026, with the lowest-cost states closer to 7 to 9 cents. Use the blended rate from your own bill instead, since demand charges and tiered pricing can make the effective cost differ from a published average.

Measure at the wall, not from the label

A power supply’s wattage rating is a ceiling, not a measurement. To learn actual consumption, plug the computer into an inexpensive watt meter or an energy-monitoring smart plug, and record the draw in each state: off, asleep, idle, and under a typical workload. Include the whole desk, because monitors, docking stations, and speakers draw power as well. Sample across a full working week, and use metered power strips or PDUs for server racks. ENERGY STAR applies the same logic when it certifies computers, weighting measured power in off, sleep, and idle modes by assumed time in each to estimate yearly energy. A business can do the same with its actual working hours.

Idle power is where waste hides

Consider an illustration, with the assumptions stated plainly. A desktop averages 40 watts while powered on and 2 watts asleep, and electricity costs 14 cents per kilowatt-hour. Left on all year, it uses about 350 kilowatt-hours and costs roughly $49. If it sleeps outside a 50-hour work week, it uses about 116 kilowatt-hours and costs roughly $16, a saving near $33 per computer. Across 50 computers, that is about $1,600 a year. Energy.gov, citing ENERGY STAR, estimates savings of up to about $30 per computer each year from sleep features, which sits in the same range.

Equipment efficiency and replacement decisions

Efficient hardware helps, though less than people expect. Energy.gov reports that ENERGY STAR labeled computers use 30 to 65 percent less energy than unlabeled ones, depending on usage, and that laptops use much less energy than desktops. Apply 30 to 65 percent to the $49 example and the annual saving is roughly $15 to $32 per machine. That rarely justifies replacing a working computer early, but it is a sound tiebreaker at refresh time. Favor ENERGY STAR certified models, consider laptops and docking stations for staff who do not need desktop power, and include monitors, which draw very little when certified and asleep.

Practical energy-management decisions

Start with settings, which cost nothing. Push sleep and display timers centrally through Group Policy or Microsoft Intune, matching them to real work patterns. Check that overnight patching and remote access still work, since sleeping machines must wake for updates; scheduled wake times or Wake-on-LAN usually solve this. Computers also release heat, so lower power draw can trim cooling needs in warm months. Ask your utility whether it offers incentives for efficient equipment or power management, and review the numbers again after a year, using the original meter readings as the baseline. Report results as dollars per workstation per year, so decision makers can weigh energy against other IT priorities.

Want to know what your office computers really cost to run and where you can cut waste without disrupting staff? Our team can measure your fleet, set up centralized power management, and plan efficient hardware refreshes. Get in touch to start.

What do your office computers really cost to run?

A computer’s price tag tells only part of its cost. A few inexpensive measurements and some simple arithmetic reveal what each workstation really costs to run and which energy-management steps pay off.

Start with the arithmetic

The calculation is simple. Multiply a device’s power draw in watts by the hours it runs, divide by 1,000 to get kilowatt-hours, then multiply by the electricity rate. A 100-watt device running 10 hours a day, for example, uses one kilowatt-hour daily. U.S. Energy Information Administration data put the national commercial average near 14 cents per kilowatt-hour in early 2026, with the lowest-cost states closer to 7 to 9 cents. Use the blended rate from your own bill instead, since demand charges and tiered pricing can make the effective cost differ from a published average.

Measure at the wall, not from the label

A power supply’s wattage rating is a ceiling, not a measurement. To learn actual consumption, plug the computer into an inexpensive watt meter or an energy-monitoring smart plug, and record the draw in each state: off, asleep, idle, and under a typical workload. Include the whole desk, because monitors, docking stations, and speakers draw power as well. Sample across a full working week, and use metered power strips or PDUs for server racks. ENERGY STAR applies the same logic when it certifies computers, weighting measured power in off, sleep, and idle modes by assumed time in each to estimate yearly energy. A business can do the same with its actual working hours.

Idle power is where waste hides

Consider an illustration, with the assumptions stated plainly. A desktop averages 40 watts while powered on and 2 watts asleep, and electricity costs 14 cents per kilowatt-hour. Left on all year, it uses about 350 kilowatt-hours and costs roughly $49. If it sleeps outside a 50-hour work week, it uses about 116 kilowatt-hours and costs roughly $16, a saving near $33 per computer. Across 50 computers, that is about $1,600 a year. Energy.gov, citing ENERGY STAR, estimates savings of up to about $30 per computer each year from sleep features, which sits in the same range.

Equipment efficiency and replacement decisions

Efficient hardware helps, though less than people expect. Energy.gov reports that ENERGY STAR labeled computers use 30 to 65 percent less energy than unlabeled ones, depending on usage, and that laptops use much less energy than desktops. Apply 30 to 65 percent to the $49 example and the annual saving is roughly $15 to $32 per machine. That rarely justifies replacing a working computer early, but it is a sound tiebreaker at refresh time. Favor ENERGY STAR certified models, consider laptops and docking stations for staff who do not need desktop power, and include monitors, which draw very little when certified and asleep.

Practical energy-management decisions

Start with settings, which cost nothing. Push sleep and display timers centrally through Group Policy or Microsoft Intune, matching them to real work patterns. Check that overnight patching and remote access still work, since sleeping machines must wake for updates; scheduled wake times or Wake-on-LAN usually solve this. Computers also release heat, so lower power draw can trim cooling needs in warm months. Ask your utility whether it offers incentives for efficient equipment or power management, and review the numbers again after a year, using the original meter readings as the baseline. Report results as dollars per workstation per year, so decision makers can weigh energy against other IT priorities.

Want to know what your office computers really cost to run and where you can cut waste without disrupting staff? Our team can measure your fleet, set up centralized power management, and plan efficient hardware refreshes. Get in touch to start.

How to measure the real energy cost of workplace computers

Most businesses know what their computers cost to buy and almost none know what they cost to run. Measuring real consumption, instead of relying on nameplate ratings or rules of thumb, shows where the money goes and which changes are worth making.

Start with the arithmetic

The calculation is simple. Multiply a device’s power draw in watts by the hours it runs, divide by 1,000 to get kilowatt-hours, then multiply by the electricity rate. A 100-watt device running 10 hours a day, for example, uses one kilowatt-hour daily. U.S. Energy Information Administration data put the national commercial average near 14 cents per kilowatt-hour in early 2026, with the lowest-cost states closer to 7 to 9 cents. Use the blended rate from your own bill instead, since demand charges and tiered pricing can make the effective cost differ from a published average.

Measure at the wall, not from the label

A power supply’s wattage rating is a ceiling, not a measurement. To learn actual consumption, plug the computer into an inexpensive watt meter or an energy-monitoring smart plug, and record the draw in each state: off, asleep, idle, and under a typical workload. Include the whole desk, because monitors, docking stations, and speakers draw power as well. Sample across a full working week, and use metered power strips or PDUs for server racks. ENERGY STAR applies the same logic when it certifies computers, weighting measured power in off, sleep, and idle modes by assumed time in each to estimate yearly energy. A business can do the same with its actual working hours.

Idle power is where waste hides

Consider an illustration, with the assumptions stated plainly. A desktop averages 40 watts while powered on and 2 watts asleep, and electricity costs 14 cents per kilowatt-hour. Left on all year, it uses about 350 kilowatt-hours and costs roughly $49. If it sleeps outside a 50-hour work week, it uses about 116 kilowatt-hours and costs roughly $16, a saving near $33 per computer. Across 50 computers, that is about $1,600 a year. Energy.gov, citing ENERGY STAR, estimates savings of up to about $30 per computer each year from sleep features, which sits in the same range.

Equipment efficiency and replacement decisions

Efficient hardware helps, though less than people expect. Energy.gov reports that ENERGY STAR labeled computers use 30 to 65 percent less energy than unlabeled ones, depending on usage, and that laptops use much less energy than desktops. Apply 30 to 65 percent to the $49 example and the annual saving is roughly $15 to $32 per machine. That rarely justifies replacing a working computer early, but it is a sound tiebreaker at refresh time. Favor ENERGY STAR certified models, consider laptops and docking stations for staff who do not need desktop power, and include monitors, which draw very little when certified and asleep.

Practical energy-management decisions

Start with settings, which cost nothing. Push sleep and display timers centrally through Group Policy or Microsoft Intune, matching them to real work patterns. Check that overnight patching and remote access still work, since sleeping machines must wake for updates; scheduled wake times or Wake-on-LAN usually solve this. Computers also release heat, so lower power draw can trim cooling needs in warm months. Ask your utility whether it offers incentives for efficient equipment or power management, and review the numbers again after a year, using the original meter readings as the baseline. Report results as dollars per workstation per year, so decision makers can weigh energy against other IT priorities.

Want to know what your office computers really cost to run and where you can cut waste without disrupting staff? Our team can measure your fleet, set up centralized power management, and plan efficient hardware refreshes. Get in touch to start.

Why VoIP call transfers fail between phone systems

A call transfer may seem simple, but behind the scenes, multiple phone systems must coordinate how to pass an active call to another person or number. They do this through SIP messages, which different vendors may handle in their own ways. When systems don’t agree, calls can drop, callers may hear silence, or transfers may fail when dialing an outside number. Understanding how the process works makes these issues easier to troubleshoot.

How a SIP transfer works

A SIP call transfer involves three parties: the transferor, who initiates the transfer; the transferee, whose call is being moved; and the target, who receives the call.

Most transfers use the SIP REFER method, defined in RFC 3515 (The Session Initiation Protocol REFER Method). This RFC defines how one SIP device can ask another to make a new request, such as starting a call to a different destination. The destination is included in the Refer-To header, while the Referred-By header identifies who requested the transfer.

The receiving system then sends a new INVITE, the SIP method used to initiate a call, to the target. It reports the call’s progress through NOTIFY messages, which communicate updates such as whether the new call is ringing or has connected.

The process depends on the type of transfer. A blind transfer sends the call to the target immediately, without first checking their availability. An attended transfer allows the transferor to call the target first and confirm they are available before completing the handoff. It uses the Replaces header, defined in RFC 3891 (The SIP Replaces Header), to identify the existing call that the new call should take over.

For a broader look at how these mechanisms work together, RFC 5589 (Session Initiation Protocol Call Control – Transfer) describes recommended practices and call flows for implementing SIP transfers, including blind and attended transfers.

Where interoperability breaks down

SIP transfer failures usually fall into a few common categories. The first is support mismatch: not every phone system or carrier supports REFER. Microsoft Teams Direct Routing documentation provides an example of how platforms handle this, listing a fallback order of REFER, INVITE with Replaces, and then an internal transfer method that the session border controller (SBC), which manages SIP traffic between networks, cannot see. These fallback methods can behave differently, sometimes leaving callers unable to hear the phone ringing while waiting for an answer.

Header handling is another common issue. A REFER request may not contain all the information needed to route the new call, so Microsoft expects the SBC to preserve the Refer-To and Referred-By headers when creating the new INVITE. That INVITE must go back to the platform’s SIP proxy rather than directly to the telephone network. Rewriting the headers or routing the INVITE elsewhere can break the transfer.

Missing progress messages can also cause failures. The receiving system should respond to REFER with “202 Accepted” and send NOTIFY messages to report progress. If these messages never reach the initiating system, it may time out. If a BYE message, which ends an established call, arrives too early, the original call can drop before the transfer completes.

Firewall rules add another potential obstacle. REFER requests may arrive over new TLS connections from any of the platform’s signaling addresses. Firewalls that allow only specific addresses can block these requests, even when other SIP traffic works normally.

Finally, carrier behavior and platform updates can introduce unexpected problems. A 481 Call/Transaction Does Not Exist response means the receiving system can no longer find the referenced call or transaction. During an attended transfer, this can happen when the transferor’s temporary call to the intended recipient (known as a consultation call) stays on hold long enough for a carrier device to expire it.

Platform changes matter too. In June 2026, Microsoft changed its blind-transfer behavior so its side ends the original call as soon as the SBC accepts the transfer, without waiting for the final result. Configurations that worked under the previous behavior may therefore need to be reviewed.

Practical troubleshooting checks

Start by identifying the transfer type (blind or attended), its direction, and which system receives the REFER request. Capture SIP traces of both a failed and successful transfer using SBC logs or a packet capture, then compare the messages to find where they differ.

Check whether REFER is listed in the Allow header on each leg of the call. If a system does not support REFER, removing it from the advertised methods may force some platforms to use INVITE with Replaces as a temporary workaround.

Next, verify that the new INVITE preserves the Refer-To and Referred-By values and that 202 Accepted and NOTIFY messages reach the system that initiated the transfer. Check message timing too, particularly whether a BYE arrives before the final NOTIFY. If callers hear silence instead of ringing, check REFER support and the handling of 180 Ringing and 183 Session Progress responses, which provide call-progress updates.

Also review firewall rules to ensure all required signaling addresses are allowed, and confirm that destination numbers use the format expected by the next system.
Finally, test internal and external transfers separately, including both blind and attended transfers across desk phones, softphones, and mobile devices. Comparing the results helps identify which system or network connection is causing the failure.

Call transfer failures between your phone system, carrier, or cloud platform can be difficult to diagnose. Our team can capture and analyze SIP traffic, identify where the handoff breaks, and help get your calls transferring reliably. Contact us to start troubleshooting.