@OldaNovak You are right: you cannot sync an Ambit2’s new moves with SA. At the moment that is entirely normal.
MovesLink2 (croc-connector program) isn’t intended to sync with Suunto App at all so you won’t see any new moves there from a sync. As @jw-cou wrote, the transfer copied your existing Movescount data to the SA db which you can review but not, as yet, add to via Suunto App. Check out this recent post.
Pre-Covid-19, Suunto stated that non-BT Ambit users will be able to have a “renewed experience” of functionality via the other cable sync program, SuuntoLink, “by summer 2020”. Check “Compatible watches”, May and November updates here.
@Dimitrios-Kanellopoulos importation from Movescount done on september this year.
But…
I just discovered last week that a lot of moves were wrong in Ascent / Descent values once imported :
on Movescount, these moves are fine ;
on SA, they are wrong.
I think the problem is coming from moves that were on the two platforms (in 2018, i was using the two platforms and synced my activities on the two services) : the Ascent / descent bug on SA wasn’t solved last year and i always get wrong values. So i stayed on Movescount the time to get this bug solved.
I remember reading some information telling us that once the bug solved, all the old moves with incorrect Ascent / descent values will be updated ? Am i wrong ?
What is the solution to have some correct datas for Ascent / Descent which correspond to the right values that are on the Movescount platform ?
I’m trying to ask some assistance from Suunto :
nobody on French phone assistance ;
i don’t find any way to contact some mail assistance…
Any idea, suggestion ?
