Catalogue › Integration and Data

Integration and Data

Use it in Copilot Cowork: download the Integration and Data plugin for Copilot Cowork and upload it in Cowork under Customize > Plugins > Upload plugin. How to install.

Moving data in and out of CRM: integration architecture, ERP and Project Operations touchpoints, migration strategy, mapping and cleansing, mock migrations and reconciliation.

Layer Delivery

Lead role modelled Integration Architect and Data Migration Lead

Subject lead Simon Foote

Agent charter .claude/agents/integration-and-data.md

Install

Claude Code:

/plugin marketplace add SimonFoote-greensparx/d365forge
/plugin install integration-and-data@d365forge

ChatGPT and Codex: add this repository as a plugin marketplace, or copy this folder into .agents/skills/ in your project.

Skills

Skill What it covers Status

integration-and-data:data-mapping-and-cleansing Produces the field-level mapping from legacy sources to Dataverse and the cleansing rules that make data loadable and trustworthy, covering deduplication, alternate keys, choice values, lookups and owners. Use when building the migration mapping, agreeing duplicate rules, or deciding how legacy codes map to choice columns. reviewed

integration-and-data:erp-and-project-touchpoints Defines, from the CRM side, what crosses between Dynamics 365 CE and the ERP or Project Operations, covering customers, products and pricing, orders, invoices, inventory and time. Use when agreeing master data ownership with finance, scoping quote to cash or time to billing, or deciding whether dual-write applies. reviewed

integration-and-data:integration-architecture Designs how Dynamics 365 CE exchanges data with other systems, choosing the pattern, timing, identity and error handling for each interface. Use when building the integration inventory, choosing between Power Automate, Logic Apps, Service Bus, Functions or virtual tables, deciding sync or async, or planning retries, throttling and monitoring. reviewed

integration-and-data:migration-strategy Sets the overall approach for moving legacy CRM, spreadsheet and mailbox data into Dataverse, covering scope, history cut-off, load order, owners and users, tooling and cutover approach. Use when deciding what to migrate, choosing migration tools, sequencing loads around lookups, or estimating the migration workstream. reviewed

integration-and-data:mock-migrations Plans and runs rehearsal migrations into non-production environments, recording timings, error rates and defects and tuning throughput until the load fits the cutover window. Use when scheduling mock loads, setting entry and exit criteria, investigating slow or failing loads, or preparing the dress rehearsal before go-live. reviewed

integration-and-data:reconciliation Proves that migrated or integrated data arrived complete and correct, using record counts, financial and quantity totals, relationship checks and business sample reviews, ending in signed acceptance. Use when defining reconciliation checks, investigating count mismatches after a load, or gathering migration sign-off for go/no-go. reviewed

Skill	What it covers	Status
`integration-and-data:data-mapping-and-cleansing`	Produces the field-level mapping from legacy sources to Dataverse and the cleansing rules that make data loadable and trustworthy, covering deduplication, alternate keys, choice values, lookups and owners. Use when building the migration mapping, agreeing duplicate rules, or deciding how legacy codes map to choice columns.	reviewed
`integration-and-data:erp-and-project-touchpoints`	Defines, from the CRM side, what crosses between Dynamics 365 CE and the ERP or Project Operations, covering customers, products and pricing, orders, invoices, inventory and time. Use when agreeing master data ownership with finance, scoping quote to cash or time to billing, or deciding whether dual-write applies.	reviewed
`integration-and-data:integration-architecture`	Designs how Dynamics 365 CE exchanges data with other systems, choosing the pattern, timing, identity and error handling for each interface. Use when building the integration inventory, choosing between Power Automate, Logic Apps, Service Bus, Functions or virtual tables, deciding sync or async, or planning retries, throttling and monitoring.	reviewed
`integration-and-data:migration-strategy`	Sets the overall approach for moving legacy CRM, spreadsheet and mailbox data into Dataverse, covering scope, history cut-off, load order, owners and users, tooling and cutover approach. Use when deciding what to migrate, choosing migration tools, sequencing loads around lookups, or estimating the migration workstream.	reviewed
`integration-and-data:mock-migrations`	Plans and runs rehearsal migrations into non-production environments, recording timings, error rates and defects and tuning throughput until the load fits the cutover window. Use when scheduling mock loads, setting entry and exit criteria, investigating slow or failing loads, or preparing the dress rehearsal before go-live.	reviewed
`integration-and-data:reconciliation`	Proves that migrated or integrated data arrived complete and correct, using record counts, financial and quantity totals, relationship checks and business sample reviews, ending in signed acceptance. Use when defining reconciliation checks, investigating count mismatches after a load, or gathering migration sign-off for go/no-go.	reviewed

Credit and licence

Created by Simon Foote and Robert Peledie as part of D365Forge. The skills are licensed under CC BY 4.0: use them freely, including commercially, and credit Simon Foote and Robert Peledie when you share or adapt them. NOTICE.md gives the wording.