Sage 300 and Marketo integration

What moves between them

The main flow runs from Sage 300 into Marketo. ml-connector polls Sage 300's ARCustomers endpoint on a schedule and syncs matching customer records into Marketo companies. When enabled, order data from Sage 300's OEOrders and ARInvoiceBatches flows into Marketo as enrichment on company records. Purchase order data can also flow to track vendor relationships and supply chain activity. The sync is one-way: Sage 300 serves as the source of truth for customer master data and transactional history, while Marketo uses that data to enhance lead scoring, segmentation, and campaign targeting.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Sage 300 side, it constructs the full IIS-based API URL per customer, encodes the uppercase username and password in the Authorization header per every request, and polls ARCustomers using OData date filters to fetch new and modified records. It pages through results using OData $skip and $top parameters. On the Marketo side, ml-connector exchanges the Client ID and Client Secret for a Bearer token, refreshes the token before expiry, and posts the transformed customer records into the Marketo companies endpoint in batches of up to 300 records. Because both systems are polling-only, ml-connector runs on a schedule tied to your order entry cycle rather than waiting for a push. Customer names, addresses, and identifiers are mapped from Sage 300 to Marketo company fields, and optional invoice and order totals enrich the company record for scoring rules. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-market B2B software vendor manages customer orders and invoices in Sage 300 ERP, and runs account-based marketing campaigns in Marketo. Before the integration, the marketing team maintained a separate customer list in a spreadsheet and updated it monthly after the sales team exported reports from Sage 300. Campaign targeting was always stale, and the account team never saw order history in Marketo's lead timeline. With Sage 300 and Marketo connected, new customer orders sync into Marketo on a daily cadence, enriching each company record with the latest invoice total and order count. Marketing campaigns now segment on real order activity, the account team sees customer order history in the lead timeline, and the manual data work is gone.

What you can do

• •Sync Sage 300 customer master data into Marketo companies on a schedule you control.
• •Enrich Marketo company records with Sage 300 order totals and invoice history.
• •Handle Sage 300 HTTP Basic Auth with uppercase credentials and OData pagination, and exchange Marketo OAuth2 Client Credentials for a Bearer token.
• •Poll both systems on your order entry cycle with full retry logic and an audit trail on every record.
• •Map custom Sage 300 customer fields to Marketo company custom objects for scoring and segmentation.

Questions

Which direction does data move between Sage 300 and Marketo?

The main flow is Sage 300 into Marketo. Customer master data and order history from Sage 300 sync into Marketo companies to enrich marketing targeting and lead scoring. Marketo itself does not push changes back to Sage 300, so Sage 300 remains the source of truth for customer and order data.

How does ml-connector handle the different authentication methods?

Sage 300 uses HTTP Basic Authentication with uppercase username and password in every request header, while Marketo uses OAuth2 Client Credentials to exchange a Client ID and Secret for a Bearer token. ml-connector stores both credential sets encrypted, constructs the correct authorization headers and token exchanges for each system, and refreshes the Marketo token before it expires.

Does the integration require internet connectivity from the Sage 300 server?

Yes. Because Sage 300 is on-premise and self-hosted, the IIS server must have outbound HTTPS access to Marketo's mktorest.com REST API. The Sage 300 API user must be created in Administrative Services with Web API permissions, and the IIS Anonymous Authentication must be enabled while Windows Authentication is disabled.