Is AdaptivMapr a step up from ImportCSV?

On healthcare use cases, yes — multilingual hints, FHIR emit, inherited BAA coverage, learned auto-accept thresholds. On generic low-volume B2B imports ImportCSV may stay the better answer on cost.

What does schema-only mode include?

Schema-only mapping across the 10 healthcare templates plus 21 business templates; MCP server access; the hosted Workbench and the REST API. It bills only the small flat per-map fee from your prepaid wallet — no metered AI. Schema-only mode minimizes data exposure — only headers and ≤3 truncated sample rows are processed; a DPA/BAA may still be required depending on the data, and mapr provides one on request.

Can I migrate one template at a time?

Yes. Most teams move templates over in order of compliance pressure — healthcare first, generic last. Feature-flag at the import route to run both side by side during cutover.

Do I need a separate product for full-data mode?

Only for full-data mode. Schema-only mapping is standalone. An AdaptivMapr (PHI) entitlement unlocks LLM-driven row-level cleanup with an inherited BAA; the tokens it uses bill from your prepaid wallet.

Every commit is written to Chainlog as a hash-chained event — which rows, mapped from which source columns, by which user, against which schema version.

ImportCSV alternative

AdaptivMapr is the healthcare-aware ImportCSV alternative.

ImportCSV is bare-bones lower-cost CSV import tool — minimal feature set, simple pricing. We are not pretending otherwise. AdaptivMapr’s wedge is narrower and sharper: data-minimized schema-only mode, FHIR-aware healthcare templates with multilingual hints, and a BAA posture that comes from an inherited BAA rather than negotiating a vendor-specific one.

If your import path touches PHI, FHIR, or multilingual clinical data, the trade is worth running. If it does not, stay on ImportCSV.

Talk to migration Try in MCP →View pricing →

Where ImportCSV wins

Cheap and simple — fewer features means fewer decisions
Works for early-stage products that just need any importer
No-friction setup for generic, low-stakes CSV ingestion

Where AdaptivMapr wins

Healthcare-aware templates with FHIR emit ship out of the box
Schema-only mode is a production-grade data-minimization mode (DPA/BAA on request), not just a trial
MCP server, multilingual hints, and learned auto-accept thresholds from production data

Side by side

ImportCSV vs AdaptivMapr

Only the rows where the answer is clear. If a comparison is ambiguous we have left it out rather than guess.

Capability	ImportCSV	AdaptivMapr
Pricing floor	Lower-cost simple tiers	Prepaid token wallet from $10 (no free tier, no subscription). A small flat fee per map (~$0.001); AI cleanup bills AI tokens at provider cost × 2 (× 0.5 with your own key).
MCP server (Cursor, Claude Desktop)	Not shipped	@adaptivmapr/mcp-server — schema-only tools need no key, no signup
Schema-only mode (minimal data exposure)	Not a documented mode	Default. Only headers + ≤3 sample rows ever leave the caller
Healthcare templates with BAA path	DIY — generic schema builder	10 templates (Patient, Observation, Medication, Claim.item, Coverage, Practitioner, Appointment, …) with inherited BAA coverage
FHIR resource emit	Not built-in	Templates emit FHIR resources where applicable
Learns from per-tenant corrections	Per-workspace synonyms, manually curated	Cascade auto-accept at {minN:100, minRatio:0.95} and {minN:20, minRatio:1.00} from prod corrections
Multilingual healthcare hints	EN-first, custom synonyms per tenant	DE / FR / IT / EN / ES on every healthcare field, shipped
Regulated-data validators	Generic regex / range	IBAN, BIC, GTIN, LOINC, ICD-10, ATC, CPT, NPI, GLN as first-class validators
Replaces ImportCSV for generic B2B CSV import	Yes — that is the core use case	Not the wedge. Use ImportCSV for non-regulated flows.

The switch

Why dev teams switch from ImportCSV

ImportCSV is a fine answer when the bar is "we need an importer this week and it does not have to do much". Teams outgrow it when the importer has to do real work — handle multilingual headers, validate clinical codes, emit FHIR, or pass a compliance review. The switch to AdaptivMapr usually happens when the team realises they are about to rebuild from scratch what AdaptivMapr ships in templates: AHV/NPI/LOINC/ICD-10 validators, per-tenant correction learning, and a BAA-inherited full-data mode.

When ImportCSV is actually the right call

For low-stakes, low-volume, non-healthcare imports ImportCSV is the cheaper, simpler answer and we are not going to win that comparison on cost alone. The argument for AdaptivMapr is that your use case is already healthcare-shaped or about to become so, and rebuilding healthcare validators on top of a bare-bones tool is more expensive than switching.

Migration

Migration walkthrough

Most ImportCSV deployments are simple — a single endpoint, a thin set of column mappings. Re-create each schema as an AdaptivMapr template (or use an existing one for healthcare shapes). Drop the embed in place of the ImportCSV widget. Use the MCP server to test the mapping outcomes from your editor before cutting over production traffic. The Chainlog audit trail starts immediately on the first AdaptivMapr commit, which usually makes the compliance team happy.

30-second equivalence

Before · ImportCSV

// Before — ImportCSV minimal embed
<ImportCSVButton
  importerKey="ic_…"
  onComplete={(data) => /* … */ }
/>

After · AdaptivMapr

// After — AdaptivMapr (healthcare-aware, schema-only mode)
import { AdaptivMaprImport } from '@adaptivmapr/react'

<AdaptivMaprImport
  templateId="patient_demographics"
  mode="schema-only"
  onCommit={(rows) => /* … */ }
/>

// Or call the API directly:
// POST /v1/uploads -F file=@patients.csv -F template=patient_demographics

FAQ

Questions, answered

Is AdaptivMapr a step up from ImportCSV?: On healthcare use cases, yes — multilingual hints, FHIR emit, inherited BAA coverage, learned auto-accept thresholds. On generic low-volume B2B imports ImportCSV may stay the better answer on cost.
What does schema-only mode include?: Schema-only mapping across the 10 healthcare templates plus 21 business templates; MCP server access; the hosted Workbench and the REST API. It bills only the small flat per-map fee from your prepaid wallet — no metered AI. Schema-only mode minimizes data exposure — only headers and ≤3 truncated sample rows are processed; a DPA/BAA may still be required depending on the data, and mapr provides one on request.
Can I migrate one template at a time?: Yes. Most teams move templates over in order of compliance pressure — healthcare first, generic last. Feature-flag at the import route to run both side by side during cutover.
Do I need a separate product for full-data mode?: Only for full-data mode. Schema-only mapping is standalone. An AdaptivMapr (PHI) entitlement unlocks LLM-driven row-level cleanup with an inherited BAA; the tokens it uses bill from your prepaid wallet.
What about audit?: Every commit is written to Chainlog as a hash-chained event — which rows, mapped from which source columns, by which user, against which schema version.

Next step