Failed migration from prepaid to postpaid plan

If your phone doesnt support esim, i recommend you sign up for postpaid normally (online or instore), and then you can port over from your Koodo prepaid to your koodo postpaid.  Once the port is completed, your prepaid line will automatically be closed

​@Dennis ill give it a shot and lyk tomorrow

Hey ​@Dennis , I have still been getting the same problems.

• When i try to migrate through the self serve option, I get the error from the screenshot in my first post
• When i try to sign up for the monthly plan as a new customer, I get prompted for my EID which my phone doesn’t support
• When i try to sign up for the monthly plan as an existing customer, i get rerouted to login to self serve as a prepaid customer which leads to the same outcome as the first option.

Did you clear out the cache and cookies on your browser? Have you tried using a different browser or device? If it still does not work, you may need to download an app that can make or receive calls from Canada, such as Fongo, and schedule a callback through Koodo Assist to that number to speak with a rep. https://widget.telus.tiia.ai/koodoprepaid/koodoprepaid.html

​@Dennis hey i sorted out the problem, how do i close this thread?

​@Timothy101  after a while, a rep will close the thread for responses if the issue has been resolved. Alternatively, you can also mark one of the responses as the “best answer” as the thread creator. Again, after a while, the thread will then be closed for responses, but where the best answer is given it is presumed closed by those who monitor the page (such as us mobile masters and reps).

Closing community threads would be up to the discretion of the Koodo reps who monitor the page so the times for when threads close can vary, but usually a couple of days to a week after the problem has been solved tends to be the norm.

Glad to see this worked out for you though🙂 What was the solution in the end where you sorted the problem?

hey ​@Oliver C thanks for responding.

I got around the issues by emailing my college and having the IT team get my authenticator app fixed.

• I did clear cache and used chrome (i use Firefox by default) but the problem still persisted
• Now i didnt fully go on to sign up as a new customer, bcs my school had already sorted out the issue tho i suspect it would have solved my problem

I’ll try migrating to a post paid plan when i get back to Canada with the plan that Dennis suggested.

thanks ​@Dennis and ​@MilkyWay