Real-time
Real-time sync
Changes in E2 Shop System or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
E2 Shop System to Microsoft 365 integration — real-time data sync
Keep E2 Shop System 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 E2 Shop System and Microsoft 365
Flow E2 Shop System data into Microsoft 365 in real time — no exports, no schedulers, no custom scripts.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Microsoft 365, so Microsoft 365 always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Microsoft 365 is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Common use cases
- Sync employee records from an HR system into Entra ID users and group memberships.
- Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
- Replicate job and work order status into a reporting database to power shop-floor and delivery dashboards.
- Sync customer and invoice data to accounting or CRM so the front office is not re-keying from the ERP.
Where Microsoft 365 faces customers and E2 Shop System carries account records
Order, invoice, or account status from E2 Shop System appears alongside the customer in Microsoft 365, so front-line teams answer from live data.
Where Microsoft 365 collects payments: transactions post through
Payment events sync into E2 Shop System as they occur, keeping the enterprise records current without manual entry.
Where E2 Shop System is the HR or people system of record
Worker and organization data from E2 Shop System stays current in Microsoft 365, so the tools people use daily reflect the org as it actually is.
What you can sync between E2 Shop System 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.
| E2 Shop System objects | Microsoft 365 objects | |
|---|---|---|
| Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. | Users Entra ID user accounts synced with HR and identity systems. | |
| Jobs / Work orders Released work with routings and status; the record shop-floor dashboards track. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | |
| Customers Buyer records synced to CRM or accounting counterparts. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | |
| Vendors Supplier records referenced on purchasing documents. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | |
| Parts Part masters with routings and material definitions specific to each shop. | Contacts Personal and org contacts kept consistent with CRM contact records. | |
| Routings / Operations Per-part operation sequences that carry estimated and actual times. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. |
What ships with E2 Shop System ⇄ Microsoft 365
Connect E2 Shop System and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever E2 Shop System 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 E2 Shop System or Microsoft 365 record.
Observability
Monitoring
Track your E2 Shop System ⇄ 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 E2 Shop System and Microsoft 365.
How the E2 Shop System and Microsoft 365 connectors work
E2 Shop System
- Integration surface
- No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
- Authentication
- Database credentials or application-level export access on the on-premises installation
- Change detection
- Polling database tables or scheduled exports
- Capabilities
- read
- Rate limits
- Not API-bound; constrained by on-premises database access windows
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 E2 Shop System 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.
- 01
Connect your apps
Authenticate E2 Shop System 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.
E2 Shop System
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the E2 Shop System 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.
objects · E2 Shop System ⇄ Microsoft 365Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
E2 Shop System Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
E2 Shop System and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between E2 Shop System and Microsoft 365 — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into Microsoft 365. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for E2 Shop System and Microsoft 365: Where Microsoft 365 faces customers and E2 Shop System carries account records; Where Microsoft 365 collects payments: transactions post through; Where E2 Shop System is the HR or people system of record. Order, invoice, or account status from E2 Shop System appears alongside the customer in Microsoft 365, so front-line teams answer from live data.
-
E2 Shop System: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment. Authentication: Database credentials or application-level export access on the on-premises installation. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Change notifications can push events for resources such as messages, events, and driveItems, with subscriptions that must be periodically renewed. E2 Shop System: E2 is a Windows-based job shop ERP from Shoptech, now part of ECI Software Solutions, where it has been rebranded as JobBOSS²; most installations run on premises. Stacksync's field mapping accounts for these differences between E2 Shop System and Microsoft 365 without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means E2 Shop System and Microsoft 365 records are not retained after a sync operation.
SECURITY
Security teams love 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.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for E2 Shop System and Microsoft 365.
Popular · 8 of 386
-
E2 Shop System ⇄ Customer.io -
E2 Shop System ⇄ eClinicalWorks -
E2 Shop System ⇄ Full Enrich -
E2 Shop System ⇄ Google Sheets -
Microsoft 365 ⇄ QAD ERP -
Microsoft 365 ⇄ Rootstock ERP -
Microsoft 365 ⇄ Sage 100 - Microsoft 365 ⇄ Sage 300
No integrations match .
