Token migration tool - worked for you? Where are CRE tokens stored?

Epicor ERP 10
1

We are upgrading from 10.2.100 to 10.2.400 this evening and part of the upgrade will be migrating from SDM to CRE using the token migration tool. Has anyone done this? Issues? (We are on premise and staying on the same VM server)

Also, during questions to tech support I was told by one that the existing SDM tokens are migrated into CRE and stored in our SecureDB. Then, a later tech support person said the CRE tokens are not stored anywhere in our system and are instead stored “on Epicor CRE Cloud Servers” and “once we have CRE running you can remove all the ESDM components including the secure db”… I have conflicting information and I’m trying to get a solid answer here. Any thoughts here to help clarify for me?

1 Like
2

Hello Adam,

Did you got any response about this? How did it go?

1 Like
3

No, I never got a clear answer. During that upgrade we ran into issues and had to just stick with SDM.

However, we are beginning to test another version and will need to complete this CRE migration very soon.

1 Like
4

Sorry to Necropost, but this is the only mention of someone trying this tool on here. We’re embarking on a migration from Epicor 10.2.400 and SDM to Kinetic 2022.2 and Epicor Payment Gateway / CRE.

Did you ever do the migration, or figure out this tool @Adam ?

I’m trying to figure out if I can test / run it at all before doing the final go-live migration, or if it should wait until we’re fully live in our new environment.

5

Adam,

From what I recall, we had a migration issue during the upgrade process and ended up sticking with SDM (we just reverted the CC configuration back to SDM, on premise).

Then, after being on 10.2.400, we were instructed to update the CRE install and re-run the token migration. All looked good, so we then updated the CC configuration tab, pointing to CRE.

If it were me, I would update to CRE before launch day, taking one piece of the challenge out of the equation. If it works, then you’d be using CRE in 10.2.400 and can upgrade to 2022.2 without that being a part of the process.

Epicor may have other suggestions… perhaps worth asking them about their suggested route.

1 Like
6

Interesting - hadn’t even thought about doing the cut to CRE while still on 10.2.400; we might try that! One less thing to have to worry about going wrong during the full go-live.

Sorry this may be a bit of a stretch to remember, but when you did the Token Migration in that “Token Migration and Mass Void Authorizations” screen, do you remember what combination(s) of these checkboxes you used? The Application Help isn’t super helpful on what the normal process would be, if you have to run it multiple times, if you have to use that “Retrieve” button on the Authorizations tab, etc.
image

image

7

We had “Convert tokens from SDM to CRE” and “Reauthorize” checked.

Also, had “enable logs”, but I don’t see that on your screenshot.

-Adam

1 Like
8

Thanks Adam,

With some encouragement here and my own reading, we gave it a go and failed. Kept getting errors about unable to open network connection. So we reverted to SDM, but then tried again a week later working with an Epicor consultant. There were some gaps in his understanding of the whole process too (apparently this is a piece of Epicor that is not highly used) but between the both of us we got it going. A few key things:

  • Set the ISO code on our USD currency (not sure this actually helped)
  • Installed the latest CRE, the one that came with our K2022.2 supplemental installs folder, on our current Epicor 10.2.400 application server. Apparently it didn’t like talking to that same version installed on a different host server. And the CRE that comes with 10.2.400 just plain don’t work anymore.
  • Had to switch SDM Web Server (SecureDataWS) over to http instead of https for the Token Migration process to be able to talk to it… oddly, it wants http and only http

Thanks again!