@@ -8,8 +8,8 @@ Web-based migration / import without jumping through CLI hoops may or may not fo
## Requirements
* An up-to-date [stops.csv](https://travelynx.de/static/stops.csv) dump
* An up-to-date [user data export](https://travelynx.de/account)(“travelynx-export-*username*-*date*.json”)
* An up-to-date [stops.csv](https://travelynx.de/static/stops.csv) dump from the source instance.
* An up-to-date [user data export](https://travelynx.de/account)(“travelynx-export-*username*-*date*.json”) from the source instance.
* The ability to run `perl index.pl import` commands on the target instance.
## How-To
@@ -28,5 +28,8 @@ travelynx calls the former “eva” and the latter “external\_id” or extID.
So, in order for an import to work, there are two requirements:
* The target instance must know all stops used within your trips.
* When importing, numeric stop IDs used for MOTIS trips must be mapped from the IDs on the origin instanece to the corresponding IDs on the target instance.
These are typically *not* identical, but can be mapped via (slow) extID lookups.
* When importing, numeric stop IDs used for MOTIS trips must be mapped from the IDs on the source instanece to the corresponding IDs on the target instance.
These are typically *not* identical, but can be mapped via the source instance's stops.csv export and (slow) extID lookups on the target instance.
