Moving From Retreaver to VeloCalls: Migrating Tags and Routing Rules

3:14pm on a Wednesday. I'm staring at a Slack message from an operator in Tampa who just discovered that Retreaver is sunsetting his legacy plan. He's got 47 active tags, 12 number pools, and a webhook pipeline that feeds three different CRMs. Migration deadline is 45 days out.

That's usually when the call happens. Panic mode.

Retreaver built a solid platform. We've said this about Ringba in our Ringba migration guide, and it applies here too — these aren't bad products. Retreaver's tag system is genuinely powerful. The visual campaign builder works. For some operators, it's exactly right.

But the pricing math changes, or the feature roadmap diverges from what you need, or support tickets start taking four days instead of four hours. Plenty of operators jump because the AI calling space keeps moving and their current platform stopped keeping up. Whatever the trigger, once you're looking at migration, you need a clean path. This is that path.

What You'll Have at the End

By the end of this tutorial, you'll have:

• All Retreaver tags mapped to VeloCalls equivalents
• Routing logic rebuilt in VeloCalls' visual IVR and rule system
• Number pools transferred or ported
• Webhooks re-wired to the same downstream systems
• A parallel testing setup that catches routing bugs before they cost you calls

If your setup is simpler — under 20 tags, one or two number pools, no complex webhook chains — this will take you a weekend. Maybe less. If you're the Tampa operator with 47 tags and three CRMs, budget two weeks and a lot of coffee. And probably some swearing.

Prerequisites

Before you start:

• Retreaver admin access for export functions
• VeloCalls account — free trial, no credit card required
• Spreadsheet app for tag mapping documentation
• Carrier account (Twilio, Telnyx, or Bandwidth) if using BYOC
• Webhook endpoint URLs for your downstream systems (CRM, analytics, billing)
• 2-3 hours blocked for the initial export and audit

Also helpful: your current call volume numbers. You'll use these to estimate per-minute costs. VeloCalls pricing is per-minute (not per-call), lifetime-usage-tiered. Managed Carriers start at 4¢/min and step down to 2¢/min at scale. BYOC starts at 2¢/min and drops to 0.5¢/min at 200K+ lifetime minutes. See our pay-per-call benchmarks report for industry cost comparisons.

Step 1: Export Your Retreaver Configuration

Pull everything out of Retreaver while you still have access.

Tags. This is the core of Retreaver's routing intelligence. Go to Tags → Export (or navigate to your campaign settings and export tag configurations). You'll get a list of tag names, descriptions, and which campaigns they're attached to. Save this as your master tag document.

Campaigns and targets. Export your campaign list with all associated targets (buyer phone numbers, caps, schedules). Note which tags apply to which campaigns — this relationship is what you'll recreate in VeloCalls.

Number pools. Document each number pool: how many numbers, what campaigns they're assigned to, any geographic restrictions. If you're porting these numbers, you'll need the specific phone numbers for the port request.

Routing rules. Retreaver's routing logic lives in campaign settings — priority order, tag requirements, fallback behavior. Screenshot or document each campaign's routing configuration. The visual representation helps when you're rebuilding in a different system.

Webhooks. Go to Integrations → Webhooks. Export every webhook configuration: endpoint URL, trigger event (call start, call end, call qualify), payload format, authentication headers. You'll re-create these in VeloCalls pointing to the same destinations.

What you should have after this step: a folder with tag exports, campaign CSVs, number pool docs, routing screenshots, and webhook configurations. This is your migration bible. Every decision in the next steps references back to this folder.

Step 2: Map Retreaver Tags to VeloCalls Concepts

Retreaver's tag system is flexible — tags can represent geo, time, skills, intent, lead quality, or anything else. VeloCalls uses a combination of buyer tags and routing rule conditions to achieve the same results, but the structure is different.

Here's the translation table:

Create a mapping spreadsheet. For each Retreaver tag, document:

1. Tag name
2. What it represents
3. VeloCalls equivalent (rule condition, buyer tag, or IVR branch)
4. How you'll implement it

Example mapping:

