Production-grade acumatica data extraction tool. OAuth2 governance, every API covered (Contract-Based REST, OData v4, legacy SOAP), every entity, scheduled deltas, Parquet/JSON/FBDI outputs. No bespoke REST scaffolding.
Hand-built REST/OData/SOAP clients against Acumatica always start cheap and end expensive. Three API surfaces, evolving schemas, rate limits and xRP custom-field discovery break them one by one.
Acumatica's Contract-Based REST, OData v4 and legacy SOAP web services are not difficult to call — but they are difficult to call correctly at scale across the three surfaces simultaneously. Contract-Based REST handles most modern entities but its pagination and $expand semantics differ from OData's $skip/$top/$expand. OData v4 is better for high-volume analytical pulls but doesn't expose every business operation. Legacy SOAP is still required for some Screen-Based scenarios and specialized Generic Inquiry exports. A custom script written for one surface breaks on the next.
Syntra ETL's acumatica data extraction tool ships pre-built support for every production endpoint across all three surfaces, every pagination pattern, every documented quirk — plus the undocumented ones we've discovered across multiple customer deployments. Backed by an SLA. Customers typically pay back the tool in week-three savings versus equivalent custom development, and the ongoing maintenance burden (chasing Acumatica's quarterly release upgrades, updating OAuth2 client patterns, handling new endpoints, discovering xRP custom fields) disappears entirely.
Whether you need a one-shot bulk extract for Fusion migration, a scheduled nightly delta feeding your data warehouse, or a Generic-Inquiry-driven analytical export for Excel-loving finance analysts — the same acumatica data extraction tool covers every case with the same governance model.
Every production endpoint, every API surface, every quirk handled.
GL journals, AP Bills, AR Invoices, Cash Management, Fixed Assets, Tax History — pulled via Contract-Based REST with $expand for related entities. Modified-since watermark for delta extraction.
High-volume GL Transaction extraction via OData v4 with $filter pushdown on FinPeriodID and Branch. Parallel partition extraction, 500K–2M lines/hr per worker pod.
SOOrders, POOrders, InventoryItems, Warehouses, Receipts, Issues, Transfers, Lot/Serial — through Contract-Based REST with full relationship $expand.
Projects, Project Tasks, Pay Apps (AIA-format export), Subcontracts, Change Orders, Cost Codes, Commitments via Contract-Based REST. Construction document attachments preserved.
Every published Generic Inquiry exposed as an OData endpoint, streamed with $filter and $select pushdown. Ideal for custom analytical pulls without writing SQL.
Customization Project repository, DAC schemas, Business Event definitions, Acumatica Report Designer reports, Dashboards via admin APIs and SOAP — feeds discovery without manual export.
From OAuth2 provisioning to first scheduled delta run, typically completes in 2–4 days.
Acumatica tenant admin creates an Integrated Application (OAuth2 client) with read-only access to the endpoints in your extraction plan. Client credentials stored in your cloud KMS — Syntra never holds them in plaintext. Legacy login endpoint configured as fallback if needed.
Extractor runtime deployed to your cloud environment (containerized, runs on Kubernetes, ECS, Cloud Run or bare VM). Output destination configured: S3/GCS/Azure Blob for files, plus optional Fusion FBDI/HDL drop targets.
Per-entity extraction scope configured (which fiscal periods, which Branches, which Generic Inquiries, which customer-defined endpoints). Schedule defined: one-shot bulk, nightly delta, weekly full snapshot, or any cron schedule. Output format per entity set.
Initial full-snapshot extract runs across all configured entities in parallel. For multi-year GL transaction history, partitioned by FinPeriodID and Branch and throttled to off-peak windows. Signed manifest produced with counts, sums and hashes per partition for downstream reconciliation.
Scheduled delta runs execute on cron, capturing modified-since records since the last watermark. Run logs feed your SOC 2 audit trail. Failures surface as alerts via email, Slack, PagerDuty or webhook — no silent drift.
The details that matter when the acumatica data extraction tool has to run unattended for years.
Every extract is idempotent — re-running the same scope produces byte-identical output. Failed runs resume from the last partition checkpoint rather than starting over.
Respects Acumatica's per-tenant concurrent session caps (default 10, configurable lower). Automatic 429 back-off with exponential retry. Never throttles live user submissions or shop-floor activity.
Every run produces a signed JSON manifest with record counts, sum totals, hash signatures, and source-modified timestamps per partition per Branch — ready for downstream reconciliation.
OAuth2 credentials encrypted at rest in cloud KMS. Parquet and JSON output encrypted at rest with KMS-managed keys. TLS 1.3 in transit. SOC 2 controls inherited.
Prometheus metrics exposed for extraction throughput, error rates, API latencies, queue depth per API surface. Grafana dashboards shipped. Plug into your existing observability stack.
Every OAuth2 token issuance, every API call across REST/OData/SOAP, every output write logged with user, timestamp, scope and result. Audit logs ship to SIEM via syslog or CloudTrail integration.
An acumatica data extraction tool is a piece of software that authenticates to an Acumatica tenant, calls the Contract-Based REST API, OData v4 endpoints and (where required) legacy SOAP web services, and streams the resulting data — JSON for REST, XML or Atom for OData, structured XML for SOAP — to a destination of your choice. Syntra ETL's acumatica data extraction tool authenticates via OAuth2 bearer flows with scoped client credentials, paginates through every endpoint, respects Acumatica's per-tenant API rate limits and concurrent session caps, handles 429 back-off transparently, captures modified-since watermarks for delta runs and hash-signs every output for downstream reconciliation. Output formats include Parquet for analytics, JSON Lines for downstream ETL, and FBDI/HDL for direct Oracle Fusion loading.
Custom REST/OData/SOAP clients against Acumatica always start cheap and end expensive. Acumatica exposes three distinct API surfaces — Contract-Based REST (the modern preferred path), OData v4 (preferred for bulk analytical pulls), and legacy SOAP (still required for some operations) — and each one has its own authentication model, pagination pattern, rate-limit behavior and quirks. A custom script that works for AP Bills via Contract-Based REST falls over on inventory transactions through OData (different pagination), then breaks again on legacy Generic Inquiry export through SOAP. Syntra ETL's acumatica data extraction tool ships pre-built support for every API surface, every endpoint, every quirk — backed by an SLA.
All three production API surfaces. Contract-Based REST API: every endpoint in the Default endpoint plus customer-defined endpoints, paginated correctly, with $expand for related entities. OData v4: every entity in the Generic Inquiry-derived OData service, ideal for bulk analytical pulls with $filter and $select pushdown. Legacy SOAP web services: Screen-Based API for screens that haven't been exposed through Contract-Based REST, including some specialized Generic Inquiry exports. Plus admin APIs for xRP customization metadata, Business Event configuration, Acumatica Report Designer reports and Dashboard definitions. New endpoints get folded in via quarterly extractor releases tracking Acumatica's own roadmap.
Acumatica's modern path is OAuth2 with authorization_code or client_credentials grant — Syntra ETL ships a vetted OAuth client pattern with scoped client credentials, automatic token rotation before expiry, encrypted credential storage in cloud KMS and SOC 2-compliant audit logging of every token issuance and API call. For older tenants that haven't enabled OAuth2 the extractor also supports the legacy /entity/auth/login + session-cookie pattern, with the same encrypted credential handling. No admin password is ever stored in plaintext, no service-account shortcuts are used, and OAuth scope can be reduced post-deployment without re-installing anything.
Yes. The extractor includes a built-in scheduler with cron syntax and supports modified-since delta extraction on every entity that exposes a LastModifiedDateTime field (which is virtually every transactional entity in Acumatica). Common schedules: nightly delta extract feeding a downstream data warehouse, weekly full-snapshot extract for backup, monthly Branch-by-Branch financial extract for management reporting. Each scheduled run produces a signed manifest (counts, sums, hashes per partition per Branch) plus a run log captured for SOC 2 audit. Failures surface as alerts through email, Slack, PagerDuty or webhook — no silent drift.
Three primary formats: Parquet (columnar, partitioned by fiscal year and Branch, ideal for downstream analytics in Athena/BigQuery/Snowflake/Spark), JSON Lines (newline-delimited JSON preserving the full Acumatica Contract-Based REST response shape including $expanded sub-entities, ideal for streaming pipelines), and Fusion-native loaders (FBDI ZIPs for GL/AP/AR/Item/PO/FA/PPM, HDL bundles for HCM context, REST API payloads for incremental delta loads). Custom output formats are configurable per entity. Generic Inquiry exports through OData v4 can also stream directly as CSV or Excel for downstream analyst consumption.
GL transactions, inventory transactions and AR/AP transactions are the highest-volume entities in any Acumatica tenant — typically millions of rows per fiscal year. The acumatica data extraction tool pulls them through OData v4 (which is better at bulk than Contract-Based REST), uses $filter pushdown on FinPeriodID and Branch to partition the extract, runs partitions in parallel against a configurable connection pool (default 10, matching Acumatica's typical concurrent session cap), and checkpoints progress per partition so a failed run resumes from the last successful partition rather than starting over. Throughput in production: roughly 500K–2M GL lines per hour per worker pod.
Yes. The acumatica data extraction tool authenticates with read-only OAuth2 scope (or read-only session for legacy auth), so no write operations ever touch the tenant. API calls are rate-limited to respect Acumatica's per-tenant API limits (default 10 concurrent sessions, configurable lower) so live order entry, AP processing and shop-floor operations are never throttled. Heavy extracts (multi-year GL detail, inventory transaction history, Generic Inquiry exports) are scheduled for off-peak windows. No Acumatica admin downtime is needed, no tenant configuration changes are required. Customers routinely run scheduled nightly extracts against live production tenants for years without a single user complaint.
30-minute discovery call. We'll scope your Acumatica modules, Branch structure, Generic Inquiry inventory, OAuth2 setup and downstream destination — and have a working extract running on your tenant within a week.