079 Considerations When Migrating To New Tech
I’m definitely blowing the 20 hours a week out of the water here the last couple weeks, but once I get things set, I should be able to reduce those hours. Hopefully, otherwise, we’re going to have to rethink the plan.
What I wanted to share with you today are some considerations when you’re moving from one platform to another. Specifically, I’m moving a new product or an existing product from an old website to a new website.
Here are the things to consider:
Split to duties and roles
You can split out the copy, the graphics and the technical components separately so that everybody can work independently and you can pull them together and that way that won’t slow down your timeline. Because everyone of those people right now is me, I can do them but it really helps if I write them out in a document so then I can go ahead and just type in the copy, create the graphics separate, and then do it all at once.
First time learning curve
The second thing is the first time you do anything, it takes longer. So, when I do this for the next product that I migrate over, I expected to take about 50% less. Probably 25% to 50% less the time because I’ll have everything set up.
Know the basic flow
The next item is to understand the flow of the new program and the technical stuff and how it works. Map out the items logically and then technically depending where your strengths are, but understand the flow of what you want to map out.
For example, you know, if I’m selling a product, I need a sales page; I need a purchase page; I need a thank you page. Once they get in, they’re going to need access and so they’ll be a welcome video and then the components they need access to. So, if you can logically think about that and map it out on a piece of paper just so you understand the flow and that’s good enough. Again, if you’re not technical or not, but at least you’re all on the same page, then that’s really helpful.
Test, test, test
The last couple items are when you create it make sure you’ve tested. So get it all set up and then create a test user, dummy user, test data, or whatever you need to test to validate that it works.
Then, finally, release it to the public. So for me, the goal is to finish up getting everything configured. I will do a last test tomorrow when I’m fresh and then I will release it.
#podcastdaily
For show notes or more information, for the Kim D Snyder show, go to
https://KimDSnyder.com/podcast
.