Migrate your Acumen data
Fiscal agent and billing management CRM for medical organizations handling payer claims, eligibility, and remittance workflows.
In its favor
Why people choose Acumen
The signal that keeps Acumen on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Long-standing track record in self-direction — Acumen has operated as a Fiscal Employer Agent since 1995, making it one of the oldest FMS providers in the country and a default option for many state Medicaid waiver programs.
DCI software platform handles EVV out of the box — Acumen uses the Direct Care Innovations (DCI) system for time entry, EVV, and payroll, satisfying the federal 21st Century Cures Act EVV mandate without requiring participants to source third-party tools.
Multi-state coverage with state-specific resource pages — Acumen runs dedicated state pages for programs in Oklahoma, Georgia, Missouri, Minnesota, North Carolina and others, with localized forms and program-specific guidance.
Handles full employer-of-record obligations — Acumen processes payroll deductions, federal/state/local tax filings, W-2s, and 1099s on behalf of self-directing participant employers, removing the tax-compliance burden from families managing their own care.
Web portal and mobile app for time entry — direct care employees can submit time via either the DCI web portal at acumen.dcisoftware.com or the DCI mobile app, with employer approval routed through the same system.
Service quality complaints are well-documented — BBB shows a 1.0-star rating across 18 reviews and 7 complaints, with recurring themes of slow phone support, unresolved issues, and difficulty reaching staff (per BBB customer review aggregations).
Glassdoor employee reviews reflect operational churn — 103 reviews on Glassdoor surface internal turnover and process inconsistency, which translates into customer-facing handoff problems mid-payroll cycle.
Dependence on DCI software means platform changes are out of Acumen's control — when DCI pushes interface or workflow changes, participants must adapt regardless of Acumen's preferences.
Limited to self-directed Medicaid waiver populations — organizations outside the FMS/FEA model (traditional agency-based home care, private-pay) cannot use Acumen at all, forcing migration when service models change.
Pricing is set by state contracts, not by the customer — participants and families have no negotiating leverage on FMS fees, which are pre-negotiated rates between Acumen and the state Medicaid agency.
Reasons to switch
Why people leave Acumen
The recurring reasons buyers give for replacing Acumen. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Acumen fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
What gets migrated
Acumen object support
Object-by-object support for Acumen migrations. Per-pair details surface during scoping.
Patients
Mapping requiredPatient records in Acumen Fiscal Agent include demographic, insurance, and fiscal agent assignment fields. We map these to the destination patient object while preserving the agent relationship as a custom field.
Insurance Claims
Mapping requiredClaims are the core transactional object. We export claims with status, submission date, and payer response. Claims history is exported in full. We flag claims with open follow-up items for manual review before import.
Remittance Records
Mapping requiredERA/EOB remittance records attach to claims and include payment amounts, adjustments, and denial codes. We match remittance entries to claims and export them as linked line items.
Encounters
Mapping requiredMedical encounters link patient, provider, date of service, and procedure codes. Encounter data is used to generate claims and must be sequenced before claims export to maintain billing order.
Payers
Fully supportedPayer records (insurance carriers, Medicare, Medicaid) are referenced by claims and remittance. We export the full payer list and re-link claims to destination payer records by payer ID mapping.
Providers
Mapping requiredProvider records include NPI, taxonomy, and billing group assignments. We export provider data and map to destination provider records, flagging any inactive or terminated providers.
Fee Schedules
Mapping requiredCustom fee schedules per payer or provider are stored as configuration data. We export fee schedule rules and map them to destination pricing structures, noting any unsupported schedule formats.
Fiscal Agent Assignments
Mapping requiredFiscal agent relationship data tracks which patients and providers are represented by the agent. We export these assignments and map them to the destination agent context, flagging if the destination does not support agent assignment objects.
Documents
Mapping requiredSupporting documents (authorization letters, appeals, contracts) may be attached to claims or patients. We export document metadata and provide download links or file blobs where available.
| Object | Support | Notes |
|---|---|---|
| Patients | Mapping required | Patient records in Acumen Fiscal Agent include demographic, insurance, and fiscal agent assignment fields. We map these to the destination patient object while preserving the agent relationship as a custom field. |
| Insurance Claims | Mapping required | Claims are the core transactional object. We export claims with status, submission date, and payer response. Claims history is exported in full. We flag claims with open follow-up items for manual review before import. |
| Remittance Records | Mapping required | ERA/EOB remittance records attach to claims and include payment amounts, adjustments, and denial codes. We match remittance entries to claims and export them as linked line items. |
| Encounters | Mapping required | Medical encounters link patient, provider, date of service, and procedure codes. Encounter data is used to generate claims and must be sequenced before claims export to maintain billing order. |
| Payers | Fully supported | Payer records (insurance carriers, Medicare, Medicaid) are referenced by claims and remittance. We export the full payer list and re-link claims to destination payer records by payer ID mapping. |
| Providers | Mapping required | Provider records include NPI, taxonomy, and billing group assignments. We export provider data and map to destination provider records, flagging any inactive or terminated providers. |
| Fee Schedules | Mapping required | Custom fee schedules per payer or provider are stored as configuration data. We export fee schedule rules and map them to destination pricing structures, noting any unsupported schedule formats. |
| Fiscal Agent Assignments | Mapping required | Fiscal agent relationship data tracks which patients and providers are represented by the agent. We export these assignments and map them to the destination agent context, flagging if the destination does not support agent assignment objects. |
| Documents | Mapping required | Supporting documents (authorization letters, appeals, contracts) may be attached to claims or patients. We export document metadata and provide download links or file blobs where available. |
Gotchas
What to watch for in Acumen migrations
Issues we've hit on past Acumen migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Acumen does not own the software — DCI is the underlying platform
FMS data is regulated by state Medicaid waiver rules
EVV records carry GPS and biometric verification data
State pages reference state-specific forms not in the standard schema
| Severity | Issue |
|---|---|
| High | Acumen does not own the software — DCI is the underlying platform |
| High | FMS data is regulated by state Medicaid waiver rules |
| Medium | EVV records carry GPS and biometric verification data |
| Medium | State pages reference state-specific forms not in the standard schema |
Leaving Acumen?
Where Acumen customers move next
12 destinations Acumen can migrate to.
How a Acumen migration works
Four steps, Acumen-specific
Connect
Not publicly documented — Acumen's data lives inside the DCI (Direct Care Innovations) platform at acumen.dcisoftware.com. Access to extract data requires DCI credentials provided to the participant employer. into Acumen. Scopes limited to read-only on the data we move.
Map
We translate Acumen-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Acumen quirks before production.
Migrate
Full migration with Acumen rate-limit handling. Rollback available throughout.
FAQ
Acumen migration FAQ
Answers to the questions buyers ask most during Acumen migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Acumen migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Acumen.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Acumen setup and destination — written quote back within a business day.