# Make website leads usable inside the CRM > Plan CRM field mapping for website leads: what the record contains, where each field goes, how duplicates are handled, and who owns the next action. Source: https://scayverstaging.1wp.site/resources/site-operations/crm-field-mapping/ ![Three people wearing headsets sit at computers in a bright office space.](https://scayverstaging.1wp.site/wp-content/uploads/2026/09/sg-resources-146856-hero.webp) CRM field mapping lets a teammate opening the record see why someone contacted you through the website, where the inquiry came from, and who should respond. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) [Every resource](https://scayverstaging.1wp.site/resources/) **Format** [Guide](https://scayverstaging.1wp.site/resources/type/guide/) **In this format** 92 ## What should a complete lead record answer? Sending a form submission to a CRM is not the same as giving a sales or service team a usable lead. Begin with the record a teammate needs to open, not the field names a connector happens to offer. Ask what a responder needs in the first minute. Usually that includes the person’s name, reply route, service interest, short request, source page, and submission time. Some businesses also need location or preferred contact method. Do not add a field merely because the CRM has one. Each question increases form work and introduces another value that needs governance. Decide whether the website creates a contact, a company, a deal, a ticket, or several related records. A simple inquiry may need only a contact and task. A quote request may need a deal with product or project details. These choices affect reporting and duplicate handling. The same email address can submit a new request without being a new person. ## How should CRM field mapping move data between systems? Write a field map with website label, data type, CRM field, required status, and transformation rule. If “Which service do you need?” offers a small list, map each option to a valid CRM value. Preserve a visitor’s free-text message as a note or inquiry description rather than forcing it into a short title field. Record consent separately from marketing interest. A customer can request a callback without asking for promotional email. The organization must define the lawful and approved data-handling process. Technically, the CRM should keep enough context for staff to respect that choice. ## What happens with duplicates and errors? Test a repeat inquiry, a blank optional field, a long message, and an invalid value. Decide whether a repeat request updates an existing contact, adds a new deal, or creates a separate support item. Prevent a form retry from creating several identical deals when the first response was merely slow. Define the failure path. If the CRM rejects the submission, where can staff find the original request? Who receives the alert? The visitor’s confirmation should reflect what actually happened. A connection can fail while the website itself stays online, so test this state explicitly. ## Who owns the resulting work? Add assignment rules and a response owner. A record with rich fields still fails if it lands in an unmonitored list. Decide how staff mark the inquiry handled and how that status feeds reporting. Record the account administrator and where integration documentation lives without storing credentials in the content brief. Review the map whenever the form, service categories, or CRM pipeline changes. A new option on the website can silently arrive as an unknown value if nobody updates the destination. A small field map is easier to maintain than an undocumented automation chain. ## What should you bring to a scoping conversation? Bring one completed sample form, a screenshot or export of the desired CRM record, and your current assignment process. Ask the developer to walk through normal, duplicate, and failed submissions. See [CRM integration](https://scayverstaging.1wp.site/services/development/crm-integration/) for the service path. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/) to connect a website inquiry to a clear team action. [Explore the site-operations guides](https://scayverstaging.1wp.site/resources/site-operations/). Guides ## Guides beside Make website leads usable inside the CRM. 1. ### [Define the website before you price the build](https://scayverstaging.1wp.site/resources/site-operations/website-requirements-checklist/) Site operations · 4 min read 2. ### [Choose a CMS around the work your team does](https://scayverstaging.1wp.site/resources/site-operations/choosing-a-cms/) Site operations · 3 min read 3. ### [Use the smallest build that solves the real problem](https://scayverstaging.1wp.site/resources/site-operations/plugin-vs-custom-development/) 4. ### [Map the handoff between tools before you automate it](https://scayverstaging.1wp.site/resources/site-operations/integration-data-map/) 5. ### [Check the dependency before it becomes invisible](https://scayverstaging.1wp.site/resources/site-operations/api-vendor-due-diligence/) 6. ### [Plan checkout as a business process, not a button](https://scayverstaging.1wp.site/resources/site-operations/checkout-flow-planning/) 7. ### [Give the product catalog a structure that can grow](https://scayverstaging.1wp.site/resources/site-operations/ecommerce-catalog-structure/) 8. ### [Decide the order rules before you configure checkout](https://scayverstaging.1wp.site/resources/site-operations/shipping-and-tax-workflow/) 9. ### [Make the return path clear before someone needs it](https://scayverstaging.1wp.site/resources/site-operations/returns-content-structure/) 10. ### [Define access rules before the member dashboard](https://scayverstaging.1wp.site/resources/site-operations/membership-access-model/) 11. ### [Design the learning workflow before choosing the LMS](https://scayverstaging.1wp.site/resources/site-operations/lms-delivery-requirements/) 12. ### [Ask for what the appointment actually needs](https://scayverstaging.1wp.site/resources/site-operations/appointment-booking-fields/) 13. ### [Stop form spam without punishing real visitors](https://scayverstaging.1wp.site/resources/site-operations/form-spam-and-privacy/) 14. ### [Every automation needs an owner when it stops](https://scayverstaging.1wp.site/resources/site-operations/automation-failure-handling/) 15. ### [Give the chatbot a smaller, trustworthy job](https://scayverstaging.1wp.site/resources/site-operations/ai-chatbot-knowledge-boundaries/) 16. ### [The handoff is part of the answer](https://scayverstaging.1wp.site/resources/site-operations/ai-human-handoff/) 17. ### [Name the action before you tag the button](https://scayverstaging.1wp.site/resources/site-operations/analytics-event-naming/) 18. ### [Test the conversion, not just the dashboard](https://scayverstaging.1wp.site/resources/site-operations/conversion-event-validation/) 19. ### [Make measurement follow the choice a visitor makes](https://scayverstaging.1wp.site/resources/site-operations/consent-and-analytics-planning/) 20. ### [Spend page weight on things visitors can use](https://scayverstaging.1wp.site/resources/site-operations/website-performance-budget/) 21. ### [Accessibility continues every time someone publishes](https://scayverstaging.1wp.site/resources/site-operations/accessibility-content-operations/) 22. ### [Test the backup before you need it](https://scayverstaging.1wp.site/resources/site-operations/backup-restore-drill/) 23. ### [Update the plugin, then prove the journey still works](https://scayverstaging.1wp.site/resources/site-operations/plugin-update-staging/) 24. ### [An alert needs a person and a next action](https://scayverstaging.1wp.site/resources/site-operations/monitoring-ownership/) 25. ### [Know what ongoing website care actually covers](https://scayverstaging.1wp.site/resources/site-operations/website-care-scope/) 26. ### [Keep the domain and its connected services in view](https://scayverstaging.1wp.site/resources/site-operations/domain-dns-transfer/) 27. ### [Decide what to carry before you rebuild](https://scayverstaging.1wp.site/resources/site-operations/content-migration-inventory/) 28. ### [Give each old link a sensible destination](https://scayverstaging.1wp.site/resources/site-operations/redirect-mapping/) 29. ### [Decide how to reverse a bad launch before launch day](https://scayverstaging.1wp.site/resources/site-operations/website-launch-rollback/) No other guides in this group yet. Keep reading ## Read after Make website leads usable inside the CRM. The rest of the resources, newest first. - [2 July 2026 Customer Persona Worksheet](https://scayverstaging.1wp.site/resources/customer-persona-worksheet/) - [2 July 2026 The Social Content Sprint Playbook](https://scayverstaging.1wp.site/resources/the-social-content-sprint-playbook/) - [2 July 2026 AI Prompt Pack for Blog Post Outlines](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-blog-post-outlines/) - [2 July 2026 Email Welcome Sequence Template](https://scayverstaging.1wp.site/resources/email-welcome-sequence-template/) - [2 July 2026 Website Pre Handoff QA Checklist](https://scayverstaging.1wp.site/resources/website-pre-handoff-qa-checklist/) - [2 July 2026 The SEO Content Audit Guide](https://scayverstaging.1wp.site/resources/the-seo-content-audit-guide/) - [2 July 2026 Positioning Statement Worksheet](https://scayverstaging.1wp.site/resources/positioning-statement-worksheet/) - [2 July 2026 The Client Onboarding Playbook](https://scayverstaging.1wp.site/resources/the-client-onboarding-playbook/) - [2 July 2026 AI Prompt Pack for Ad Headline Variations](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-ad-headline-variations/) - [2 July 2026 The One Page Creative Brief Template](https://scayverstaging.1wp.site/resources/the-one-page-creative-brief-template/) - [2 July 2026 Brand Launch Readiness Checklist](https://scayverstaging.1wp.site/resources/brand-launch-readiness-checklist/) - [2 July 2026 The Landing Page Teardown Guide](https://scayverstaging.1wp.site/resources/the-landing-page-teardown-guide/)