Skip to content
Database ⇄ Business productivity

IBM AS/400 to Microsoft 365 integration — real-time, two-way sync

Keep IBM AS/400 and Microsoft 365 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect IBM AS/400 and Microsoft 365

Mirror Microsoft 365's data into IBM AS/400 so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Microsoft 365 through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in IBM AS/400.

Stacksync mirrors Teams, Planner & To Do Tasks, Users, Groups from Microsoft 365 into Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400 and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Microsoft 365, so the tool and the database never disagree.

Common use cases

  • 01 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
  • 02 Sync SharePoint lists with operational databases so business users edit in SharePoint while systems read SQL.
  • 03 Expose AS/400 order, inventory, and item master data to modern SaaS tools without rewriting green-screen applications.
  • 04 Use journal-based change capture to replicate IBM i data into a cloud warehouse for reporting.

Common sync patterns

Read Microsoft 365 with a query

Records from Microsoft 365 are ordinary rows in IBM AS/400; join them, index them, and use them in application logic without touching the vendor API.

Automate Microsoft 365 from your codebase

Write to the synced tables in IBM AS/400 and Stacksync propagates the change into Microsoft 365, replacing custom integration code.

React to changes as they happen

Updates in Microsoft 365 arrive as row changes in IBM AS/400, so triggers, jobs, and services can respond in near real time.

What you can sync between IBM AS/400 and Microsoft 365

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

IBM AS/400 objects Microsoft 365 objects How this pairing syncs
Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. Teams Team and membership data provisioned from upstream systems. Data queues is specific to IBM AS/400 and Teams to Microsoft 365 — each maps to any object or custom field on the other side.
Libraries The schema-equivalent containers that scope which files a sync reads. Planner & To Do Tasks Task items synced with project and work-management tools. Libraries is specific to IBM AS/400 and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side.
Physical files (tables) The Db2 for i tables mapped directly to sync targets. Users Entra ID user accounts synced with HR and identity systems. Physical files (tables) is specific to IBM AS/400 and Users to Microsoft 365 — each maps to any object or custom field on the other side.
Logical files (views) Indexed or filtered views over physical files, usable as read sources. Groups Microsoft 365 and security groups kept aligned with org structure and access rules. Logical files (views) is specific to IBM AS/400 and Groups to Microsoft 365 — each maps to any object or custom field on the other side.
Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Mail Messages Exchange Online messages read for logging, archiving, or activity capture. Members is specific to IBM AS/400 and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side.
Rows / records The unit of read and write, accessed via SQL or record-level access. Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. Rows / records is specific to IBM AS/400 and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side.

How changes propagate between IBM AS/400 and Microsoft 365

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

IBM AS/400 Microsoft 365 Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.

Microsoft 365 IBM AS/400 Sub-second propagation

DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.

DeliveryEach detected change is applied to IBM AS/400 as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
What ships with IBM AS/400 ⇄ Microsoft 365

Connect IBM AS/400 and Microsoft 365 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM AS/400–Microsoft 365 connection.

Real-time

Two-way sync

Changes in IBM AS/400 or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever IBM AS/400 or Microsoft 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single IBM AS/400 or Microsoft 365 record.

Observability

Monitoring

Track your IBM AS/400 ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between IBM AS/400 and Microsoft 365.

How the IBM AS/400 and Microsoft 365 connectors work

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.

Microsoft 365

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
Change detection
Graph change notifications (webhooks) plus delta queries for incremental sync
Capabilities
read · write · webhooks
How it works

How to connect IBM AS/400 to Microsoft 365 — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate IBM AS/400 and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    IBM AS/400 connected
    Microsoft 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the IBM AS/400 and Microsoft 365 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · IBM AS/400 ⇄ Microsoft 365
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    IBM AS/400 Microsoft 365
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

IBM AS/400 and Microsoft 365 integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 384 integrations available for IBM AS/400 and Microsoft 365.

Popular · 6 of 384
All IBM AS/400 integrations All Microsoft 365 integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own