The illustrations in the provided Wiki pages are for consultation purpose only and may not always reflect the latest implementation. 


Fields may vary depending on the action type of you project. Please read the onscreen information carefully to complete the relevant fields.

This page explains general mobility activity import files. The examples provided are based on the import for KA131, call 2022, Student mobility activities.

It is possible to export the mobility activity list as XLSX or CSV file and to import as XLSX or CSV. The instructions on this page are based on the processing of an XLSX file. The templates used for the import of mobility activities can be found on the page Data dictionary and Mobility Import-Export templates.

Take note

It is advisable to export the latest template after each release to ensure that any changes (e.g. added or removed fields) are also reflected in the file you intend to import.

For a quick overview of import and export of mobility activities in Beneficiary module, please view the eLearning video. 

The page Manage mobility activity export and import provides an overview of the process for importing and exporting mobility activities in beneficiary projects.

  • Erasmus+, Call year 2021 onward
    • KA121 - Accredited projects for mobility of learners and staff in school education, vocational education and training, and adult education
    • KA122 - Mobility for learners and staff in school education, vocational education and training, and adult education
    • KA131-HED - Mobility of higher education students and staff supported by internal policy funds
    • KA151-YOU - Accredited projects for youth mobility 
    • KA152-YOU - Mobility of young people 
    • KA153-YOU - Mobility of youth workers 
    • KA154-YOU - Youth participation activities 
  • Erasmus+, Call year 2022 onward
    • KA171-HED - Mobility of higher education students and staff supported by external policy funds


For specific conditions regarding Ukraine, see the page Project handling specifics related to the Russian aggression on Ukraine.



1. Open the XLSX file

If you exported the file from your existing project, you might already have some rows filled in with mobility activity information added to the project at an earlier stage. In the file you find the following:

  1. The first row details the names of the fields.
  2. The second row indicates:
    • if the field is mandatory to create a draft mobility activity record in the project, it is marked with (**)
    • if the field is mandatory to create/import a complete mobility activity, it is marked with (*).
    • if a dictionary value (DICT) is required or whether special formatting is required, such as the format for dates (DD-MM-YYYY) or decimal separators.
    • if a value will automatically be calculated (CALC) upon file import and the column can remain empty. 

Take note of the following:

  • Changes in the files since the last release are highlighted in orange text. Fields that are removed are also indicated with “strikethrough".
  • As of row three in the file, each row filled in, will indicate a mobility activity to be updated or created. 
  • In the exported file, the first row or title of a column indicates the field that will be updated for each mobility activity. Take note of row two of each column. This cell indicates for each mobility activity if a specific value or special formatting is required, if the field is mandatory or automatically calculated.
  • If a specific value is required, it corresponds to the behaviour of the field when creating or updating a mobility activity (for example a drop-down list for country selection). All possible values can be found in the Data dictionary. Those fields requiring a data dictionary value are indicated with DICT in row two of the column. 
  • In the templates, mandatory fields required to create a draft mobility activity in the project are marked with two asterisks (**) and mandatory fields to create/update a mobility activity as complete are marked with one asterisk (*).

Open the XLSX file

2. Column description

2.1. Basics

There are certain specific columns for each action type. Therefore it is important to consult the relevant data dictionary for the action type and call year of your project in order to fill in the file correctly.

For example, if your project reference number is 2021-1-RO01-KA131-HED-000002719, then KA131 relates to the action type and 2021 the call year of your project. Use the corresponding template and data dictionary relevant for your project and activities. For higher education, the templates are further divided into Staff and Students and the import for each file type must also be done separately.

