--- title: "What should move from CRM to ERP when a deal is won? | R&D COPILOT" lang: en canonical: https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/ content_version: 71525ed7e4c575af68decdc2a81ea51c96c775b6d771fecfce6ca49b0685700f contact: https://rdcopilot.com/contact/ --- [RDC](https://rdcopilot.com/) [Insights](https://rdcopilot.com/insights/)CRM CRMDecision guide # What should move from CRM to ERP when a deal is won? Winning an opportunity should create an actionable operational handoff, with the commercial agreement preserved and the receiving team able to accept it. A CRM stage change alone does not tell an ERP what to deliver. The integration needs a shared definition of the customer, the agreed scope and the conditions that make the order ready for fulfilment. By R&D COPILOT6 October 20265 min read In this guide 1. [Define what won authorises the business to do](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-1) 2. [Resolve customer identity before creating the order](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-2) 3. [Translate the offer into operational lines](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-3) 4. [Give operations an acceptance and rejection path](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-4) 5. [Decide how changes flow after acceptance](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-5) 6. [Scope the connection as a maintained service](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-section-6) [Sources & inspiration](https://rdcopilot.com/insights/crm-erp-won-opportunity-handoff/#guide-sources) ## Define what won authorises the business to do Ask sales and operations to describe the point at which a deal can enter the delivery process. An accepted proposal may still depend on a purchase order, a final delivery address or an agreed start date. Decide which conditions are necessary for the handoff and which can remain open under a named owner. This makes the meaning of won clear without forcing every commercial detail into one field. Keep the buyer’s agreement linked to the opportunity. Record the accepted proposal version and the date of acceptance, together with any relevant conditions. If sales changes the scope afterwards, that should become a visible amendment requiring the agreed review. The integration should not quietly overwrite an operational order just because someone updated a note in the CRM. ## Resolve customer identity before creating the order The organisation shown on an opportunity may be a trading name, a group company or a contact acting for another legal entity. Operations and finance need the correct customer record for the transaction. Agree which identifiers connect CRM accounts to ERP customers, and when the receiving team must confirm a new customer before the order can proceed. Keep billing, delivery and contact information distinct. A familiar account can still place an order for a new location or a different purchasing entity. Where existing records disagree, show the difference to an authorised reviewer rather than always trusting the most recently edited field. Store the mapping once it is accepted so later orders can reuse it, while preserving a controlled way to update changed business details. ## Translate the offer into operational lines A proposal may describe an outcome, while the ERP needs item or service lines with quantities, units and delivery conditions. Document the translation with the people who prepare and fulfil orders. For recurring services, staged projects or bundled offers, decide whether one commercial line becomes several operational lines and how the relationship remains visible. Commercial amounts and conditions must pass through the approved finance process. The connector should carry agreed values, not invent missing prices, tax treatment or payment terms. Include references that let a reviewer compare the order with the accepted proposal. A compact handoff contract makes those responsibilities clear and gives the implementation team a stable basis for building and testing the connection. - Identify the accepted proposal and its version. - Map the purchasing entity to the approved ERP customer. - Describe each deliverable with quantity, unit and agreed scope. - Preserve delivery locations, dependencies and requested dates. - Include the commercial fields approved for transfer by finance. - Assign an owner to every missing prerequisite or disputed value. ## Give operations an acceptance and rejection path The first destination should be a state the receiving team understands. Depending on the process, that may be a draft order awaiting review or an accepted order with all prerequisites satisfied. Make the distinction explicit. Sales needs to know whether the handoff was delivered technically, accepted operationally or returned for correction. A rejection should identify the field or condition that requires attention and name the person expected to resolve it. Keep the correction on the same handoff record. Avoid creating a second opportunity merely because the first transfer failed. When a network interruption makes the result uncertain, check the existing reference in the ERP before sending another create request. Technical recovery should preserve the business identity of the agreement. ## Decide how changes flow after acceptance Once operations accepts the order, define which system owns each kind of change. Sales may own negotiation of an amended scope, the warehouse may own actual dispatch information and finance may own its document status. A connector that permits both systems to overwrite all fields creates conflicts that are difficult for users to understand. Use a change request for amendments that affect committed work. Show the previous and proposed values, the reason and the operational effect before approval. If a delivery has already begun, a cancellation requires a different path from an untouched draft. Test these cases with the team and keep status feedback flowing to CRM so the salesperson can answer the customer without pretending that a CRM stage is the complete operational truth. ## Scope the connection as a maintained service Review the actual integration capabilities, licence requirements and version constraints of both applications. Confirm who administers credentials, monitors failed handoffs and approves mapping changes. For EU-hosted or company-managed deployment, map any additional queues, logs and document storage used between CRM and ERP, and restrict them to the data needed for the transfer. Rehearse a known customer, a new purchasing entity, a bundled proposal, a rejected handoff and an amendment after acceptance. Measure accepted handoffs, missing prerequisites, duplicate prevention and time spent resolving returned orders. Keep the definitions stable before comparing periods. RDC can work with sales, operations and finance to define the handoff contract, implement the connection and make exceptions visible. Bring an accepted proposal and the operational order it should produce; that comparison is more useful than starting with a list of API endpoints. Inside the product ## CRM [![Opportunity board with relationship details and activity history.](https://crm.rdcopilot.com/product-demos/crm/gallery-overview-en.png)View full size](https://crm.rdcopilot.com/product-demos/crm/gallery-overview-en.png) Opportunity board with relationship details and activity history. [![Forma Supply relationship selected with its proposal and activity history.](https://crm.rdcopilot.com/product-demos/crm/gallery-detail-en.png)View full size](https://crm.rdcopilot.com/product-demos/crm/gallery-detail-en.png) Forma Supply relationship selected with its proposal and activity history. Swipe or use the arrows to explore. Image 1 of 2 Follow the references ## Sources & inspiration ### [AI Powered Auto CRM](https://devpost.com/software/ai-powered-auto-crm) Devpost project by Alejandro Capellán Independent inspiration for workflow design. This independently created project is credited as inspiration. The workflow and implementation guidance in this article are RDC’s analysis. - [Stripe: idempotent requests](https://docs.stripe.com/api/idempotent_requests) Put the guide to work ## Start with your workflow. Tell us what your team needs to do, which systems are involved and where the current process slows down. [Discuss your project](https://rdcopilot.com/contact/?product=crm) [Explore CRM](https://crm.rdcopilot.com/en/products/crm/) CRM ## Keep exploring. [All guides](https://rdcopilot.com/insights/) Workflow ### [A CRM follow-up process for a small sales team](https://rdcopilot.com/insights/crm-follow-up-process-small-team/) Build a CRM follow-up process around buyer decisions, clear next actions and reliable handovers, with reviewable reminders that fit the way a small sales team works. [Read guide](https://rdcopilot.com/insights/crm-follow-up-process-small-team/) How-to guide ### [Stop website enquiries getting lost before sales follows up](https://rdcopilot.com/insights/crm-website-lead-handoff/) Connect website enquiries to CRM ownership, contact matching and a visible next action, with dependable acceptance records and a practical delivery exception queue. [Read guide](https://rdcopilot.com/insights/crm-website-lead-handoff/)