Two-way sync
Changes in Amazon SES or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon SES and Microsoft Dynamics 365 Sales in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Microsoft Dynamics 365 Sales holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. Amazon SES is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.
Stacksync syncs Activities, Custom Tables, Accounts, Contacts in Microsoft Dynamics 365 Sales with Email Templates, Suppression List, Verified Identities, Configuration Sets in Amazon SES field by field, in real time, and in both directions. Current contact details flow out to Amazon SES so it can reach the right person, and the calls, messages, and meetings Amazon SES produces flow back onto the matching record in Microsoft Dynamics 365 Sales. You decide which system owns which fields, and conflicts resolve by rules you set.
A number, address, or unsubscribe recorded in either system updates the other, so no one calls a disconnected line or messages someone who opted out.
A contact created or updated in Microsoft Dynamics 365 Sales appears in Amazon SES within seconds, so outreach starts without exporting a list or re-keying numbers.
Names, phone numbers, email addresses, and the owning rep from Microsoft Dynamics 365 Sales stay current in Amazon SES, so every call, text, or email goes to the right person at the right address.
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.
| Amazon SES objects | Microsoft Dynamics 365 Sales objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Subscribers in the contact list with per-topic opt-in state; CRUD via CreateContact/ListContacts/UpdateContact/DeleteContact, each carrying a LastUpdatedTimestamp for polling. | Contacts Person records linked to accounts; synced with marketing and support systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Messages (SendEmail / SendBulkEmail) Outbound email is produced via SendEmail and SendBulkEmail, accepting raw MIME or a template plus destination list. Send-only; there is no message store to read back. | Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. | Messages (SendEmail / SendBulkEmail) is specific to Amazon SES and Invoices to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Contact Lists One list per AWS account, subdivided into Topics that group subscriptions; read and write via CreateContactList and GetContactList. | Activities Emails, calls, appointments, and tasks; read out for activity analytics. | Contact Lists is specific to Amazon SES and Activities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Email Templates Reusable subject/HTML/text templates with replacement variables; synced via CreateEmailTemplate, GetEmailTemplate, ListEmailTemplates, and UpdateEmailTemplate. | Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. | Email Templates is specific to Amazon SES and Custom Tables to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Suppression List Addresses auto-added on bounce or complaint; read with ListSuppressedDestinations and written with Put/DeleteSuppressedDestination to control re-sends. | Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | Suppression List is specific to Amazon SES and Accounts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side. | |
| Verified Identities Email-address and domain identities cleared to send; managed via CreateEmailIdentity, ListEmailIdentities, GetEmailIdentity (DKIM and verification status). | Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Verified Identities is specific to Amazon SES and Leads to Microsoft Dynamics 365 Sales — 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.
DetectionAmazon SES notifies Stacksync of record changes through webhook events. Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations.
DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.
DeliveryEach detected change is written to Amazon SES through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon SES–Microsoft Dynamics 365 Sales connection.
Changes in Amazon SES or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon SES or Microsoft Dynamics 365 Sales data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon SES or Microsoft Dynamics 365 Sales record.
Track your Amazon SES ⇄ Microsoft Dynamics 365 Sales sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon SES and Microsoft Dynamics 365 Sales.
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 Amazon SES and Microsoft Dynamics 365 Sales 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 Amazon SES and Microsoft Dynamics 365 Sales 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 Amazon SES and Microsoft Dynamics 365 Sales: authenticate both systems, choose the objects to sync (such as Amazon SES's Contacts and Messages (SendEmail / SendBulkEmail)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Microsoft Dynamics 365 Sales: Alternate keys allow upserts against external identifiers, so integrations do not need to store Dataverse GUIDs to write reliably. Amazon SES: Sending events aren't retrievable via any SES API; they must be captured through a configuration-set event destination (SNS/EventBridge/Firehose/CloudWatch). Stacksync's field mapping accounts for these differences between Amazon SES and Microsoft Dynamics 365 Sales 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 Amazon SES and Microsoft Dynamics 365 Sales records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon SES and Microsoft Dynamics 365 Sales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon SES–Microsoft Dynamics 365 Sales integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon SES and Microsoft Dynamics 365 Sales. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Amazon SES: Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations (SNS/EventBridge/Firehose); contacts, templates, and suppression entries are polled via List/Get operations. On Microsoft Dynamics 365 Sales: Dataverse change tracking with delta tokens, plus registered webhooks on table events. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 335 integrations available for Amazon SES and Microsoft Dynamics 365 Sales.