The following columns are applicable to all action types and follow the same format. The position of these columns in the file vary according to the action type template you are using.

  1. The Grant Agreement Number column is always available, either in the first or second column in the file. You can see that this is a mandatory field by the presence of an asterisk in the second row. 
  2. The Mobility Activity ID is mandatory to create the draft mobility activity record in the project and must be unique for each mobility activity added in the XLSX file as well as for the entire project. The field is alphanumeric.
  3. The Activity Type, is also mandatory and must contain a valid dictionary value.
  4. In our example below, fields such as Blended Mobility Activity, Blended Intensive Programme or Doctoral Mobility activity are specific for KA131-HED projects.
  5. Some fields are only required if you have completed another field. For example if you have entered YES in the Force majeure column, you must also fill in the Force majeure explanations field.

A number of columns require a Data Dictionary value and are marked with DICT. See column C in our example. If the dictionary value YES or NO is required, this is also indicated. Only YES or NO can be used in these cells to indicate the answer. See column D in our example template for KA131 Students.

Grant Agreement No, Mobility Activity ID, Activity Type and other required fields

2.2. Participant specific columns

The Participant ID column (1) is not mandatory and no dictionary value or special formatting is required. If you do fill it in, the Participant ID must be unique within the project. The field is alphanumeric.

A number of columns deal with the participant details (2), for example their first name, last name, email, gender, date of birth, nationality, etc. Depending on the action type of your project, there may be additional columns.

Participant specific columns

2.3. Sending and Receiving Organisation ID, OID and Erasmus code columns

In all other modules, the Organisation ID (OID) refers to the ID generated upon registration in the Organisation Registration system (ORS). In Beneficiary module, the Organisation ID generated from the organisation registration system is referred to as the OID and the Organisation ID that can be defined upon creating an organisation in the project. The Organisation ID is a unique identifier assigned to each organisation in your project. This is not the same as the OID. All organisations in the beneficiary project have an Organisation ID, including partner organisations which may or may not have an OID.

Please note that:

  • The Organisation ID must be unique in the project. The Organisation ID in beneficiary module can be freely defined by the person creating the organisation in the system.
  • The OID cannot be linked to more than one Organisation ID in the project.
  • The OID is the ID obtained from the Organisation registration system.
  • The OID, when entered in the system, will retrieve all organisation details from ORS. Likewise, a new OID added to the file will retrieve the organisation details once the file is imported.
  • The Erasmus+ Higher Education Charter (Erasmus Code or ECHE), if available, can also be used to retrieve organisation details.
  • OID is not always required when creating an organisation in beneficiary module. This is dependent on the action type of your project and the role of the organisation. See Participating Organisations in projects for details. 

The Sending or Receiving Organisation ID is a mandatory field in the import file and it is used to identify the organisation in the file against the ones existing in the project. If you have started from an empty template, you may not see the default Organisation ID in the file, but you can overwrite it with the ID of your choice, by specifying it in the Sending Organisation ID or Receiving Organisation ID fields (1), as applicable.

Remember: the Organisation ID must be unique for each organisation in the project.

The OID is the unique organisation identifier obtained when registering in the Organisation Registration system. When the Sending or Receiving organisation OID (2) is filled in, other organisation details will be automatically filled in when importing the file. This is true for both sending and receiving organisations details. For partner organisations without an OID, provide at least the mandatory details, indicated with an asterisk followed by "if no OID" in the file. 

If the organisation is a higher education institution holding an Erasmus Charter for Higher Education, it is recommended to use the Erasmus Code instead of the OID in the relevant Sending/Receiving Organisation Erasmus Code (3) column. You can find the list of Higher education institutions holding an ECHE (2021-2027) on https://erasmus-plus.ec.europa.eu/document/higher-education-institutions-holding-an-eche-2021-2027.

Sending and Receiving Organisation ID and OID columns

2.3.1. Import organisations to the project

It is possible to use the import file to add new organisations to the project. 

Did you know?

A new Organisation ID creates a new organisation in the project as long as the associated OID or Erasmus Code is also unique for that project when importing the file. This allows you to add organisations to your project without having to add them manually from the Organisations section in your project. 

