13 business templates
Core (3), CRM (5) and E-commerce (5) packs cover users, contacts, companies, products, orders and the rest of the common business objects — with DE / FR / IT / EN / ES hints so any customer export maps.
⇌AdaptivMapr
Solution · Business packs
Users, contacts, orders — Core, CRM & E-commerce.
Every SaaS onboards customer data — user lists, CRM contacts, product catalogs, orders — and each customer export looks different. AdaptivMapr makes onboarding imports just map.
The problem
Why this is hard
Every SaaS has to onboard customer data — user lists, CRM contacts, product catalogs, orders — and each customer’s export looks different. Building a bespoke importer per customer, or asking them to reshape their file, is friction at exactly the wrong moment. The AdaptivMapr Core (3 templates), CRM (5) and E-commerce (5) packs cover the common business objects with multilingual hints, so onboarding imports just map. These are low-risk and fast, and most columns resolve on the free deterministic layers without ever calling a model.
How it works
The pipeline, end to end
- 1
Upload the customer file
Take whatever a customer exports — a user list, a CRM contact dump, a product catalog, an orders CSV — and upload it as-is. No pre-formatting required.
CSV / ExcelAny layout - 2
The cascade maps it
Deterministic layers (statistics, heuristic, fuzzy) resolve the common business objects against the Core, CRM and E-commerce packs using multilingual hints — most columns land without ever reaching a metered model.
CoreCRME-commerce - 3
Validate
Field-level validators check the formats each template defines (GTIN on catalog items, email and identifier formats on contacts) so bad values are caught at map time.
GTINField validators - 4
Commit to your DB or webhook
Confirmed mappings write straight to your database or fire a webhook. One-click layout reuse remembers the mapping for a recurring file, so the next import of the same shape skips straight to commit.
Layout reuseWebhook / DB
Why AdaptivMapr
What makes it fit
One-click layout reuse
The whole confirmed mapping for an exact header row is cached by fingerprint, so a recurring import from the same source offers a reuse-last-mapping shortcut and skips the mapping step.
Connectors for scheduled ingest
Register a scheduled ingest source with encrypted secrets and let it pull and map on a cadence — no manual upload for recurring feeds.
MCP + REST API
Drive the whole flow over a clean REST /v1 surface or through the MCP adapter, so onboarding automation and agents can map files programmatically.
In code
A representative call
Map a customer’s orders export to the E-commerce orders template — low-risk, mostly resolved on the free deterministic layers, then committed to your DB.
curl
# 1. upload the customer file
curl https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $MAPR_KEY" \
-F file=@orders.csv
# 2. map to the e-commerce "orders" template
curl https://api.adaptivmapr.com/v1/uploads/$ID/mappings \
-H "Authorization: Bearer $MAPR_KEY" \
-X PATCH -d '{"template":"orders"}'
# 3. reuse a known layout next time (skip mapping)
curl https://api.adaptivmapr.com/v1/layouts/lookup \
-H "Authorization: Bearer $MAPR_KEY" \
-X POST -d '{"headers":["OrderID","SKU","Qty","Total"]}'response
{
"template": "orders",
"risk": "low",
"requires_hitl": false,
"layout": { "match": "exact", "reusable": true },
"fields": {
"order_id": { "source": "OrderID", "ok": true },
"sku": { "source": "SKU", "validator": "gtin", "ok": true },
"quantity": { "source": "Qty", "ok": true },
"total": { "source": "Total", "ok": true }
}
}FAQ
Common questions
Three packs, 13 templates: Core (3) for the base business objects, CRM (5) for contacts, companies and the sales objects, and E-commerce (5) for products, orders and catalog data. Each carries multilingual hints so a customer’s export maps regardless of their header names or language.
Business templates are low-risk and their columns are common, so the free deterministic layers — statistics, heuristic and fuzzy — resolve most of them without ever calling the metered LLM layer. That is the biggest cost lever, and business objects lean on it hardest.
When a mapping is confirmed, the whole layout is cached against a fingerprint of the normalized header row. The next time the same shape arrives, POST /v1/layouts/lookup returns the stored mapping so the importer can offer a one-click reuse and skip mapping entirely. It is workspace-scoped — no cross-tenant sharing.
Yes. Connectors register a scheduled ingest source with encrypted secrets and pull-and-map on a cadence, and the full flow is available over the REST /v1 API and the MCP adapter for programmatic onboarding.
Ready when you are
Map business packs data without shipping raw records.
Test on schema-only for a few tokens per map. Full-data routing under a BAA when you go live.
$10 minimum to start · pay only for what you map · PHI under BAA coverage