Dynamics 365 & SharePoint Integration
Budget: $50 – $0 AUD
I need Dynamics 365 deployed in my existing Microsoft 365 tenant and configured so it works seamlessly with the rest of our stack.
Phase 1 – Core deployment and data migration
• Install and license Dynamics 365, making sure Copilot is available.
• Import every ACT! contact into Dynamics, merge duplicates, and preserve history so the new system starts clean.
Customise fields for mapping.
• Turn on native SharePoint integration; files that already sit in SharePoint must appear against the matching contact automatically by contact name—no manual tagging.
• Connect Microsoft Teams for effortless file-sharing and meeting scheduling straight from a contact record.
• Add Outlook tracking so every email on that address shows in the timeline.
Phase 2 – Eliminate double entry
Build a client “fact-find” form (Power Apps or a native Dynamics form, whichever is faster) that feeds data directly into the contact and related tables. The goal is for staff to complete one form and never re-type details elsewhere.
Acceptance criteria
– Users log in with existing tenant credentials and see Dynamics 365 in the app launcher.
– A sample contact shows linked SharePoint documents without manual work.
– Scheduling a Teams meeting and sharing a file from within Dynamics succeeds first try.
– An email sent from Outlook appears on the contact’s timeline within minutes.
– The fact-find form writes back to the contact record with no duplicate fields created.
If you have proven experience integrating Dynamics 365 with SharePoint, Teams (file sharing + meeting scheduling), Outlook email tracking, and have handled ACT! migrations before, let’s talk.
Phase 1 – Core deployment and data migration
• Install and license Dynamics 365, making sure Copilot is available.
• Import every ACT! contact into Dynamics, merge duplicates, and preserve history so the new system starts clean.
Customise fields for mapping.
• Turn on native SharePoint integration; files that already sit in SharePoint must appear against the matching contact automatically by contact name—no manual tagging.
• Connect Microsoft Teams for effortless file-sharing and meeting scheduling straight from a contact record.
• Add Outlook tracking so every email on that address shows in the timeline.
Phase 2 – Eliminate double entry
Build a client “fact-find” form (Power Apps or a native Dynamics form, whichever is faster) that feeds data directly into the contact and related tables. The goal is for staff to complete one form and never re-type details elsewhere.
Acceptance criteria
– Users log in with existing tenant credentials and see Dynamics 365 in the app launcher.
– A sample contact shows linked SharePoint documents without manual work.
– Scheduling a Teams meeting and sharing a file from within Dynamics succeeds first try.
– An email sent from Outlook appears on the contact’s timeline within minutes.
– The fact-find form writes back to the contact record with no duplicate fields created.
If you have proven experience integrating Dynamics 365 with SharePoint, Teams (file sharing + meeting scheduling), Outlook email tracking, and have handled ACT! migrations before, let’s talk.