Migrate from Agworld to Odoo CRM

Agworld farms map to Odoo res.partner records with type='company'. Farm name becomes partner name, farm address maps to partner address fields, and farm size is stored as a custom float field x_farm_size_acres. Multi-farm operations map each farm to a separate partner record with parent_id set if hierarchy exists in Agworld.

Agworld fields map to address records under the farm partner, storing crop type, acreage, planting date, and season-year as custom fields. Field boundary geometry (GPS coordinates) is exported as GeoJSON attachments since Odoo has no native GIS storage. Each field gets a unique identifier preserved in x_agworld_field_id for traceability.

Agworld growers and operators map 1:1 to Odoo res.partner records with type='contact'. Name, email, phone, and address fields migrate directly. Multiple growers per farm are represented as child contacts under the farm partner record, matching Agworld's N:1 farm-to-grower relationship, with the original Agworld grower ID preserved in x_agworld_grower_id for audit trail and de-duplication purposes.

Agworld agronomist accounts map to res.partner records linked to res.users records in Odoo so they can log activities. If the agronomist does not need Odoo login access, they are stored as partners only. Contact details (name, email, phone) map directly; expertise notes become a custom text field.

Agworld jobs (spraying, planting, harvesting, soil sampling) map to Odoo mail.activity records linked to the corresponding crm.lead or res.partner. Activity type, date, notes, and product used are preserved as activity fields. The original Agworld job ID is stored in x_agworld_job_id for delta-run de-duplication.

Agworld agronomist recommendations migrate as notes on the associated crm.lead, with the recommendation text, product suggested, and application rate stored in custom fields x_recommendation_text, x_recommended_product, and x_application_rate. Recommendation status (pending, accepted, applied) maps to a custom pick-list field for tracking the lifecycle of each agronomist suggestion within the Odoo pipeline.

Agworld spray records, chemical applications, and harvest compliance data require a custom compliance record model in Odoo. Fields include: record date, field_id (FK to res.partner), chemical product, rate applied, pre-harvest interval, and operator. This model links to the field record and creates an audit trail for regulatory compliance.

Agworld product catalog entries (fertilizers, chemicals, seed) map to Odoo product.product records. Product name, SKU, unit of measure, and category map directly. Pricing and vendor information may require supplementary mapping depending on Agworld's product data depth and whether you need to preserve historical pricing or supplier relationships in Odoo.

Soil sample results attach to the field partner record via custom fields: x_soil_ph, x_soil_nitrogen, x_soil_phosphorus, x_soil_potassium, x_sample_date, and x_lab_name. Historical samples are preserved as a one2many relation on the field partner if multiple samples per field exist, allowing year-over-year soil health tracking in Odoo.

Agworld season-level planning data (crop planned, planting date, expected yield, budget) maps to custom fields on crm.lead: x_season_year, x_planned_crop, x_planting_date, x_expected_yield, and x_season_budget. Each field's current-season lead carries this planning context alongside its compliance history, enabling seasonal forecasting within the CRM pipeline.

Agworld file attachments (PDFs, images, shapefiles) are re-uploaded to Odoo ir.attachment records linked to the corresponding record (field, job, compliance record). File size limits apply; Odoo default is 25MB per file. Inline images in notes are downloaded and rehosted as attachments.

Agworld owner IDs are resolved against Odoo res.users by email match. Unmatched owners are flagged before migration; your team either creates their Odoo user first or assigns records to a fallback owner. No record lands in Odoo without a valid user_id reference.