Hi, sorry for a bit a late reply, both nomenclatures are very different, flow names and also compartments, EF is on purpose like a silo, not meant to be used with other databases. A mapping is possible to some extent, the inventory modeling (system boundaries, previous / next life cycle) are not fitting, you cannot change EF as these are all aggregated system processes, so even with mapped flows you can either leave two not-fitting inventory models in one LCA or you can try to adjust ecoinvent to EF since you cannot modify the system process modeling. We can also support this if you like but it is not too easy (as you may guess already). Just let me know.
Thank you and best wishes,
- addition: same of course for the upcoming EF 3