NDT ERP Integration Matrix: 10 Systems, Fields, and Setup Time

A transparent row-by-row reference for every integration Atlantis NDT Suite supports out of the box, plus the custom API path for everything else. Use this page to scope your integration project before you sign a contract with any NDT ERP vendor.

The matrix below covers 10 integration targets across financial ERP, EAM (enterprise asset management), CRM, and no-code middleware. For each system we publish the integration method (native connector, REST API, Zapier, or file-based), typical setup time, data sync direction (one-way or two-way), the specific fields that flow, and known constraints. This is the same scoping document we send to prospective customers during pre-sales, so there is no fluff.

Three rules we have learned after 100+ integration projects: (1) always designate one system as the master of record for each master-data object before you start, (2) financial posting should be one-way out of the NDT ERP into the financial ERP to avoid two reconciliation sources of truth, and (3) start with a 2-week proof-of-concept on a sandbox before committing to a full production rollout.

SAP S/4HANA is the most common financial backbone in global super-majors (ExxonMobil, Shell, Chevron, Aramco, ADNOC). The integration pattern is predictable: Atlantis NDT Suite owns the inspection workflow and the technician-facing UX, SAP owns financial consolidation and global master data. Master data syncs two-way, financial documents post one-way from Atlantis into SAP FI-AR. Oracle Fusion follows the same pattern via Oracle Integration Cloud. Dynamics 365 F&O is simplest of the three because Dataverse + Dual-write handles the plumbing.

Plan 4-6 weeks for SAP, 3-5 weeks for Oracle, 2-4 weeks for Dynamics. Budget $15K-$60K for the integration project itself, separate from the NDT ERP license. Always run a 2-week UAT with a subset of real inspection jobs before cutover.

In asset-intensive industries (pipelines, refineries, power gen, petrochem) the EAM — most commonly IBM Maximo — is the system of record for equipment and work orders. The Atlantis-Maximo integration pushes Work Orders from Maximo into Atlantis as inspection Jobs, captures findings in the field, and writes back to the Maximo Service Request and Inspection Result objects. Equipment master syncs two-way with Maximo as the master of record.

For inspection companies under $25M revenue, QuickBooks Online or Xero is typically the financial system. Both integrations are self-serve through OAuth and take about 30 minutes to wire up. Customers, items, invoices, and payments sync bi-directionally on a 15-minute schedule (or real-time via webhook).

Salesforce integration is most common for enterprise inspection companies running Field Service Lightning. HubSpot is typical for growth-stage inspection businesses managing inbound leads. Zapier covers the long tail of no-code automations: Slack alerts, email digests, spreadsheet sync. Any system we do not support natively can be wired via our OpenAPI spec in 2-6 weeks.

Three anti-patterns account for roughly 70% of integration failures we see in NDT ERP deployments. The first is dual-write without a clear master of record. If both SAP and the NDT ERP can edit the equipment master, you will eventually get conflicting edits, race conditions, and a painful reconciliation process. Fix: designate one system as authoritative for each object before the first line of integration code is written, and document it in the integration design.

The second anti-pattern is batching all integrations into a single big-bang go-live. Integration projects are easier to deliver and easier to debug when they are sequenced: financial integration in Phase 1, EAM integration in Phase 2, CRM in Phase 3, and no-code workflows in Phase 4. Big-bang means if one integration is late, the whole cutover slips. Phased means you start delivering business value in Week 6, not Week 20.

The third anti-pattern is over-engineering real-time sync where scheduled sync would work fine. Most master data changes infrequently enough that a 15-minute or hourly sync is completely adequate and dramatically simpler to build, test, and operate. Reserve real-time for the handful of objects where latency truly matters: job status updates for on-site supervisors, defect escalation alerts, and financial posting to the GL at invoice signing.

Every Atlantis integration supports OAuth 2.0 or API key authentication over TLS 1.3. For enterprise customers, we also support mutual TLS and IP allowlisting on the integration edge. All API calls are logged with full request/response payloads for 90 days by default (extendable to 7 years for SOX or API-regulated customers) so you have a complete audit trail. Role-based access control (RBAC) is enforced on every endpoint, and integration service accounts are treated as first-class principals with their own permission sets.

For customers with heightened compliance requirements (aerospace ITAR, nuclear 10 CFR, government regulated data), we offer private-cloud and on-premise deployments of the integration layer. The integration contracts (APIs, webhooks, file formats) are identical, only the runtime topology changes. This matters because it means you can start on the SaaS integration in Phase 1, and migrate to private cloud in Year 2 or 3 without rewriting your integration code.

Native connectors (QuickBooks, Xero, HubSpot, Zapier, Dynamics 365 via Dataverse) are included in the standard Atlantis NDT Suite license at no extra charge. You configure them yourself through the admin console. Enterprise connectors (SAP S/4HANA, Oracle Fusion, IBM Maximo, Salesforce with custom objects, custom REST/GraphQL) are scoped as implementation projects and typically run $15K-$60K one-time plus a modest ongoing support uplift of $3K-$12K per year per system.

File-based integration (SFTP drop of CSV/XML on a schedule, for legacy systems without APIs) is supported out of the box and usually configurable in 2-5 days. Webhook subscriptions to your external systems are free on all tiers. Dedicated sandbox environments for integration testing are included for the duration of an implementation project and available on-demand post go-live for regression testing before major release cycles.

Send us your current tech stack. We will return a scoped integration plan within 48 hours.

What this page covers

How to read this matrix
Financial ERP tier: SAP, Oracle, Dynamics
EAM tier: IBM Maximo
SMB accounting tier: QuickBooks, Xero
CRM and middleware tier: Salesforce, HubSpot, Zapier, custom API
Integration anti-patterns to avoid
Authentication, security, and audit
Pricing: what integrations actually cost
Have a system not on this list?