Damco

AS/400 integration services that connect the IBM i APIs and data feeds, so other systems stop waiting on file drops

Order sync, IBM i and SalesforceIllustrated
DirectionBoth ways, as orders change
MethodREST API on the IBM i
Today1,284 orders, no errors
ReplacedA nightly file drop

IBM i integration for every system that needs its data Real-time where it matters, scheduled where it doesn't, and recorded either way

Plan the integrationsIBM i integration consulting: which systems need what, how often, and how.
Build AS/400 APIsREST APIs over IBM i programs and data, secured and logged.
Integrate the databaseDb2 for i data fed to warehouses, BI tools and cloud platforms.
Connect ERP and CRMSAP, Salesforce, Dynamics 365 and the packages around your i.
Reach screens with no APIAgent 400 works the green screens when building an API isn't worth it.

How our AS/400 integration works Five steps, from your requirements to integrations that run every day

  1. Week 1Assess requirementsWhich systems need which data, how fresh, and what happens when one is down.
  2. Week 2Agree the modelA fixed project, a team, or integrations we build and run.
  3. Weeks 3 to 6Design and developAPIs, feeds and mappings built, each field confirmed by your team.
  4. Before launchTest and QASample records run through end to end, and every result is checked.
  5. After launchSupportWe watch every run and fix breaks when a system on either side changes.

When AS/400 integration is the right fit And when the system needs more than a connection

A good fit when

  • The IBM i works, but its data reaches other systems by file drop or retyping
  • A new portal, partner or AI project needs the i's data
  • Staff key the same order into the i and the CRM

Look elsewhere when

  • The programs behind the API need rewriting first: modernize them
  • You're leaving the platform soon: integrate the new system instead
  • The need is a one-off data extract, not a running connection

Our AS/400 integration services in detail What each kind of connection covers, and what it replaces

IBM i integration consulting

Most IBM i shops have grown dozens of connections over the years: FTP jobs, file drops, data queues, screen scrapers and custom programs. We list them, note which break most often, and plan what to replace and in what order.

AS/400 API integration

We expose IBM i programs and data as REST APIs, through IBM's Integrated Web Services or a gateway, with authentication, rate limits and a log of every call. The IBM i can also call other systems' APIs directly from RPG.

With APIs in place, portals, partners and AI agents reach the i the same way they reach any other system.

IBM i database, BI and cloud integration

Db2 for i data can feed a warehouse, Power BI, Snowflake or a cloud platform through scheduled loads or change data capture, so reports and AI work from fresh data without touching the programs.

  • Change data capture for near-real-time feeds
  • Nightly loads for reporting
  • Data reconciled against the source after every run

AS/400 ERP, CRM and EDI integration

We connect the IBM i to SAP, Salesforce, Microsoft Dynamics 365, warehouse systems and e-commerce platforms, and to trading partners through EDI. Each field is mapped in business terms and confirmed by your team.

Damco Switchboard has AI agents build each connection and prove it on sample records, and it then runs as plain, tested code in your cloud.

When there's no API: an agent on the green screens

Some tasks aren't worth an API. Agent 400 works the AS/400 green screens like your best user, from a chat, and shows which tasks run often enough to deserve an API next.

Questions about AS/400 integration What IT leaders ask us before connecting their IBM i

Can you help us plan IBM i integration?

Yes. We list the connections you have, find the ones that break or cost most, and plan what to replace with APIs or feeds, in order.

How much does an AS/400 integration project cost?

It depends on the number of systems, the data involved, and whether we run the integrations afterwards. We quote per integration after a short review, or as a monthly team.

Our existing AS/400 integrations keep failing. Can you help?

Yes. We review them, find why they fail, and either fix them or replace them with APIs or feeds that are tested and monitored.

How long does an IBM i integration project take?

One integration can be built in weeks. A program to replace dozens of old connections runs longer, one connection at a time, starting with the one that hurts most.

How do I measure whether an AS/400 integration worked?

By what it replaced: hours of retyping saved, orders that no longer wait for a nightly file, errors that stopped, and how often the integration fails. We report these every month.

Bring the AS/400 connection that keeps breaking

We'll tell you why it breaks and what we'd replace it with.