To add (a) new organisation(s) in the project via the import file, provide a unique Organisation ID for each new organisation in the Sending Organisation ID or Receiving Organisation ID field(s), as required. 

  • If the organisation you want to add has an OID, fill it in the Sending Organisation OID or Receiving Organisation OID field. When the OID is filled in, other organisation details will be automatically filled in when importing the file. Alternatively, if applicable, the ECHE code for the organisation can be used in the relevant Erasmus Code field. 
  • If the organisation you want to add does not have an OID, you must fill in all other details that are mandatory in the file for the sending or receiving organisation, indicated in the file with "if no OID".

In example below, adding a unique Organisation ID and the OID of an organisation not yet present in the project will create the organisation automatically in your project after the import is successfully completed. Once added, it will be available in the list of Organisations

Unique Organisation ID and the OID

2.3.2. Higher education specifics

In Higher Education projects, sending organisations can only be from Programme Countries. Receiving organisations from Programme Countries must hold a valid ECHE accreditation, except for Student and Staff Training activities (HE-SMT and HE-STT). For international mobility activities, the receiving organisations from Partner Countries are not required to register in the Organisation Registration system, nor to obtain an ECHE accreditation, but they must respect the ECHE principles. See more details about Eligible countries.

2.4. Date and Durations 

Dates must use the format DD-MM-YYYY, using a dash as separator, for example Start or End Date (1). Durations (2) must use integer numbers and the allowed number of digits is indicated in the second row. Durations that are automatically calculated upon import of the file display CALC (3) in the second row and can remain empty.

Date and Durations

2.5. Grant amount values

Certain Grant fields in the file will be calculated upon file import and do not need to be filled in. These are marked with CALC (1) in the second row of the relevant column.

Where a grant amount is required, the required format (2) is displayed in the second row of the relevant column.


Grant amounts must use the full stop as the decimal separator.

For example, a monetary value of 1500 EUR must be filled in as 1500.00 or 1500,00 in the file and not as 1.500,00. Using the last format will cause the file import to fail.

Grant amount values

3. Fill in the file

3.1. Add the first mobility activity

You will have to fill in one row per mobility activity you want to import. 

Provide all mandatory fields in your spreadsheet for the first mobility activity. Keep the information, explained above, in mind to avoid errors when importing the file into your project.

Add the first mobility activity in the file

For the following mobility activities, either fill in the additional rows one by one, or follow the instructions further below to copy the information from the first mobility activity row, then update as required for each of the additional mobility activities.

3.2. Select the entire mobility activity row and select "Copy"

In order to explain how to add new mobility activities, we will look at a simple scenario where three new mobility activities are added. 

Each mobility activity will have a different participant but coming from the same organisation and going to the same location for the same time for the same activity. The mobility activity budget is also the same for each mobility activity.

Select the row of an existing mobility and copy. 

Select the entire mobility activity row and select Copy

3.3. Select multiple empty rows and "Paste"

Select as many empty rows as desired, then paste the copied information. Depending on your spreadsheet editor, there are various options for the paste action. In our example, have the following options:

  • Press ENTER 
  • Press at the same time CTRL+V or CMD+V
  • Right-click on your mouse and select Paste

Select multiple empty rows and Paste

3.4. Update the mobility activity information

Update the specific details for each participant. 


  1. The Grant Agreement No. must be the same for all rows in the file.
  2. Update the Mobility activity ID. It must be unique for the participant in the project. You cannot have the same mobility activity ID twice in the file, as there will be errors at import.
    • If the Mobility activity ID is the same as that of an existing mobility activity (previously imported/added in the project), the new upload will overwrite/update the existing mobility activity.
    • Any new Mobility activity ID added to the spreadsheet will result in a new mobility added to the project.
  3. You can also update the Participant ID with a unique ID. Alternatively, leave it blank and an automatic ID will be assigned upon importing the file. 
  4. Update any other fields, such as the participant information, as required for each mobility activity in the file.

Update the mobility activity information

4. Save the file

Once all information is entered, save your file as XLSX or XLS. You are now ready to import the mobility activity file into your project.

Save the file

Expected Outcome