Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Plan how Dynamics 365 F&O and Microsoft Dynamics GP should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
Proposed workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Dynamics 365 F&O Customers or Microsoft Dynamics GP Customers needs a defined result in the other system.
Start with Dynamics 365 F&O Customers and Microsoft Dynamics GP Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipProposed record relationships
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Dynamics 365 F&O record | Microsoft Dynamics GP record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.Record matching | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| VendorsProposed record; confirm Stacksync object support.Record matching | VendorsProposed record; confirm Stacksync object support. | Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries. | Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process. |
| General Journal EntriesProposed record; confirm Stacksync object support.Record matching | GL Accounts & Journal EntriesProposed record; confirm Stacksync object support. | Retain journal ID and line IDs within the legal entity and accounting period. | The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Requires account access and compatible change tracking. Confirm field permissions and sync direction. |
| Requires API exposure and compatible change tracking. Confirm field permissions and sync direction. |
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Dynamics 365 F&O | Microsoft Dynamics GP |
|---|---|---|
| Integration interface | OData REST endpoint over data entities, plus the Data Management Framework for batch | SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments |
| Authentication | OAuth via Microsoft sign-in | Confirm the credentials, API plan, and permissions required for Microsoft Dynamics GP. |
| Change detection | Full and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Available for supported records | Confirm with Stacksync |
| Write access | Available for supported records | Confirm with Stacksync |
Enterprise controls
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:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize Dynamics 365 F\&O
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Dynamics 365 F&O and Microsoft Dynamics GP planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Record matching
Compare whether Dynamics 365 F&O Customers and Microsoft Dynamics GP Customers describe the same customer in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: Dynamics 365 F&O: Customers documentation
Record matching
Compare whether Dynamics 365 F&O Vendors and Microsoft Dynamics GP Vendors describe the same supplier or vendor in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: Dynamics 365 F&O: Vendors documentation
Record matching
Compare whether Dynamics 365 F&O General Journal Entries and Microsoft Dynamics GP GL Accounts & Journal Entries describe the same journal or ledger entry in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: Dynamics 365 F&O: General Journal Entries documentation
Record matching
Compare whether Dynamics 365 F&O On-hand Inventory and Microsoft Dynamics GP Inventory Items (IV) describe the same inventory or stock position in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: Dynamics 365 F&O: On-hand Inventory documentation
Record matching
Compare whether Dynamics 365 F&O Purchase Orders and Microsoft Dynamics GP Purchase Orders (POP) describe the same purchase order in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: Dynamics 365 F&O: Purchase Orders documentation
Choose a method around one example record and the update your business needs. Use Customers / Customers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Customers or Customers record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Vendors or Vendors record needs a defined result in the other system.
Expected result: Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
If it fails: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected General Journal Entries or GL Accounts & Journal Entries record needs a defined result in the other system.
Expected result: Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
If it fails: Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Dynamics 365 F&O needs operational visibility through Customers or Vendors.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
The expected supplier or vendor relationship is preserved with no duplicate action or unintended write.
Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
The expected journal or ledger entry relationship is preserved with no duplicate action or unintended write.
Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
The expected inventory or stock position relationship is preserved with no duplicate action or unintended write.
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Only an approved, supported direction and permitted fields are written.
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect Dynamics 365 F&O Customers and Microsoft Dynamics GP Customers, their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect Dynamics 365 F&O Vendors and Microsoft Dynamics GP Vendors, their IDs, and the destination error.
Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
Inspect Dynamics 365 F&O General Journal Entries and Microsoft Dynamics GP GL Accounts & Journal Entries, their IDs, and the destination error.
Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.
Check the Dynamics 365 F&O and Microsoft Dynamics GP connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesFull and incremental syncs use Dynamics change tracking where available; enable tracking on the selected entities.
Apply updatesConfirm that Stacksync can create or update the records you need in Microsoft Dynamics GP.
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Dynamics 365 F&O.
Explore a Dynamics 365 F&O and Microsoft Dynamics GP integration with a Stacksync engineer. Stacksync support for Microsoft Dynamics GP is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Provide the Dynamics environment URL and authorize the Stacksync app with Microsoft sign-in; arrange administrator consent if required. Identify the Microsoft Dynamics GP account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Customers in Dynamics 365 F&O and Customers in Microsoft Dynamics GP. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
Choose a method around one example record and the update your business needs. Use Customers / Customers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 413 integrations listed for Dynamics 365 F&O and Microsoft Dynamics GP.
Next step
Walk through your Dynamics 365 F&O and Microsoft Dynamics GP records, field mappings, and requirements with an integration engineer.
