Two-way sync
Changes in Infor CRM or Rollworks instantly reflect in both systems. No stale data, no manual imports.
Keep Infor CRM and Rollworks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Infor CRM owns the customer relationship and the pipeline; Rollworks runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.
Stacksync syncs Campaigns, Custom entities, Accounts, Contacts in Infor CRM with Target Account Lists, Account Tiers, Accounts (TAL Items), Audience Segments in Rollworks field by field, in real time, and in both directions. You decide which system owns which fields — Infor CRM can own account and opportunity status while Rollworks owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Opens, clicks, form fills, event attendance, or ad responses recorded in Rollworks post back to the contact or account in Infor CRM, so reps see interest before they reach out.
Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.
Where Rollworks builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Infor CRM, so who receives a campaign reflects current pipeline reality instead of a stale export.
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.
| Infor CRM objects | Rollworks objects | How this pairing syncs | |
|---|---|---|---|
| Campaigns Marketing containers linked to leads and opportunities. | Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Activities Calls, meetings, and tasks synced for engagement reporting. | Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. | Activities is specific to Infor CRM and Account Tiers to Rollworks — each maps to any object or custom field on the other side. | |
| Custom entities Deployment-specific objects added through the customizable entity model. | Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. | Custom entities is specific to Infor CRM and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side. | |
| Accounts Company records matched against ERP customer masters in syncs. | Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. | Accounts is specific to Infor CRM and Audience Segments to Rollworks — each maps to any object or custom field on the other side. | |
| Contacts Person records synced with marketing and support tools. | Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. | Contacts is specific to Infor CRM and Ad Groups and Ads to Rollworks — each maps to any object or custom field on the other side. | |
| Leads Unqualified records synced in from marketing sources. | Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. | Leads is specific to Infor CRM and Reporting and Attribution to Rollworks — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Infor CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified timestamps.
DeliveryEach detected change is written to Rollworks through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.
DeliveryEach detected change is written to Infor CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor CRM–Rollworks connection.
Changes in Infor CRM or Rollworks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor CRM or Rollworks data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Infor CRM or Rollworks record.
Track your Infor CRM ⇄ Rollworks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor CRM and Rollworks.
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.
Authenticate Infor CRM and Rollworks with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Infor CRM and Rollworks 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Infor CRM and Rollworks: authenticate both systems, choose the objects to sync (such as Infor CRM's Campaigns and Activities), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Infor CRM and Rollworks: Where Rollworks captures engagement: activity lands on the record; Lead and lifecycle status agree; Segments and audiences follow the CRM. Opens, clicks, form fills, event attendance, or ad responses recorded in Rollworks post back to the contact or account in Infor CRM, so reps see interest before they reach out.
Infor CRM: REST-style SData API over the CRM entity model. Authentication: User credentials; Infor OS-managed authentication in cloud deployments. Rollworks: REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API. Authentication: OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts. Stacksync manages authentication, retries, and rate limits on both sides.
Infor CRM: Infor CRM descends from SalesLogix and exposes the SData protocol, a REST-style API over its entity model. Rollworks: There is no change-notification webhook or CDC channel; account, audience, campaign, and reporting data must be polled, so freshness depends on the sync interval. Stacksync's field mapping accounts for these differences between Infor CRM and Rollworks 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 Infor CRM and Rollworks records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Infor CRM and Rollworks.