Collect! ran small agencies for 35 years. Then it was sold.
Collect! is the Windows system a lot of small agencies, collection law firms and medical collectors have run for a decade or more, often since the founder answered the phone himself. In September 2025 Comtech Systems was acquired by Recur Software Technologies, a private equity buyer of small vertical software companies. Within a year the entry cloud tier's list price had roughly tripled, a fee appeared on payments run through any gateway but the vendor's, and the desktop client began a rewrite. If your renewal just arrived, that is the number to compare.
- Accounts, debtors & balances
- Payment history, notes & activity
- Active payment arrangements
- Stored cards & ACH, via your processor
- Compliance flags & audit trail
Migrating from Collect! (Comtech Systems, Victoria BC; owned by Recur Software Technologies since September 2025) → Resolvah
What is happening at Collect!.
Dated and sourced. The things a buyer should know before deciding whether to stay.
- 1988 to 2016
Comtech Systems is founded in Victoria, British Columbia, by Fritz Schulze. Collect! grows into a Windows thick client with hosting in Canada, the US and Australia; the vendor's public footprint claim, 1,400 companies in 40 countries, has not changed since 2012. Version 12.1 moves the database to Microsoft SQL Server in 2016.
- 2021 to 2023
Version 13 adds Reg F handling (November 2021). A SOC 2 Type II audit completes in 2023, on top of HIPAA controls in place since 2015. Cards are vaulted through Evervault. The user conference goes virtual after in-person events in 2018 and 2019.
- September 2025
Recur Software Technologies (Chicago, London, New York), founded by former Accel investors, acquires Comtech. Corum Group advises. The founder retires at the sale; Comtech becomes an operating subsidiary of about 18 people. Recur's stated playbook for the companies it buys is AI features and embedded payments.
- October 2025 to early 2026
Version 13.8.1 adds in-app payment-plan storage; a Metabase BI interface follows in December. John Mitropoulos, a portfolio-CEO from private equity, is named General Manager and then CEO and Managing Director. Premise pricing comes off the public site.
- January to September 2026
The entry cloud tier's list price takes three steps in the ten months after the sale, in November, January and September, the last one the big one; it ends roughly three and a half times its January 2024 level, for a tier now defined as three users rather than one. From April, payments run through any gateway other than Collect! Payments carry a percentage-of-volume fee. Support is billed in 30-minute blocks; early cloud cancellation carries a monthly charge for the remaining term. Version 14, a browser-based client, is in development, and the legacy payment module is retired with it. The 2026 user conference is a single free online day.
Why agencies leave Collect!.
Agencies did not leave Collect! for 35 years because it was cheap, stable and the people answering the phone had written it. The sale changed the first two things and the retirement changed the third. What is left is a Windows program delivered over Remote Desktop and called cloud, a payments fee that rewards moving your processing to the vendor, and a client rewrite whose finish date nobody has published.
Post-sale repricing. Three list-price increases on the entry cloud tier in the ten months after the sale, a new fee on payments through any non-vendor gateway, support in 30-minute billing blocks and a charge to leave a cloud term early. The vendor's own newsletter reports an NPS of 38, from 20 responses.
Cloud that is a desktop. Each hosted tenant is a dedicated Windows VM reached through a Remote Desktop gateway. It works, but it is a thick client with a remote screen, not a browser application. V14 is planned to move collectors to a browser first while administration stays on the remote-desktop client.
Two portal generations side by side: the 2001-era Collect! Online web host and newer single-page consumer and client portals on your subdomain. Which one your consumers see depends on when you set it up.
The transition ahead. V14 replaces the client and retires the legacy payment module; migrating to it will be a project on its own. If you are going to do a migration, it is worth asking whether it should be to the same vendor.
Collect! vs Resolvah
Both can collect a debt. The difference is how it feels to your team, your clients, and the person on the other end.
A consumer portal on your subdomain (newer tenants) or the legacy Collect! Online host. Takes payments and shows balances; plain-language resolution, plan building and hardship paths are not the design.
A warm, self-serve resolution experience. Dee explains the balance in plain language, offers plans people can actually afford, and lets them resolve it 24/7 from any phone.
Windows client on SQL Server: on your own server, or a dedicated VM per tenant on AWS reached by Remote Desktop through regional gateways in the US, Canada and Australia.
Fully cloud-hosted and always current — nothing to install, patch, or keep alive on a server in your office.
Reg F features since V13, SOC 2 Type II and HIPAA controls, Metro 2 including Canadian bureaus, e-OSCAR. Call-frequency and consent live in your procedures more than in the flow.
FDCPA, Reg F, TCPA and state rules built into the everyday workflow, with a complete, exportable audit trail on every account and message.
Diary-driven workflow, built-in reports plus Metabase, a REST API with about a hundred endpoints. No automation builder, no AI assist; the new owner has said AI is coming.
Modern automation and AI assist draft outreach, summarize an account at a glance, and surface the next best step — without taking the human out of it.
Tiered cloud subscription per month or year, extra seats per user, a percentage fee on payments through a non-vendor gateway, add-ons with 12-month minimums, support by the half hour.
Transparent, predictable pricing. The features that make recovery humane aren't locked behind surprise modules or per-seat upcharges.
A small team, billed in 30-minute blocks. Resolvah reads your SQL Server database and the REST API directly, and reconciles every total with you.
A Resolvah onboarding team works with yours at every step: we map your data, move it, reconcile it against your old system, and work with your payment processor so active arrangements keep running. Four weeks to three months, and we stay on through go-live.
Comparison reflects general, publicly-observable platform characteristics and is provided to help you evaluate a switch. Collect! is a trademark of its respective owner; Resolvah is not affiliated with or endorsed by it.
A migration you barely feel.
Collect! keeps your data in a Microsoft SQL Server database that is yours: on your own server if you are on premise, or on your dedicated VM if you are on the cloud. Add the REST API and this is one of the cleaner exports on our list. We take a backup (never the live database), map accounts, clients, diary entries, transactions and plans, carry the credit-reporting state across, and reconcile every total against Collect!'s own reports before cutover. Four weeks to three months, usually the short end.
Prepare
We scope your portfolio, confirm the export path, and schedule a calm migration window.
Move
Your data comes across — accounts, history, notes and active plans — with a Resolvah specialist on it start to finish.
Validate
We reconcile every total with you against your old system before anyone relies on the new one.
Go live
Your collectors pick up where they left off, and your old system stays put until you're ready to retire it.
Worried about payment tokens? We work directly with your existing payment processor to re-point the vault to Resolvah, so stored cards and ACH come across and every active arrangement keeps running. Nobody re-enters a card, and no plan is interrupted.
The honest list for this system, so cutover day holds no surprises.
- Accounts, debtors, clients and balances
Read from your SQL Server backup and reconciled account by account against Collect!'s reports.
- Diary entries, notes and transaction history
The diary is the heart of Collect!; every entry comes across with its date, operator and outcome, searchable in Resolvah.
- Active payment plans
Plans, including those stored in-app since V13.8.1, continue on their cadence.
- Stored cards and ACH
Cards are vaulted with Evervault and run through Collect! Payments (Payscout or Payroc) or your own gateway. We work directly with your processor to re-point the vault to Resolvah, so every plan keeps running.
- Credit reporting history
Metro 2 reporting state, including Canadian bureau files, comes across so the next file is consistent with the last.
- Custom reports and Metabase dashboards
The data behind them moves; the reports themselves are rebuilt in Resolvah's reporting.
- Letters and call recordings
Letters live with your letter vendor or as templates; recordings live with your dialer (TCN and others). We help you export both for retention.
- Take a full SQL Server backup you control and confirm it restores somewhere else. Cloud tenants: ask for a backup of your tenant database from your VM, in writing, and note how long the vendor takes to provide it.
- Read the cloud agreement for the cancellation charge on the remaining term and any 12-month minimums on Skip & Score or other add-ons; time the notice to the term.
- If you moved to Collect! Payments, find out who holds the merchant account and the Evervault vault; if it is the vendor, tell us early and we will set up yours before notice.
- Note which portal your consumers use (the legacy Collect! Online host or the newer portal on your subdomain) and who controls that DNS.
- Pull your API credentials and the Swagger documentation from your tenant host while you still have access; it speeds the mapping.
Switching from Collect!
Is Collect! going away?
No. There is no sunset on record, the product is still being developed, and V14 is in progress. What is on record is a change of ownership to a private equity buyer, three list-price increases on the entry tier within a year, a new fee on payments through other gateways, and a client rewrite ahead. Those are reasons to compare, not a deadline.
We are in Canada or Australia. Does Resolvah fit?
Collect! is the system Canadian and Australian agencies actually buy, and we would rather tell you that plainly than migrate you into a poor fit. Resolvah's compliance engine is built around United States federal and state rules. If you collect in the US, talk to us. If you collect only outside it, ask us first and we will give you an honest answer about what works and what does not yet.
How painful is moving our Collect! data to Resolvah?
We make it as painless as we can, and we do it with you rather than to you. Accounts, balances, payment history, notes, active arrangements and compliance flags come across, and we reconcile the totals against Collect! before anyone relies on Resolvah. Anything that cannot come across (call recordings held by a dialer vendor, for example) is identified up front, so nothing is a surprise on cutover day.
Will active payment plans keep running when we switch from Collect!?
Yes. We work with your existing payment processor to re-point the vault to Resolvah, so stored card and ACH tokens come across, scheduled arrangements continue on their cadence, and no consumer re-enters payment details.
How long does migrating from Collect! take?
Four weeks to three months, depending on the size of the portfolio and how Collect! stores its data. A Resolvah onboarding specialist scopes it with you first, so you get a date, not a range, before anything moves. Collect! stays your system of record until the reconciliation is signed off.
Don't see your system? See every migration we support.
Leave Collect! behind — without leaving anything behind.
Book a 20-minute demo and we'll map your exact portfolio onto Resolvah, payment tokens and all.
