Prepare a field map
For each site field, specify the CRM field, type, required status and conversion rule. Separately describe the source, funnel, status and person responsible. Check directory IDs in a specific account; values from another project may mean completely different entities.
Continue with: UTM in CRM: preserve the source of an enquiry.
Define the behavior of complex data
Check multiple phones, empty email, long comment, items with options and different currencies. Store the external enquiry ID for retrieval and control of duplicates. API keys of different operations may have different rights, and limits may differ by method; they should be checked in the current documentation.
Continue with: CRM duplicates: repeated delivery or a new enquiry?.
Verify the result in CRM
Create test enquiries of various types and compare the result with the original data. Check authorization error, missing required field and resubmit. A failed enquiry should go to the controlled list of errors. Agree who monitors this list and resumes the exchange after changing the fields.
Continue with: Meta leads to CRM: fields, permissions and delivery.
Is it possible to convey everything in one text comment?
You can save additional context, but it is better to map core data to dedicated fields. Otherwise, filters, automations, and reports will work to a limited extent.