How to migrate to openLCA from other tools

Many users come to openLCA with existing models developed in other LCA software or data stored in different formats. openLCA supports most common LCA data exchange formats, including JSON-LD, SimaPro CSV, EcoSpold1, ILCD, as well as Excel, allowing users to migrate existing work without rebuilding their models from scratch. Technical details of the supported import formats are provided in the official openLCA manual chapter Importing data and combining databases. This chapter focuses on selecting an appropriate migration strategy based on the intended use of the project and identifying the checks needed to ensure reliable results after migration.

The following general principles apply:

  • Determine whether the project is old/archived, ongoing, or new.
  • Decide whether to migrate the complete model, including background databases, or only the foreground model (then connecting to a background database on openLCA).
  • Use mapping files where necessary to align elementary flows with the reference flow system of the target database in openLCA.
  • Validate the migrated database and check LCIA coverage after a calculation.
  • Compare selected results with those obtained in the source software.

Note: If you already have an active license for the official database you are using, you can transform it for a fee to the openLCA version; see openLCA Nexus.

The individual import formats and their technical details should be handled according to the corresponding openLCA database import documentation. openLCA supports most common LCA data exchange formats and provides extensive functionality for importing, exporting, and working with LCA models. Its advanced, freely available development and scripting capabilities also make it possible to implement additional import/export formats and reproduce specialised workflows from other software.

Migrating from SimaPro to openLCA

Choosing a migration path

Before migrating a project, classify it according to how it will be used in the future.

flowchart TD
    A{"How will the project be used?"}

    A -->|New project| B["Start directly in openLCA"]
    A -->|Archive / reference| C["Import the complete SimaPro model"]
    A -->|Continue developing| D{"Target database structure"}

    D -->|Option 1: Retain SimaPro database structure| C
    D -->|Option 2: Adapt to openLCA database structure| E["Import the foreground model and link to the openLCA ecoinvent database"]

    C --> F{"Which LCIA methods will be used?"}

    F -->|SimaPro methods| H["No mapping file required (no mapping required to re-migrate to SimaPro)"]

    E --> I["Map foreground elementary flows to the openLCA ecoinvent reference system"]

New projects

For new projects, start directly in openLCA and use an appropriate database from openLCA Nexus openLCA Nexus; if you already have an active license for the database you are using, you can transform to the openLCA version; see openLCA Nexus.

Principle: New modelling should be done in openLCA rather than starting a new project in another software and subsequently migrating it.

Old/archived projects

Use case: Projects that should be retained for reference only.

Recommended approach: Import the complete model, including its background databases/libraries, as-is. This preserves the original model structure, elementary-flow reference system, and existing LCIA methods. It can also be the fastest approach when a project uses several background databases besides ecoinvent.

Note: The database might not be compatible with other databases in openLCA but is usable as a standalone database_

Ongoing projects

For projects that will continue to be developed, there are two possible approaches:

  • Option 1: Import the complete model, including its libraries/background databases.
  • Option 2: Import only the foreground model and connect it to the corresponding openLCA background database.

For models based on ecoinvent, as this is the most commonly migrated database, moving the foreground model is the preferred workflow when the intention is to use the openLCA version of ecoinvent and the openLCA LCIA methods.

See below Import the complete SimaPro model with a SimaPro CSV import and Import the foreground model and link it to openLCA ecoinvent.

Option 1: Retain the SimaPro database structure

Export the SimaPro project together with its libraries/background databases, such as ecoinvent or other databases, and import the datasets into a new empty database created from scratch in openLCA.

When to use this option?

  • the project is old/archive and only needs to be retained for reference
  • the SimaPro model structure needs to be preserved
  • several background databases are used
  • the existing SimaPro elementary-flow reference system and LCIA methods need to remain available

What is preserved?

  • the SimaPro model structure
  • parameters and other general features from SimaPro
  • the SimaPro elementary-flow reference system
  • the LCIA methods from SimaPro
  • the limitations of the SimaPro database structure, including lack of data quality

Mapping files

  • A mapping file is not required if the imported model will use only the SimaPro databases and LCIA methods.
  • If openLCA Nexus LCIA methods are to be used, a mapping file is required to map SimaPro elementary flows to the corresponding openLCA reference flows. See Using mapping files in openLCA.

Importing multiple CSV files

If several SimaPro CSV files are imported without a mapping file, import them together in one step so that flows shared between the files can be matched consistently. See SimaPro CSV import.

Export only the user's own project from SimaPro, without its libraries, and connect the foreground model to the corresponding ecoinvent database in openLCA.

When to use this option?

  • to use the openLCA version of ecoinvent
  • to use the corresponding ecoinvent LCIA methods
  • to allow the migrated model to use openLCA functionality and database structures.

For ecoinvent-based models, this is the recommended workflow for ongoing modelling. Other databases can also be migrated in a similar manner with support from GreenDelta.

What is preserved?

  • the foreground SimaPro model and asscociated parameters and other general features

Step 1: Export the foreground model from SimaPro

  1. Open the project you want to migrate in SimaPro.
  2. Export the project in SimaPro CSV format.
  3. Select only the project (foreground) data for export. Do not include the SimaPro libraries or background databases.
  4. Save the exported CSV file for import into openLCA.