Retreaver: "AZ-hours"
Meaning: Arizona calls during 8am-6pm MST
VeloCalls: Routing rule → If geo = AZ AND time = 8am-6pm MST

Retreaver: "spanish"
Meaning: Caller prefers Spanish
VeloCalls: Buyer tag → spanish (apply to Spanish-speaking buyers)

Retreaver: "emergency"
Meaning: Urgent service need
VeloCalls: IVR branch → "Press 1 for emergency" → route to emergency pool

This mapping doc is the most important artifact of the migration. Get it right here, and the rebuild is just execution. Get it wrong, and you'll be debugging routing for weeks. Ask me how I know.

(I've done this wrong. More than once. A plumbing operator in Denver — 34 tags, and I rushed the mapping because I thought I was smarter than the process. We spent three weeks post-migration fixing routing edge cases that would've taken an hour to map correctly upfront. Humbling.)

Step 3: Set Up Your VeloCalls Account and Decide Carrier Strategy

Create your VeloCalls account at velocalls.com. Free trial, no card required.

Carrier decision: Managed or BYOC?

Managed Carriers means VeloCalls handles telephony. Simpler setup, no carrier relationship to manage. Pricing starts at 4¢/min (0-10K lifetime minutes), stepping down to 2¢/min at 200K+ lifetime minutes. If you're comparing options, see our Ringba alternatives comparison for the full pricing breakdown.

BYOC (Bring Your Own Carrier) means you connect your Twilio, Telnyx, or Bandwidth account. Lower platform cost — starts at 2¢/min, drops to 0.5¢/min at scale. But you manage the carrier side yourself.

If you're porting Retreaver numbers, BYOC often makes sense. Port your numbers to Twilio or Telnyx, then route through VeloCalls. Caller-facing numbers stay the same, your existing carrier relationships continue, and you get the lower BYOC rates.

If you want a clean break and don't care about keeping existing numbers, Managed Carriers is simpler.

Step 4: Rebuild Buyers and Apply Tags

Go to Buyers → Add Buyer in VeloCalls.

For each target from your Retreaver export:

• Name: Buyer or agent name
• Target phone: The phone number receiving calls (E.164 format: +1XXXXXXXXXX)
• Daily cap: How many calls this buyer accepts per day
• Concurrent limit: Max simultaneous calls
• Operating hours: Specify in buyer's timezone
• Geo restrictions: States or regions this buyer services

Now apply tags. Look at your mapping spreadsheet. For each Retreaver skill/quality tag that translated to a VeloCalls buyer tag, add it here.

Example: If your Retreaver campaign routed calls tagged "spanish" and "emergency" to Buyer A, you'd tag Buyer A with spanish and emergency in VeloCalls.

Common mistake: entering operating hours in the wrong timezone. If your buyer is in Phoenix (Arizona, no DST), select Arizona time specifically. Mountain Time is not the same thing six months of the year. We've seen calls route to "closed" buyers because of this. Test it. (I still double-check timezone settings on every migration. Burned too many times.)

Once all buyers are entered, do a count check. Buyers in VeloCalls should match active targets in your Retreaver export. Spot-check a few records against your source docs.

Step 5: Translate Routing Logic

This is where the rebuild diverges from Retreaver's model.

Retreaver uses tags attached to campaigns, with priority-based routing within each campaign. VeloCalls uses two systems: a visual IVR builder (for caller-facing menus and prompts) and rule-based routing (for backend buyer selection).

If your Retreaver routing was purely backend (no IVR menus, just tag-based buyer selection), you'll rebuild as routing rules:

Go to Routing → Create Rule Set.

For each Retreaver campaign's routing logic, create equivalent rules.

Example Retreaver setup: Campaign routes calls tagged "AZ + daytime" to Buyer A, "AZ + after-hours" to Buyer B, all other AZ to Buyer C.

VeloCalls rebuild:

