Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The company must explicitly assign ongoing ownership for every custom ERP integration. The owner may be the original implementation partner under a support agreement, internal IT or an ERP team, a replacement integration partner, or an application management services (AMS) provider. The fact that a partner built an integration does not, by itself, mean it will maintain it after the project ends.
Start with the support agreement and statement of work: they determine who handles connector code, monitoring, credentials, incident recovery, and changes. ERP publisher support for the standard product should not be assumed to include custom integrations.
As an Amazon Associate I earn from qualifying purchases.
Why the builder may not be the maintainer
Implementation work can end at handover. Ongoing support needs a separate, explicit assignment—internally or through a continuing contract. For Dynamics 365, Microsoft describes a shared-responsibility model: Microsoft is responsible for its standard infrastructure and platform, while customers and implementation partners manage business processes and test changes before deployment. That guidance illustrates one platform’s division of duties, not a rule for every ERP product. Microsoft’s shared-responsibility guidance and your own contracts define the applicable boundary.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIntegration support also spans technical and business responsibilities. Technical staff monitor and troubleshoot the connection, manage security and service operations, and restore processing. A business process owner or data steward confirms that the transaction, data meaning, and business rules are correct.
Choose an owner for each responsibility
One team may cover several rows, but name a person or queue for each duty. Otherwise an incident can sit between the ERP vendor, implementation partner, internal IT, and connected-system provider.
| Responsibility | Typical owner | What to define |
|---|---|---|
| Business process and data meaning | Process owner or data steward | Expected behavior, authoritative data, validation, and approval of business-rule changes. |
| Integration technical operation | Internal IT, ERP team, or contracted partner | Monitoring, incident triage, credentials, security, performance, troubleshooting, restart and recovery, deployment, and tests. |
| ERP standard product and service | ERP publisher under the relevant support agreement | Which product defects, platform services, updates, and support channels are covered. |
| Custom code, connectors, and partner solutions | Internal technical team or contracted partner | Maintenance scope, compatible updates, regression testing, release, and deployment responsibility. |
| Integration estate and architecture | Named architecture or ERP owner | Inventory, dependencies, ownership changes, and decisions to replace or retire connections. |
| User-facing support and escalation | Help desk or first-line team, then technical owner | Ticket intake, severity, required incident information, response coverage, and escalation path. |
For Dynamics 365, Microsoft’s support strategy guidance describes support levels and calls for a support and maintenance agreement for escalation. Other ERP publishers may structure support differently, so check the applicable agreement.
Rank #2
Decide which support model fits
Internal, external, and hybrid arrangements can all work. Choose based on in-house skills and coverage, integration complexity and customization, planned upgrades, and the actual contract scope.
Free tools Windows power users keep installed
One-click scans. No signup required.
Internal ERP or IT team
This can suit an organization with the platform and integration skills, operational coverage, and authority to manage changes. The team still needs a defined route to the ERP publisher for standard-product issues.
Original implementation partner
The original partner may already understand the configuration, but building the connection does not establish continuing responsibility. Confirm that the agreement covers the specific integrations, response terms, exclusions, access, and support hours.
Replacement partner or AMS provider
A new partner or application management services provider can take on custom integration troubleshooting and maintenance when the original engagement ends or internal expertise is insufficient. Before transferring responsibility, agree on onboarding and knowledge transfer, platform expertise, service hours, escalation, change control, and ownership of code and credentials.
Hybrid support
Internal staff can handle business decisions and first-line triage while an external team takes complex platform or integration work. Make the handoff explicit: identify who owns the incident until the business flow is restored, rather than leaving coordination implicit.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do not treat vendor maintenance and AMS as interchangeable. ERP Research distinguishes standard-product maintenance from support for customer customizations and integrations; confirm the exact coverage with the relevant ERP vendor and support provider: ERP Research’s overview of ERP support and maintenance.
Route an incident to the right owner
First establish what failed and whether the transaction is incorrect, delayed, duplicated, or missing. Separate business-process questions from technical failures before assigning work.
- User or process question, or data-quality issue: involve the help desk and the business process owner or data steward to confirm the intended transaction, source data, and business rules.
- Standard ERP product defect or platform-service issue: use the support channel and coverage in the ERP publisher’s agreement.
- ERP configuration issue: route it to the named ERP configuration owner; involve the business owner if a process rule or expected outcome is in question.
- Custom code, connector, or middleware failure: send it to the named technical integration owner, who coordinates with the connector or connected-system provider as needed.
- Authentication, infrastructure, or third-party service outage: route it to the owner of that service or environment while the integration owner coordinates the end-to-end recovery.
This is a practical triage approach, not a guarantee of who is contractually obligated to respond. Actual coverage depends on the systems and agreements in place.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Make handover operational before the partner exits
Acceptance documents alone may not equip a receiving team to run or recover an integration. Microsoft’s go-live support transition guidance calls for a transition plan and the resources, tools, access, and training needed to operate. Its integration support guidance identifies areas such as data management at both ends, security, performance, monitoring or auditing, and troubleshooting. Use the following handover checklist to turn those operational needs into verifiable deliverables:
Recommended Free Tools
- Inventory: list each integration, its endpoints, connected systems, environments, dependencies, business criticality, and business and technical owners.
- Behavior and data: document field mappings, triggers, expected outputs, business rules, known exceptions, and how to identify an incorrect transaction.
- Access and credentials: identify who owns service accounts and credentials, how renewals or expiry are handled, who can grant access, and who is responsible for security.
- Monitoring and incidents: provide dashboards, failure alerts, logs, incident history, and the person or queue that receives each alert.
- Recovery: write down retry, replay, rollback, reconciliation, and manual recovery procedures, including steps for a transaction that completed only partially.
- Code and deployment: transfer applicable source code or configuration access, the deployment process, change history, and a list of partner or third-party dependencies.
- Verification: provide test cases and a repeatable check after changes, including regression tests relevant to ERP or connected-system updates.
- Support arrangements: name business and technical owners; set out support hours, severity definitions, escalation contacts, ticket process, and applicable contracts.
- Knowledge transfer: train the receiving team and arrange a knowledge-transfer or overlap period before the outgoing partner disengages.
The checklist is an operational guide, not a universal contractual standard. Agree which items apply to each integration and verify that the receiving team can access and use them.
Questions to settle with both providers
Ask the current partner and any prospective maintainer to answer these questions in writing, then reconcile the answers with the contracts:
Quick Recap
- Which integrations and custom components are explicitly in your support scope, and which are excluded?
- Who receives and investigates alerts, and who owns the incident until the business flow is restored?
- Who controls service accounts, API credentials, renewals, and access when staff or providers change?
- Who approves business-rule changes, and who performs code or connector changes?
- What testing and deployment steps are required after ERP, middleware, or connected-system updates?
- What support hours, severity levels, response commitments, and escalation routes apply?
- What documentation, code, configuration, logs, and test evidence will be delivered at handover?
- How will the receiving team learn to operate and recover the integrations?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
