IFS Cloud and Marketo integration

What moves between them

Customer and company records flow from IFS Cloud into Marketo. Sales orders from IFS Cloud are transformed into Marketo opportunity records. GL accounts and company codes from IFS Cloud are mapped to Marketo company records so that sales opportunities are tagged with the ERP's accounting dimensions. Reference data flows in both directions so that Marketo campaigns can be allocated to the correct IFS Cloud GL accounts and cost centers. The sync runs on a regular schedule; since both systems are pull-only, ml-connector polls IFS Cloud for new or modified customers and sales orders at intervals you define, then writes or updates the corresponding lead and opportunity records in Marketo.

How ml-connector handles it

ml-connector stores the OAuth2 credentials for both IFS Cloud and Marketo encrypted and handles token refresh transparently as each bearer token approaches expiry. On the IFS Cloud side, it constructs OData query filters on the modified timestamp and company code fields to pull only new or changed records, respecting the 5000-element page limit and backing off on HTTP 429 rate limit responses. It reads each customer record to capture the ETag header (required by IFS Cloud's optimistic concurrency model) before writing changes. On the Marketo side, it batches customer and opportunity records in groups of up to 300 per request and upserts them by external ID so that repeated syncs update existing records rather than creating duplicates. The GL accounts and company codes from IFS Cloud are mapped during the transform step so that each Marketo opportunity record carries the ERP dimension it came from. Every record includes a full audit trail, and if a Marketo upsert fails partway through a batch, ml-connector can retry just the failed records without replaying the entire batch.

A real-world example

A manufacturing and field service company uses IFS Cloud to manage production, asset service calls, project finance, and procurement across multiple regions. The sales team uses Marketo to nurture leads, manage inbound campaign inquiries, and track opportunities. Before integration, the sales team tracked their own customer and opportunity records in Marketo, updated manually from spreadsheets exported from IFS Cloud after each month-end close. This meant marketing campaigns targeted outdated customer lists, opportunities fell out of sync with actual orders in the ERP, and sales reps lost visibility into which accounts were active or at risk. With IFS Cloud and Marketo connected, every new customer entered in the ERP and every new sales order flow into Marketo on a daily schedule. Campaigns now target the current customer list, opportunity records stay synchronized with actual order flow, and sales teams can see which customers have active orders and which are dormant, without manual updates or email.

What you can do

• •Sync IFS Cloud customers into Marketo company records, keeping marketing campaigns aligned with ERP master data.
• •Transform IFS Cloud sales orders into Marketo opportunities and link them to the correct companies and GL accounts.
• •Map IFS Cloud company codes and GL accounts to Marketo company and opportunity fields for multi-dimensional reporting.
• •Poll IFS Cloud and Marketo on a daily schedule, handling OAuth2 token refresh and OData pagination automatically.
• •Upsert records by external ID in Marketo so repeated syncs update existing records and prevent duplicates.

Questions

Which direction does data flow between IFS Cloud and Marketo?

The main flow is from IFS Cloud into Marketo. Customers, sales orders, GL accounts, and company codes move from the ERP into Marketo as company and opportunity records. Marketo's lead and opportunity records are not written back to IFS Cloud, so the integration is unidirectional at the record level, though reference data such as company codes can be aligned in both directions.

How does the integration handle IFS Cloud's lack of webhooks?

ml-connector polls IFS Cloud on a regular schedule (daily by default) using OData query filters on the modified timestamp field. This is the same pattern as polling any read-mostly API. IFS Cloud's Event Actions could trigger notifications if configured per customer, but polling is the standard approach and does not require manual admin configuration.

What happens if a Marketo batch upsert partially fails?

ml-connector tracks which records succeeded and which failed, and retries only the failed records in the next sync cycle without replaying the entire batch. Each record includes an audit entry showing whether it was synced, updated, or failed to upsert, so you can trace any Marketo record back to its IFS Cloud source and see the full history of sync attempts.