Can Close and Microsoft 365 sync in both directions?

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.

How fast does the Close to Microsoft 365 sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

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.

How do I map Close fields to Microsoft 365?

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.

What should I do if a record fails to sync?

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.

What does a Close and Microsoft 365 integration cost?

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.

Which records should the Close and Microsoft 365 pilot start with?

Start by reviewing Contacts in Close and Contacts in Microsoft 365. 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.

What should be ready before the Close and Microsoft 365 initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Close account, edition, environment, and business objects the integration must access. Identify the Microsoft 365 account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

CRM / Business productivity

Close and Microsoft 365 integration

Plan how Close and Microsoft 365 should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Microsoft 365

Review the integration scope

Teams building with Stacksync

Plan the connection your business needs

Explore a Close and Microsoft 365 integration with a Stacksync engineer. Stacksync support for Close and Microsoft 365 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.

01 / Business process

Start with one meaningful update

Identify the record that changes in Close or Microsoft 365, where it needs to appear, and which team depends on it.

02 / Data access

Establish the available connection

Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.

03 / Success criteria

Define a result you can verify

Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.

Explore the technical references

Technical referenceAvailable documentation, candidate record relationships, and questions for your technical review.

What records can you sync?

Explore the record types and read/write requirements for each system.

CloseConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Leads	Confirm support for this record type and the direction you need.
Contacts	Confirm support for this record type and the direction you need.
Opportunities	Confirm support for this record type and the direction you need.
Activities	Confirm support for this record type and the direction you need.
Tasks	Confirm support for this record type and the direction you need.
Custom Activities	Confirm support for this record type and the direction you need.

Discuss Close requirements

Microsoft 365Connection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Users	Confirm support for this record type and the direction you need.
Groups	Confirm support for this record type and the direction you need.
Mail Messages	Confirm support for this record type and the direction you need.
Calendar Events	Confirm support for this record type and the direction you need.
Contacts	Confirm support for this record type and the direction you need.
OneDrive Files (driveItems)	Confirm support for this record type and the direction you need.

Discuss Microsoft 365 requirements

Connection requirements and limits

Close

Integration interface: REST API
Authentication: Confirm the credentials, API plan, and permissions required for Close.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Close and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Microsoft 365

Integration interface: REST API (Microsoft Graph)
Authentication: Confirm the credentials, API plan, and permissions required for Microsoft 365.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Microsoft 365 and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare your technical review

Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.

Implementation reference

Record identity and field ownership

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, ownership, and test cases

Record matchingContacts Contacts

Compare whether Close Contacts and Microsoft 365 Contacts describe the same contact in your business.

Close: Object support to establish
Microsoft 365: Object support to establish

Record identity

Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.

Field ownership

Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

Source person ID
Display name
Email address
Organization reference
Consent state

Record matchingUsers Users

Compare whether Close Users and Microsoft 365 Users describe the same application user or identity in your business.

Close: Object support to establish
Microsoft 365: Object support to establish

Record identity

Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.

Field ownership

Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes.

Fields to include

Source user ID
Tenant reference
Account status
Group references

Record matchingTasks Planner & To Do Tasks

Compare whether Close Tasks and Microsoft 365 Planner & To Do Tasks describe the same task or work item in your business.

Close: Object support to establish
Microsoft 365: Object support to establish

Record identity

Use a stable task/work-item ID and preserve its project or parent-ticket reference.

Field ownership

Choose the owner of task status and assignment; destination workflow states may require an explicit transition.

Fields to include

Source task ID
Parent reference
Assignee
Status
Due date

Architecture decision

Choose how to connect your systems

Choose a method around one example record and the update your business needs. Use Contacts / Contacts 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.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Close and Microsoft 365 record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Contacts / Contacts, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Close and Microsoft 365 need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time Close / Microsoft 365 migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow reference

From a business event to the right update

Open a workflow to see its trigger, record relationships, and expected result.

Contact sync test

Starting event: A change to the selected Contacts or Contacts record needs a defined result in the other system.

Start with Close Contacts and Microsoft 365 Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the organization relationship and any owner or consent references required by the destination.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.

If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Application user or identity sync test

Starting event: A change to the selected Users or Users record needs a defined result in the other system.

Start with Close Users and Microsoft 365 Users. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve tenant and group references and establish a protected administrative-account policy.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a renamed login, disabled account, missing group, and a user existing in two tenants.

If it fails: Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.

Task or work item sync test

Starting event: A change to the selected Tasks or Planner & To Do Tasks record needs a defined result in the other system.

Start with Close Tasks and Microsoft 365 Planner & To Do Tasks. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve project, user, and parent-item references before the task.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones.

If it fails: Reconcile the destination state before retrying a transition to avoid reopening completed work.

Plan the customer lifecycle across Close and Microsoft 365

Starting event: A customer-facing change in Close needs operational context in Microsoft 365.

Select the relevant Leads or Contacts records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.

Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.

If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.

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 Microsoft 365.

Microsoft 365 Close Direction requires confirmation

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 Close.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Close and Microsoft 365 access

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.

Close setup checklist

Identify the Close account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Close, including read/write support, authentication, and initial-load limits.

Microsoft 365 setup checklist

Identify the Microsoft 365 account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Microsoft 365, including read/write support, authentication, and initial-load limits.

Prepare to go live

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 Close and Microsoft 365 planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Security and control for your integrations

Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.

Explore security controls

FAQ