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?

Built for any business that runs on operations

Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.

What you can run on it

Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.

Affordable, accessible, fully customizable — and we mean each word

Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.

Industries we configure for

Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.

What happens when you get in touch

A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.

Questions buyers ask before they commit

Do we have to move everything across at once?

No, and it is usually a poor idea. Most implementations start with the part of the business where the pain is sharpest — often quoting and job costing, or scheduling and field capture — and run it alongside what you use today until people trust it. Once that is steady, the next area follows. Moving everything in one weekend is how projects acquire the reputation they have; moving one process at a time is how they succeed.

What happens to the spreadsheets we already rely on?

They are the specification, not the enemy. A spreadsheet that has survived years of daily use encodes real decisions about how your business works, and the first job of implementation is to read it properly. Some become configured processes in the platform, some stay as spreadsheets because that is genuinely the right tool, and a few turn out to exist only because two systems could not talk to each other, and simply stop being needed.

Our process is unusual. Will we have to change how we work?

The unusual part is often the thing that makes you competitive, so bending it to fit software is the wrong trade. The platform is configured around your process rather than the other way round. Where we do push back is on process that exists to work around a previous system's limitations — that is worth removing rather than reproducing.

How long before it is actually running?

Sooner than a traditional enterprise rollout, because the scope is deliberately narrow at first. A single well-chosen process can be live and useful while the rest is still being planned. What extends timelines is almost never the software — it is data cleanliness and decision-making on the customer side, which is why we agree early who owns which decision.

What happens to our data if we stop using it?

It leaves with you in a usable form. Ask this of every vendor you evaluate, and treat a vague answer as an answer. Being able to exit is what keeps a supplier relationship honest, and a platform confident in its value has no reason to make leaving difficult.

Do we need someone technical on staff to keep it running?

No. It runs in a browser and on a phone, and day-to-day administration — adding users, adjusting a workflow, changing a form — is designed to be done by the people who run the business rather than by a specialist. Deeper changes are a conversation with us, not a recruitment exercise.

Will this help us pass a client or accreditation audit?

It is built for it. The things audits actually ask for — that the person who did the work was qualified at the time, that the equipment was in calibration, that the procedure revision in force was the one followed, and that the records can be produced on request — are held as records with dates rather than as folders someone has to search. The difference at audit is between retrieving evidence and reconstructing it.

What happens when a qualification or calibration is about to expire?

You are told before it lapses rather than after. Expiry is tracked against the person or the instrument, and the warning arrives while there is still time to act, which is the difference between rescheduling work and cancelling it.

Still deciding? A short conversation beats a feature list. Tell us what you are trying to fix, or see the modules and sector configurations.

Compare the platform before you shortlist

Most companies arrive at a city page and actually want one of three things. If you are evaluating systems, start with NDT inspection software — what inspection companies actually need. If report turnaround is the pain, go to NDT reporting software compared. If the question is whether a generic system could work, read why generic ERP breaks on inspection work and the NetSuite comparison.

Request a demo or a tailored quote — tell us methods, levels, headcount and timing, and a consultant calls you back prepared.

Also useful: inspection management software for companies inspecting other people's assets, the full business management platform, and the evaluation checklist to run vendors against before you demo anything.