Step 2: Prepare the openLCA database

Before importing the foreground model, you need to prepare a compatible background database in openLCA.

  1. Go to openLCA Nexus and select the ecoinvent database that corresponds to the one used in SimaPro.
  2. Make sure that the ecoinvent version, system model, and process type match those used in the original SimaPro project. For example, ecoinvent 3.12, cut-off system model, unit processes.
  3. Download the database and make it available in openLCA using one of the following options:
  4. Open the prepared database in openLCA before proceeding with the SimaPro CSV import.

In openLCA:

  1. Activate the target ecoinvent database.
  2. Go to File → Import → Other → SimaPro CSV.
  3. Select the exported SimaPro CSV file.
  4. Enable Link ecoinvent processes (experimental).
  5. Click Finish.

During import, openLCA identifies the ecoinvent processes used by the foreground model from their names.

Note: No copies of the ecoinvent processes or flows are created when the link is successful; only the foreground model is added to the database.

Parameters

Parameters are migrated as follows. See the openLCA manual chapter on Parameters for details.

SimaProopenLCA
Process parametersProcess parameters
Project parametersGlobal parameters

Experimental feature

The Link ecoinvent processes option is experimental and is being actively improved. In larger models, some naming patterns may not yet be recognized. In such cases, openLCA may create a copy of an ecoinvent process instead of creating a link. Affected processes should be documented and reported so that the linking feature can be improved.

LCIA methods

When the foreground model is linked to the openLCA ecoinvent database, the model uses the LCIA methods supplied with that ecoinvent database directly. See LCIA methods and categories. Therefore:

  • SimaPro LCIA methods do not need to be imported;
  • the ecoinvent/openLCA LCIA methods can be used directly.

Checking result differences

Results may differ slightly from SimaPro. A useful check is to compare the results of selected background processes with the official ecoinvent LCIA results. If the background results agree, this provides evidence that the corresponding methods are suitable for assessing the migrated foreground model.

Elementary flows in the foreground model

Elementary flows added directly to foreground processes, such as direct emissions, are imported as SimaPro flows. These flows are not part of the openLCA reference system and therefore may not be characterized by the openLCA/eecoinvent LCIA methods.

Ways to resolve the issue

Option A — Use a mapping file

Use a mapping file during import to map SimaPro elementary flows to openLCA reference flows. See Using mapping files in openLCA. Another mapping file is to be used when exporting the database back to SimaPro.

Option B — Bulk-replace the flows

If only a small number of elementary flows are affected, use Tools → Bulk-replace to replace the imported SimaPro flows with their openLCA counterparts.

Option C — Add characterization factors

Alternatively, add the relevant flows to the LCIA methods by adding characterization factors for them to the appropriate impact categories. See Creating a new impact assessment method, category and characterization factor.

Default providers

When the foreground model is connected to ecoinvent manually, without the Link ecoinvent processes option, product inputs may not have a default provider. A Jython script can be used in the openLCA Python editor to set the default provider for exchanges whose product flow has a provider in the database. See Scripting in openLCA. The script below works correctly only for flows with exactly one provider in the database. If several processes produce the same flow, the script simply selects one of them.

print("collect providers from database")
providers = {}
for tech_flow in TechIndex.of(db):
    providers[tech_flow.flow().id] = tech_flow

print("set default providers in exchanges")
sql = "select f_flow, is_input, f_default_provider from tbl_exchanges"
count = 0

def update_rows_fn(r):
    global count
    provider = providers.get(r.getLong(1))
    if provider is None:
        return True
    is_input = r.getBoolean(2)
    if is_input != provider.isWaste():
        r.updateLong(3, provider.providerId())
        r.updateRow()
        count += 1
        if count % 500 == 0:
            print("updated %d providers" % count)
    return True

NativeSql.on(db).updateRows(sql, update_rows_fn)
print("all done")

Checking the migrated model

Regardless of which migration option is used, users are advised to validate the model after migration.

Validate the database

Right-click the database and select Validate. See Using mapping files and validating databases.

Check for:

  • broken links;
  • missing references;
  • other database errors.

Check LCIA coverage

  • After calculating a result, inspect the LCIA checks tab. See LCIA checks.
  • This identifies flows that are not characterized by the selected LCIA method.
  • Uncharacterized flows often indicate that elementary flows still need to be mapped or replaced. Unless it is a specifically uncharacterized elementary flow represented for informative purposes.

Compare results with SimaPro

  • Compare several key product systems between SimaPro and openLCA.
  • Investigate any differences rather than assuming that the migrated model is equivalent.
  • For ecoinvent-based models, comparison against official ecoinvent LCIA results for background processes is also useful.

Exporting back to SimaPro

Models in openLCA can be exported as SimaPro CSV files for use in SimaPro. See Exporting databases. If a mapping file was used during the import, the reverse mapping needs to be applied when exporting back to SimaPro.

Note: More advanced openLCA-specific features or specific SimaPro workflows may not be exportable without additional scripting with our free developer tools and API. Please contact GreenDelta directly if you need support with this.