1. Rule: If geo = AZ AND time = 8am-6pm MST → Buyer A (priority 1)
2. Rule: If geo = AZ AND time != 8am-6pm MST → Buyer B (priority 2)
3. Rule: If geo = AZ → Buyer C (priority 3, catches anything that didn't match above)

Rule priority order matters. First matching rule wins. Set your most specific rules highest priority.

If your Retreaver setup included IVR menus, you'll rebuild those in the visual IVR builder:

Go to Routing → IVR Builder.

Recreate your Retreaver IVR flow:

• Play prompt nodes for recorded messages
• Keypress routing for menu selections
• Branch to different buyer pools based on caller input

The visual builder is drag-and-drop. Most Retreaver IVR flows translate directly — the logic is the same, the interface is just different.

Pro tip from the IVR abandonment study we published: shorter IVR flows convert better. If your Retreaver IVR had 5+ menu levels, migration is a good time to simplify.

Step 6: Port or Provision Numbers

Numbers are where migrations get scary. Dropped calls cost money. Real money.

Option A: Port existing numbers.

If callers know your numbers (ads, print materials, website), keep them. Submit port requests through your carrier (Twilio, Telnyx, Bandwidth). You'll need:

• The phone numbers to port
• Current carrier/provider name
• Account number or CSR (Customer Service Record)
• Authorized contact name

Porting takes 7-14 business days for standard numbers. Toll-free can take longer.

Option B: Provision new numbers.

If you're using BYOC, provision in your carrier account, then add them to VeloCalls: Numbers → Add Number → Connect carrier.

If using Managed Carriers, provision directly in VeloCalls: Numbers → Add Number → select area code → provision.

Critical: Don't cancel Retreaver or kill old numbers until ports complete and testing passes. Run parallel numbers during transition. Route some traffic to VeloCalls, keep the rest on Retreaver. (More on this in Step 8.)

Step 7: Re-Wire Webhooks

Webhooks break when you migrate platforms. Every time. Different endpoint URLs, different payload formats, different authentication. It's annoying, but it's predictable — which means you can plan for it.

Pull your Retreaver webhook export. For each webhook:

1. Document the destination — what system receives this webhook? (CRM, analytics, billing)
2. Document the trigger — call start? Call end? Call qualified? Duration threshold?
3. Document the payload — what data fields does the destination expect?

Now recreate in VeloCalls: Integrations → Webhooks → Add Webhook.

• Endpoint URL: Same as before (pointing to your CRM/analytics/billing)
• Trigger event: Map Retreaver's trigger to VeloCalls equivalent
• Payload: VeloCalls uses different field names. Map them to match what your destination expects

VeloCalls webhook fields (common ones):

• call_id — unique call identifier
• caller_number — ANI
• called_number — tracking number dialed
• duration — call length in seconds
• buyer_name — which buyer received the call
• buyer_number — target number
• recording_url — if recording enabled

If your CRM expects Retreaver's field names, you may need a transformation layer (Zapier, Make, or a simple webhook proxy) to translate payloads. Or update your CRM integration to accept VeloCalls field names.

Test each webhook with a few calls before cutover. Nothing worse than discovering your CRM stopped receiving call data two weeks after migration.

For click-side attribution alongside call tracking, some operators wire their VeloCalls webhooks into JustAnalytics for privacy-first web analytics that doesn't trip GDPR — and ClickzProtect if they're also running paid search and want fraud filtering on the click side.

Step 8: Test and Run Parallel

Test before you trust. Seriously.

I know you want to skip this. I've wanted to skip this. Don't.

Test matrix — run at least 20 calls:

• Call from primary geo during business hours
• Call from primary geo after hours
• Call from outside geo (should hit overflow or rejection)
• Call through IVR menu (if you have one)
• Call when primary buyer is at cap (should overflow)
• Call that triggers each webhook

For each test, verify:

• Correct buyer received the call
• Tags applied correctly
• Recording started (if enabled — 3¢/min add-on)
• Webhook fired to the right destination with correct payload
• Analytics show accurate source attribution

Common errors during testing:

"Buyer unreachable" — check phone number format (E.164: +1XXXXXXXXXX). Also verify buyer's phone is actually working.

Calls routing to wrong buyer — check rule priority order. Most specific rules should be highest priority.

Webhook not firing — verify endpoint URL is correct and accessible. Check authentication headers if the destination requires them.

Parallel running:

Once testing passes, run both platforms in parallel for at least 7 days.

• Send 20-30% of traffic to VeloCalls
• Keep 70-80% on Retreaver
• Compare: connect rates, call duration, buyer feedback, webhook deliveries

After 7 days, if VeloCalls metrics match or beat Retreaver, flip the ratio. After 14 days, cut over fully.

Yes, parallel running costs money. You're paying two platforms for a week or two. Skip it at your own risk — we've caught bugs on day 5 that would've cost operators thousands if they'd cut over fully on day 1. That extra $200 in platform overlap? Cheap insurance.

Common Errors and How to Fix Them

Error: Routing rules not matching as expected

Cause: Rule priority order is wrong, or conditions are too broad.

Fix: Rules evaluate top-down. Put most specific conditions at highest priority. Add logging or test calls to see which rule is matching.

Error: Webhook payload missing fields

Cause: VeloCalls uses different field names than Retreaver.

Fix: Update your webhook configuration to include the fields your destination needs. If field names differ, add a transformation layer or update the destination to accept new names.

Error: Calls showing wrong source attribution

Cause: Tracking parameters not passing through from ad platforms.

Fix: Check tracking number setup. Verify UTM parameters or dynamic number insertion is configured correctly.

Error: Recording not starting

Cause: Recording add-on not enabled, or two-party consent disclosure not configured.

Fix: Enable recording in Settings (3¢/min add-on). For two-party consent states, configure a whisper or IVR prompt disclosing recording.

Next Steps

Once you're live on VeloCalls:

• Enable AI conversation intelligence for intake QA — transcription at 4¢/min, sentiment at 5¢/use, AI summary at 10¢/call. Pair it with a tight call qualification script so your agents and the AI score leads the same way
• Set up conversion-weighted routing after 30 days of data
• Review the TCPA compliance playbook — the 2026 enforcement landscape has shifted
• Check vertical-specific setup guides: home services or legal/mass tort

Migration is the hard part. You did it. (Or you will, once you stop reading and start doing.)

Run the math in 30 days: compare your per-minute VeloCalls cost against what Retreaver was charging, factor in your average call duration, and see where you landed. Most operators I've talked to save 15-30% on platform costs, but your mileage may vary depending on call volume and carrier setup. We bust more pricing misconceptions in our pay-per-call myths debunked guide.

Frequently Asked Questions

How long does a Retreaver to VeloCalls migration take?

Budget 2-3 weeks for a clean migration. Week one is export and audit. Week two is routing rebuild and number porting. Week three is parallel testing. Operators who try to compress this into a weekend usually spend the following month debugging edge cases.

Can I keep my tracking numbers when leaving Retreaver?

Yes. You can port tracking numbers to your own carrier (Twilio, Telnyx, Bandwidth) and run BYOC on VeloCalls, or request a port directly if using Managed Carriers. Porting takes 7-14 business days. Run parallel numbers during the transition to avoid dropped calls.

How do I migrate Retreaver tags to VeloCalls?

Retreaver tags translate to VeloCalls buyer tags and routing rule conditions. Export your Retreaver tag list, map each tag to a VeloCalls tag or a rule condition (geo, time, skill), then apply those tags to buyers during setup. The mapping doc is your source of truth for the rebuild.

What happens to my Retreaver webhooks after migration?

Re-point them. VeloCalls uses different endpoint URLs and payload formats. Export your Retreaver webhook configurations, then recreate each one in VeloCalls pointing to the same downstream systems (CRM, analytics, billing). Test with a few calls before cutover.

Try VeloCalls for Your Vertical

AI calling + pay-per-call platform built for HVAC, plumbing, roofing, PI lawyers, Medicare brokers, and insurance. Smart routing, real-time bidding, visual IVR builder, AI conversation intelligence. Per-minute pricing — Managed starts at 4¢/min, BYOC at 2¢/min, both drop as you scale.

See pricing → · Book a demo