How do I move my shoe collection into another running app without starting again?

If you are moving your shoe collection into Cinda, you can import screenshots of your existing list, check the proposed shoes and visible mileage, then finish setting up each pair. You do not have to retype every name. The result is a starting collection with mileage totals, rather than a transfer of your complete activity history.

For any other destination app, check what that app actually accepts first. A downloadable archive from one service is useful only if the next service can read the relevant shoe data. “Import activities” and “import my shoe collection” are different capabilities.

What information do you need to carry over?

Before changing apps, make a simple record of each physical pair: brand, model, version, current mileage and whether you still run in it. Keep the unit beside the total. Add a distinguishing note if you own two pairs of the same model.

Nicknames can make sense to you while hiding information another app needs. “Blue trainers” does not establish a model or version. Where possible, make the exact name visible in the source list before taking a screenshot, or keep a separate note you can use during review.

Shoe names and versions

Proposed from the screenshots, then checked by you against the pairs you own.

Mileage visible beside each shoe

Read where available. Verify the number and unit; fill missing totals yourself.

Your run types and feelings about the pair

Finish these in Cinda. Suggested roles do not replace your own experience.

Past activities and future syncing

Not transferred by shoe-list screenshots. Keep any activity archive separately.

How Cinda's screenshot import works

1. Capture a readable shoe list. Cinda's import is intended for lists such as Strava gear, Garmin, Runna, Coopah or your own notes. Show the names and their associated totals. Crop out personal information the import does not need.
2. Sign in to Cinda and open the add-shoes screen. Choose Or import from a screenshot, then select up to three screenshots at a time. PNG or JPEG is a straightforward choice if an image cannot be read.
3. Review what Cinda found. Catalogue matches are selected initially. Untick anything wrong or unwanted. Check the exact version, not only the model family.
4. Choose any unmatched entries deliberately. These are offered as custom shoes and are not selected automatically. A custom shoe can keep a name and mileage in your rotation, but Cinda has less information for analysing it or choosing it for a run.
5. Finish the shoe drafts. Check mileage, choose the run types and say how you feel about each pair before saving. Catalogue-based run types are suggestions you can change.

The current importer handles up to 20 extracted shoes in one request. If your collection is larger, split it into clearly separated batches and check what was added before the next batch. A screenshot containing a retired pair can produce an entry for it too, so leave out shoes you do not want in the collection you are building.

The screenshots are processed using Cinda's AI provider to read the names and mileage. Crop out information you do not want processed and review the results. The privacy policy explains the providers and data handling.

What should you check especially carefully?

Version numbers. An abbreviated family name may be matched to a version you do not own. Leave out a wrong proposal and add the correct catalogue pair manually, or use a custom entry if it is unavailable.

Separate physical pairs. Two identical models are still two pairs with different histories. Check that both survive the move as intended, and do not rely on the importer to distinguish them from a repeated screenshot of the same pair.

Miles and kilometres. Cinda converts imported distances to whole kilometres internally and displays mileage in your chosen unit. Small rounding differences can occur. A large difference needs checking against the source, especially if the screenshot omitted its unit. The import caps a shoe's total at 9,999km.

The starting total. If a source screenshot says 420km and you import it, that is a starting total of 420km. Do not then add your old 420km again. If you run 8km afterwards, the next total should be 428km.

What happens after the move?

This route does not connect your Strava account, synchronise future activities or bring across every historical run, note and shoe assignment. Cinda's mileage updates are manual. Decide which record you will keep current, or how you will update both, so the totals do not quietly diverge.

Keep your original list or screenshots until you have compared every imported pair and total. Then your first useful Cinda task can be choosing a shoe for an upcoming session using the collection you have just checked. The Cinda guide explains the wider rotation and run-logging workflow.