How will perennial crops assessed as "other crop" in CFT be migrated?

How will perennial crops assessed as "other crop" in CFT be migrated?

Perennial crops in CFT that do not have a corresponding perennial typology in CFP, or crops for which the typology is unknown - e.g. if assessed as "tree crops" in CFT - will not be migrated as perennials. Instead, they will be migrated into the CFP annuals pathway and mapped to the crop type “other annual crop”. This includes:

  1. Raspberry
  2. Blueberry
  3. “Tree crops” - either no specific CFP perennial typology exists, or the typology is unknown and therefore cannot be transferred as perennials. This may include cocoa, citrus fruits, almond or oil palm.

This approach was chosen because in most cases, there is currently no suitable perennial typology for these crops in CFP, and creating temporary or generic perennial options would require significant extra methods and development work and could introduce misleading or “made‑up” default values. For "tree crops", a matching typology may exist in CFP, but there is too much risk to assume this match and assign assessments to existing typologies without concrete proof. Therefore, all tree crops will be migrated to the annual pathway (e.g. "tree crop" assessments with names such as "mandarine" or "almond").


As a result, users will see above perennials assessments as “other annual crop” in CFP. Assessments will still run, but residue and pesticide results may be more conservative and may differ from CFT, reflecting the generic “other annual” treatment rather than a specific perennial model.

New assessments for these crops can be created in CFP in the available pathways - either as "other crops" in annuals (raspberry, blueberry) or as perennial if the applicable typology exists. Also see this article for a perennials typology not listed in CFP.

Other related article: How will perennials with a matching typology in cfp be migrated