MAN3000 has been the default call-logging answer in South Africa for decades, and plenty of sites still run it happily. But if your PBX estate has moved to Asterisk — FreePBX, Issabel, VitalPBX — you're probably paying for a workflow designed around hardware that your phone system no longer needs. This guide walks through what actually changes when you migrate off a buffer-based call logger, and how to do it without losing a month of reporting.
Why the buffer box is the real issue
Traditional call loggers were built for PBXes that could only print call records — so a serial or IP buffer device sits next to the PBX, captures the SMDR/CDR stream, and forwards it to the logging software. That architecture made sense in 1995. An Asterisk-based PBX writes every call detail record to a MySQL/MariaDB database as it happens — the buffer is a solution to a problem you no longer have, and one more piece of hardware that can fail, lose records, or need a dealer visit.
Modern reporting connects to the CDR database directly over SSH: no hardware, no serial cables, nothing new in the rack, and no gap between a call ending and it being reportable.
Step 1: Inventory what you actually use
Before migrating, list what your team really consumes: which reports land on whose desk, which departments have budgets, whether you bill calls onward to clients or tenants, and which add-on modules you're licensed for. Migrations go wrong when they try to replicate every report that exists rather than the handful that get read.
Step 2: Export your organisational structure
The valuable data in any call logger isn't the historical calls — your PBX still has those — it's the mapping: which extension and which PIN/account code belongs to which person and department. Get that out as a spreadsheet. On the new side you want a tool that imports it as CSV in one pass and can round-trip it back out, so HR churn stays a spreadsheet job rather than a re-keying exercise.
Step 3: Bring your rates
Cost reporting is only as good as the rate table behind it. Export or note your current per-destination rates (local, mobile, international prefixes, premium) and load them as prefix-based rules. If you bill in Rand today but have branches billing in other currencies, check the new tool can present costs in the currency your rate file uses.
Step 4: Run both in parallel for one cycle
Don't cut over blind. Run the old and new systems side by side for a billing cycle and compare
month totals. When numbers differ, the causes are almost always the same three: the old system
counted ring time (duration) where the new one counts talk time (billsec), timezone
handling shifts calls across month boundaries, or unanswered calls are filtered differently.
Resolve those deliberately and sign off the new numbers before you switch.
Step 5: Cut over — and pick up what the old system couldn't do
Once totals reconcile, the migration itself is done: the PBX keeps stamping CDR records, the new tool keeps reading them. This is also the moment to switch on the things buffer-era loggers never had: department budgets with threshold alerts, reports emailed on a schedule instead of generated by hand, and dashboards for inbound/missed-call performance.
Where Q5000 fits
Q5000 was built for exactly this migration path on Asterisk-family PBXes: it connects to FreePBX, Issabel and VitalPBX over SSH (provisioning a least-privilege read-only database user for you), imports extensions and PIN/account-code mappings from CSV, applies prefix-based rate rules with ZAR as the default currency, and adds department budgets, scheduled email reports and billing on top. Pricing is published openly, and there's a side-by-side comparison with MAN3000 if you want the detail. See Q5000 pricing →
Frequently asked questions
Do I need buffer hardware with Q5000? No. Q5000 connects to your PBX's CDR database directly over SSH — there is no serial or IP buffer device, and nothing extra to install in the rack.
My PBX isn't Asterisk-based — can I still migrate? Q5000 supports Asterisk-family systems: FreePBX, Issabel and VitalPBX. If your PBX is not Asterisk-based, MAN3000's broad legacy PBX support may still be the better fit — migrate the PBX first, then the reporting.
Do I lose my historical call data when I switch? Your Asterisk PBX retains its own CDR history, and Q5000 can also import CDR exports as CSV — so reporting continuity depends on your PBX's retention, not on the old logger. Keep the old system's archives available read-only for the handover period.
How long does the migration actually take? For a single PBX the working setup is typically an afternoon: SSH connection, extension and PIN import from CSV, and a rate file. The parallel-run month is for confidence in the numbers, not for setup effort.