The two approaches are very compatible. In fact, it is completely possible to use both. That said, as you adopt Scrum, there will probably be two significant differences.
1) Scrum is very team focused. That is not to say that you don't have experts on a Scrum Team, but the whole team is responsible to work together and that means a lot less of "my work" and a lot more of "our work". Conversations should start occurring related to if it is best to divide and conquer or swarm on a few items. Both can be the right answer in different situations so this type of conversation should be occurring multiple times per sprint (1 - 4 week iteration).
2) While Kanban is focused on the flow of work and output, Scrum is completely focused on outcome. The team should be asked to identify what work needs to be done to solve real-user problems or capitalize on opportunities. This can be a lot of fun because it allows the development team a lot more leeway in creating solutions. However, it's also a lot more responsibility. The team will have to give over some of their "coding" time to solution conversations, stakeholder discussions, and concerning themselves more with understanding the problem space than before. They are also more responsible for creating an impact. If your team's success has been measured on doing the work you are given in the past, this should change and there is definitely an adjustment to be made.
Two quick caveats: First, practicing Scrum is a difficult transition to make and you might not see all of these changes right away. Unfortunately, there are a lot of organizations where you never see these changes. Second, as I said before, Kanban and Scrum are actually very compatible. Improving flow and output can give your team the capability to achieve the outcomes better. Don't throw out everything you learned from Kanban as you adopt Scrum.