The error "Odoo Server Error Invalid field name 'in_group_21'" when importing contacts typically occurs because the import file references a field or group that does not exist in the Odoo database, or the mapping between your data and Odoo's fields is incorrect. This could also be due to mismatched field names or metadata from QuickBooks that doesn't align with Odoo.

Here’s how you can troubleshoot and resolve the issue:

1. Understand the Error

• in_group_21: This indicates a field that likely corresponds to a group or permissions in Odoo but does not exist or is not properly mapped in your Odoo instance.
• The issue may arise due to:
  • Metadata exported from QuickBooks being included in your import file.
  • Incorrect mapping of fields during import.
  • Trying to import a group or permission that doesn't exist in your Odoo configuration.

2. Steps to Resolve the Issue

A. Check Your Import File

1. Review Column Headers:
   • Open your import file (CSV or Excel).
   • Look for a column named in_group_21 or similar.
   • Remove or rename any fields that are not part of the standard Odoo fields for the res.partner model (Contacts).
2. Clean Metadata from QuickBooks:
   • QuickBooks might include additional metadata during export (e.g., permissions or settings). Review and remove unnecessary columns that are irrelevant to Odoo.
3. Match Field Names with Odoo:
   • Navigate to Contacts > Configuration > Import Contacts.
   • Download the sample import file from Odoo for reference.
   • Compare your file's columns with the sample file to ensure the field names match Odoo's requirements.

B. Check Field Mapping in Odoo

1. Preview the Import:
   • Go to Contacts > Import and upload your file.
   • Odoo will display a preview of the import data and allow you to map fields.
   • Check if in_group_21 appears in the preview. If it does:
     • Map it to a valid Odoo field, or leave it unmapped.
2. Validate Fields:
   • Ensure each column in your import file maps to an existing field in the res.partner model.
   • Remove any unnecessary columns from the import file.

C. Debug the Error

If the issue persists, use the following steps to debug:

1. Enable Developer Mode:
   • Go to Settings > Activate Developer Mode.
2. Inspect the in_group_21 Field:
   • Navigate to Settings > Technical > Database Structure > Fields.
   • Search for in_group_21. If the field doesn’t exist, it confirms that the field is invalid.
3. Inspect Your Model:
   • Check the res.partner model for any custom fields added by third-party modules.
   • If a custom module added this field and it’s no longer available, remove references to it in your import file.

D. Test a Minimal Import

1. Prepare a Small Test File:
   • Create a simplified import file with just the essential fields (e.g., Name, Email, Phone, Address).
   • Example:

     Name,Email,Phone,Street,City,Country
     John Doe,john@example.com,123456789,123 Street,New York,USA
     

2. Import the Test File:
   • If this file imports successfully, gradually add columns from your original file to identify the problematic field.

E. Look for Customizations or Permissions Issues

1. Check User Permissions:
   • If the in_group_21 field references a user group, verify that the user performing the import has the necessary permissions.
   • Navigate to Settings > Users & Companies > Users and check the access rights for the user.
2. Review Installed Modules:
   • If you have custom modules installed, they may have added or removed fields incorrectly. Disable the modules temporarily and retry the import.

3. Common Issues and Fixes

4. Final Validation

1. Import Validation:
   • After resolving the issue, run the import with a test file and verify the results.
   • Check that all data is correctly imported and appears in the Contacts module.
2. Check Logs:
   • If the error persists, check the server logs for detailed error messages:
     • Navigate to Settings > Technical > Logs > Server Logs.

Let me know if you need further assistance, and I can guide you through debugging the issue!