Subscribe
Share
Share
Embed
Need to use a SharePoint intranet due to internal policies, company transitions, or legacy systems? When all the available information is overly technical or negative, where do you turn? Enter Fresh Perspectives: Living in the reality of SharePoint intranets. We provide useful, jargon-free insights and real-world examples to help you maximize the benefits of SharePoint intranets and tackle its challenges. Pro-SharePoint but realistic, we debunk misconceptions and share product management insights from Fresh Intranet.
Welcome to another episode
of Fresh Perspectives.
I am David Bowman, product
director for Fresh Intranet.
I am missing my
little buddy, Jarbas,
for this episode,
but I'm joined by,
two guests, and we're gonna
do content holders anonymous.
We're gonna talk about
content migration,
the challenges, what
works, what doesn't.
And I'm joined by two people
who have a lot of experience in
this area.
Zoe, why don't you go
and introduce yourself?
Absolutely. So I'm a solutions
consultant at Advania.
I'm a part of the comms and collaboration
team alongside my colleague.
And we sit within consulting
and digital workplace and
really do all sorts of
projects related to SharePoint,
whether that's intranets,
migrations for intranet content
or document management or sort
of bespoke SharePoint solutions.
But, yeah, pass over to Shannon.
I feel like I don't have
to say anything now.
So exactly the same as
Zoe. So there we go.
But my name is Shannon.
Wonderful. All right, great.
Well, welcome and
thanks for joining us.
So I thought we'd start out with the
was going to say quick fire questions,
but they're probably not
really quick fire questions.
Let's let's start then
with what's the the Zoe,
let's let's start
with you first.
What is the biggest migration
that you've worked on?
That is a good question.
I think I've had, like,
twenty terabytes would be my
biggest in terms of, like,
content size.
But, yeah, it's usually, like,
huge more government agencies
who have content that
spans a whole generation of
time and have never gotten
rid of anything and they're
sort of wanting to move to the
cloud, sort of the
biggest I've seen.
Right. Shannon, same question.
Oh, I feel like I don't
know off the top of my head.
It's all merged into one.
One and more is to one.
I'd actually say though the
bigger ones tend to be easier.
So they go to the
back of my brain.
So, but yeah, probably similar.
Okay. All right.
Well, I guess interesting
aside then on that question,
what about kind of numbers
of sites, documents?
Do these numbers stick in your head
while you're doing these migrations?
This is something you wake
up two o'clock in the morning
thinking about that time you
made ten thousand sites from
SharePoint Classic.
Shannon, you've had an experience
recently with SharePoint twenty
sixteen, have you not?
Yes.
Which
is not quite ten thousand
sites, but it's enough sites.
We're moving like just
under a hundred sites, but
it's just hard to get yourself
back into the mindset of
SharePoint server and
remember everything.
And try and also
at the same time,
teach the client about
what's gonna change,
while also trying to think about
what they've currently got.
So I think even when
it's a huge number or a
small number, there's so much
to think about in terms of like
reeducating and also making
sure that we understand what
they've currently got.
And usually that's the
most difficult part because they
don't understand what
they've got either.
Yeah. Yeah.
Well, and, you know,
SharePoint twenty sixteen feels like
a long time ago now. Yeah.
But, you know, I think we we we were
having this conversation when we spoke
to Kripal Kavi from from
Microsoft talking about the
sort of legacy of SharePoint.
And this is a product
that has a long, rich,
varied history.
I'm old enough to remember
when it was introduced.
So it isn't a surprise to find
customers that are on very
old versions of SharePoint.
And, often in most of
those cases, I guess,
in in my experience,
customers don't tend to
delete a lot of data.
What's the, have you ever
had anything that was,
particularly old or
weird that you've
migrated, Shannon?
Not super weird, definitely old.
We find a lot of Christmas
party pictures from two
thousand and nine or
something like that, or
like employee of the
month from like, yeah,
two thousand and five
or something crazy.
They're the funny ones and it's so
hard to just like not have a
quick flick through and see
where they were in Christmas
two thousand and
eight or whatever.
Well, that doesn't sound like
that long ago to to to be honest.
It would be, you know, for me,
the pictures from Christmas
parties in the nineteen
nineties would be would be fun.
Zoe, what about you?
Anything, anything
weird, unusual, very old?
I think, yeah, Shannon's
probably covered the weird.
I think it's often photos that
sort of hit the weird category
for people wanting
to move across.
But in terms of old, I've
definitely had you know,
we run reports in a
migration which, you know,
pull back to, I guess,
metadata on all
sorts of documents.
And sometimes, you know,
it's things that haven't
been touched in twenty years,
yet somehow it's still on
the table to be migrated.
And it's, you know,
something no one knows about,
hasn't used,
probably couldn't even find
it in their current system.
But those sorts of discussions are
all on the table and a lot
of customers still want
to migrate those things.
Maybe in my opinion that would
be a weird case because I'm
not sure why you'd want to keep a
document no one even knew existed.
Yeah, that's Particularly
the Christmas party photos.
Yeah.
Okay.
So, you know, I guess we've we've
talked about we've talked about
before, and it's, you know,
a question that, you know,
when you're when you meet a
customer for the first time and
you're showing a
demo of intranets,
you're talking about
SharePoint in a
sense, and what they're describing
is we've got a lot of content from
a lot of places,
and we need you to
help us migrate it.
What are your experiences in those
conversations with customers?
Because often what they're
describing in the sort of first
conversations to what ends up
happening at the end of the
project can feel very different.
Talk a little bit about
your experiences there.
I think for me,
obviously when you're having
an initial conversation,
it's usually coming from one
person or one part of the
business, whether that's
the IT team or someone else.
And I think they have
a vision of, okay,
we can just lift everything
over or we can just take this.
And I think when we have
that initial conversation,
something that we tend to
push for is actually, no,
we need to speak to people
across the business,
different owners of this
content and get a clear picture
about what is being used,
what isn't being used.
And I think sometimes when
a client comes and says,
we wanna do a migration,
they just think it's
gonna be like a tick box.
Yes, no, we're taking this.
When actually a lot of it is
about having conversations with
heads of divisions or people
who own the content to
understand what's there
and what's actually needed.
Yeah. Same experiences, Zoe.
Yeah. Virtually the same.
It's easy for, I guess, people
at a high level, especially IT,
to sort of oversimplify
and think Yeah.
We can just, yeah, lift all
the content over here and,
you know, share point online.
But it's the there's
a lot of complexities
once you talk to actual users of
that content owners, you know,
all sorts of different workflows
they might have in place.
And I think a huge important
piece of migrations is
obviously, like, the user
experience out the other side,
which IT teams love to
forget about or think is an
important, you know,
that there's a huge technical
element of the migration.
But at the end of the
day, like, it's, you know,
talking to the users and
actually understanding how we
need to structure the solution
to actually make it work for
them on the other side.
Yeah. Yeah.
It's it's it's
I guess it's somewhat
amusing, know,
kind of in those conversations
and that, you know,
you what they're describing is
a situation where people are
getting poor results in search
and they can't find anything.
And then you get into the
conversation about content
migration, and then
what you get is, well,
we'd like to move everything
over to the new environment.
So well Just visitors.
gonna bring your
problems with you.
You know, this isn't necessarily
gonna resolve everything.
So, you know, I guess it
what what it sounds like is,
you know, kind of key point in
those early stages of project is to
start uncovering the value of
the content from the people
that are closest to it.
Is that a sort of
fair a fair statement?
Yeah.
Yeah. Absolutely.
If we can, it's sort of
running workshops sort of off
each department,
definitely content owners,
and yet it's the only way you
can really understand those
complexities, I think, rather
than, you know, talking to,
more like approached
high level project team.
Yeah.
And when you, you know,
when you're in there
having conversations then with the
people that are a bit
closer to the content,
do you find that there's a a
good level of understanding
about what's what they've got, what
they own, how useful, how valuable,
or is that the first time that they're
hearing about a lot of the stuff?
I'd say it really varies.
I've definitely met with people
where they it shocks me how
little they actually know about
their content and, you know,
even, like, where they
should be saving it.
But then other times,
you really find empowered users
who have have taken ownership
and have, you know, used the
technology they have to create, like,
a robust storage if it's for
documents or like a structure
that really works for
them and the team.
But yeah, on the flip side,
you can go in sometimes and they
have they can't help us at all.
Yeah.
Same experiences, Shannon.
Yeah, exactly the same.
It's just so varied.
Like Zoe said, it's
either people are really invested
and spend a lot of time managing
structures no matter
how deep they are.
Or they just go, oh,
I'll save it wherever.
And there's just nothing.
So they tend to not
be a happy medium.
It's either one
extreme or the other.
Right. Okay. Okay.
Well, and that, you know,
I guess that that's in some
ways is reassuring because you
at least know what you're
walking into in most instances.
And, you know, for the people
that you meet that, you know,
do have a really good sense of their
content and understand it really well,
what's the what are the sort
of attributes of the people or the
content of the organization
that makes a difference there?
What's the sort of what's the
magic ingredient that you find?
Yeah. It's a good question.
I think it's often the
the nature of the person.
It's someone who likes
organized, you know,
sets of folders and
something looking clean.
They're usually the ones who
are all on top of their content
and, you know, know exactly
where things should be going.
I also find in terms
like organizations,
if there's any sort of auditing that
happens or that sort of, you know,
any of that in place that they
need to be able to find things
and know stuff still
exists and get to it.
They are also the type of
organizations that seem to care
a lot more about how their
content is structured and that
it's findable.
Right.
Yeah. It's it's
interesting, isn't it?
Because, like, I could I
could probably bring to mind,
the names of sort of four
or five customers where I could
imagine that that person would have a
really good handle on on their content.
I think we'd probably share
some of the names on our list
would be the same names, think.
Probably.
When the project is unfolding,
and you're kind of in
these conversations,
you've got that sort of high
level instruction from IT about
we need to move everything.
You're starting to kind of get
into the details a little bit
the people in the organizations.
What are the common
challenges that
you're coming across
in those projects?
Are there patterns?
Are there things that every
organization struggles on or is
it different every time?
Shaman.
I think for me a lot of it
is like changes in behavior.
I tend to find like
when we're moving over
is the deep file structures.
And they're just wanting to create
a new folder for everything.
And it's trying to kind of
change the behavior slightly of
like moving to more best
practice of trying to keep it
threefold the levels deep,
then it will really
help you find stuff.
Trying to introduce metadata that
maybe they weren't doing before.
I think that's the a fear for
a lot of people of like, well,
we've been saving stuff
like this for ages.
I just create a new folder and
put version three point blah
blah blah blah.
And then we come in
and we're like, well,
we're gonna move stuff, but why
don't we try moving like this?
This is Yeah. Why
it's gonna improve.
And that's where I find a
little bit of fear from people,
especially if they've been working
in a certain way for a long time.
Right.
Zoe?
Yeah.
I would say a complexity
or challenge I find across the
board is always
permissions as well.
Because, I mean, lots of
sort of legacy systems,
like the way they did
permission management is often
vastly different to how it sort
of works in SharePoint online.
And especially with our,
yeah, best practice,
we don't usually
like to, you know,
start creating unique
permission levels once you sort
of get to folders.
So it's that sort
of restructures can,
yeah, cause, I guess,
just, yeah, complexities
with how we migrate or,
like, reset up permissions,
especially now,
obviously, with Copilot,
it becomes even more important
how permissions are managed in
terms of their
SharePoint structures.
So if for a lot of,
you know, customers,
a huge benefit of moving
to SharePoint online are those
more AI capabilities sort
of at their fingertips.
But then if they're just moving over
legacy permissions and they, you know,
these they're not even sure
what permissions they have set
up, it definitely, I guess,
creates more work
for them in the
future if it's not something
handled as part of the
migration, but to do more like
copilot readiness is like a
separate secret.
I just wanna as
Microsoft would say,
I wanna double click on a
couple of things that you you
mentioned there.
Well, we try to not cringe too hard
from my from my use of that expression.
Shannon, you were talking
a little bit about about
metadata, and, you know,
this is a really important
concept in in SharePoint,
which, know, I think
is is often overlooked.
I wonder if you'd just be able
to talk a little bit about why
this is important.
Yeah.
So essentially with
metadata, I mean,
the first description of it is it's
information or data about data, right?
When we use metadata, it
really improves search and
findability of documents.
Like if users are using
search in SharePoint and their search
terms are matching metadata
that's been attached to a
document, we're gonna see
more relevant and accurate results.
It also means that, especially
in SharePoint Online,
we can create different views
based on metadata rather
than going into those
deep file structures.
I think it's a new
concept to quite a lot of
organizations, which I think is
strange to us because we talk
about metadata so much.
But I think especially
with search being so
prominent in like intranets
and SharePoint now,
once you try to
like do a few demos,
explain how it can help
with search and findability.
They see the benefit of it,
but getting them to fill it
out is a different story.
But it's definitely a big
change in behavior for some
organizations.
Yeah, completely agree.
Completely agree.
Think it's often one of those
things that produces quite a
lot of eye rolling moments
when you start talking about
metadata with people.
But I think the moment that
people see the benefit that it
has and the value that it
can add in a well structured
environment is super powerful.
And I think particularly for
people that have moved from
sort of file share type
structures into SharePoint,
they've brought that kind
of, it sounds wrong to say,
kind of legacy mindset about
how they're going to store data.
And it is, as you say,
kind of reconfiguring someone's
behavior to be, you know,
think about it in metadata,
shallow stores of content
that's going to produce the
best result there.
The other one that
I want to just
pick up on there, Zoe,
you're talking a bit about how
important this is for Copilot
now particularly.
And I think, you know, as we're
all seeing people coming, you know,
back to SharePoint or
thinking about their content management
strategy in SharePoint
because of Copilot.
There's a there is a huge
connection between the kind of
quality of the outputs in
Copilot and how people are
thinking about, as you
say, permissions, but also,
having loads and loads of old
data, incorrect information,
that kind of stuff.
Can you talk a little bit
about about, you know,
any any views that
you have on that?
Yeah. Absolutely.
And, yeah, you as
you alluded to,
it's the sort of like
versionings and knowing,
you know, what
document is this, like,
latest source of truth is
definitely a massive part of that.
So I suppose in the
context of migrations, it's
us not migrating sort
of duplicates of documents,
for example, where, you know,
once they've all got the same
name with a v one, v two,
v three at the end.
It's actually doing
that sort of, you know,
reconciliation as part
of a migration as well.
So we're bringing in and using,
like, the versioning, I guess,
as a part of SharePoint where
it's just one document and the
versions attract
within it, I think,
is a huge part of
knowing, you know,
what you can pull back in
Copilot results is the latest
document is definitely,
like, a massive part of that.
Yeah.
And then, yeah, of
course, with permissions,
it's really just
making sure if these,
you know, secure documents that
they are correctly security trimmed.
And, you know, I think
it's empowering, like,
a more IT technical team to
use some of the functionality
within if that's, you know,
SharePoint premium or
something where there's,
so you can do reporting
and actually have, yeah,
that oversight of
correct sort of
security trimming within your
content and structures, I think,
is really important before sort
of hitting the go button on
Copilot. Yes.
Yes.
And I I guess,
ultimately, you know,
whether that's for a user
interface like an intranet or
answers in Copilot,
better structured, the
better permissioned,
the less duplicates, the
less incorrect information,
the better the outcomes are
going be all around you.
It's a sort of obvious
positive to that work. Yeah.
Alright.
I've allowed myself to become a
little bit distracted,
but a couple of important
points to pick up on there.
Just want to talk
about, you know,
we get into lots of
conversation about content
migration and this kind of
scripting versus automation
through tools versus manual.
Zoe, wonder if you could just give us
a bit of an introduction to, you know,
how you guys think about
the use of those different
approaches and, you know,
broadly what I cover.
Yeah. Absolutely.
So, yeah, I would suppose it
depends what type of content we are
migrating, primarily around
more like intranet or page
based content.
We've gone the more
manual approach.
I think it's, yeah,
the usual standpoint where it's
actually quite a recreation of
pages like a copy and paste
into new web parts and formats.
I think previously,
we've used Shared Gate
for a page migration.
We do have a subset of Shannon
and I's team who are the the
technical experts that usually
run those sort of toolings.
And that's, I guess, quite
the same with the larger,
more sort of document management
based migrations as well.
I think where possible, they
we usually go for, like,
a SharePoint native tooling.
So, like, the SharePoint
migration tool.
Or, yeah, I think ShareGate is, you
know, commonly used as, a first step.
Got your ShareGate.
Yep. Yep. Exactly.
I think migration
tools available.
Yeah. Yeah. But then, yeah.
I guess I can't speak for the
the super technical guys in our
team, but I'm sure there's
scenarios when those don't fit.
And then, yeah, there
is always, like,
custom scripting that might
need to be completed to sort
of make sure we can get content
across into SharePoint Online.
Yeah.
Shannon, any additional thoughts
on approaches, methods, tools?
Not really.
Just yet to reiterate that what
we tend to find is if it's any
If we're maybe migrating from
an intranet to an intranet,
a lot of the pages
manual, which me and
Zoe have sat, I know,
previously and recreated
many, many pages.
But then usually if
it's more of like a DMS,
things like that, that is where
either the tools, automation,
or the scripts can be useful
rather than downloading,
re uploading.
We tend to try and script
that or use a tool.
Yeah, anything kind of
page or news post related,
we sit down and put our
headphones on for a good few
hours and redo it.
Is there, is there a particularly
good type of music to listen to
while doing content migrations?
Oh, feel like me and Zoe have
very different, ideas on this.
Well, I would have gone for
slipknot or something, know,
I'd need the distraction
for doing that.
All right. Well, I won't press
you on your musical choices.
And and just to to sort of
pick up on the, you know,
you you were talking about kind
of intranet migrations and pages.
And I guess, correct me if I'm wrong
in in in the assumption on this one,
but, you know, because that's
graphical user interface,
people are gonna be
hitting those pages.
An automatic migration might
not create something that's
gonna look nice or make best use
of the feature functionality.
Is that the kind of
influencing factor to that?
Yeah. It's definitely
a part of it.
And also, it's you know,
we're making use of web parts
and sort of key functionality,
I think, on pages
where, you know,
you can't necessarily migrate
content, and it requires,
like, configuration front end.
So even if we can
get, you know, text content across,
which I think is what we
did with when we have used
ShareGate before.
It's just unfortunately,
the technology does require
sort of front end configuration.
And absolutely, it's like
adding imagery into a page.
My lights just turned back on.
But, yeah, it's like
there's definitely, I guess,
more visual elements which just require
configuration rather than just, yeah,
us hitting a button and everything
gets sped out the other side.
Yeah. Yeah.
And it does feel like the
sort of content that probably needs
a bit more consideration.
And I guess the advantage there
is that what you also don't
want is a kind of brand
new, fresh intranet,
excuse the use of
the word there,
with a lot of content that's
years old that's going to clog
up search and isn't actually going
to be that helpful for anyone.
Yeah, we usually try and
redirect them to, you know,
just recreate or remigrate,
really vital pages,
but otherwise, it is a massive
opportunity to start fresh,
and, you know, have more of like
a blank canvas to at least, like,
their news content and some of
the key informational pages.
It almost forces the customer,
I think, to, you know,
relook at what they've got and
bring some life back into it.
Yeah.
And DMS, document
management system, you know,
I guess that's, you know,
feels a little bit more
transactional from a kind of
content migration perspective.
Yeah. Definitely is. Yeah.
Okay.
That's where we tend
to see a lot more of,
the lift and shift or we create
a new document library and we
can move it over kind of thing,
which you can't tend
to do in an intranet.
Yeah. Yeah. Okay.
Where do things go wrong?
In, you know, in just I'm
specifically referring to content
migrations, not I'm not asking.
I guess one that I have kind
of worked through recently is
agreeing on new
structure, for example.
If we're wanting to change library
structure or, say for example,
I've just been working with a
client where they were using
sub sites still and we've
now moved them out to a flat
SharePoint structure.
I'm working with them
to understand what their
new document libraries
need to be and
agreeing what their folder
structure should be and what
their naming
convention should be,
rather than just lifting
and shifting has been quite
challenging and has
been kind of like, well,
we have the subsites now,
why do we need to change?
So it's explaining why we're
changing and then also getting
them to think about
what the change will be,
and then we can actually
do the migration.
So it's like a lot of steps before
we even get to that migration point.
Yeah.
Yeah. And I was
gonna add to that.
Sometimes the technical piece
is the easiest and where it all
falls over is when we sort of
wave goodbye at the door and
it's up to them to adopt it.
I've previously done, like,
a migration where the
customer was really willing.
They wanted to get all on
board with Microsoft Teams.
We did massive amount of team
facing sort of front end,
and actually SharePoint was
just the back end file storage.
But then when it came to
users actually working,
and Teams was just too
much of a jump for them.
They couldn't wrap
their head around it,
and therefore they just kept
saving their files locally.
And so all the work
we had done didn't get
adopted, which is
why I think, yeah,
having good communications
and training and ongoing
from the solution going live
to reinforce behaviors is
sometimes the biggest part.
Yeah, I think you're almost
back to the beginning of the
conversation about when
you are starting a project,
the expectation about a content
migration being a sort of a
mechanical, technical thing.
I think what what people
probably undervalue in there is
the importance of making
sure that the people that are
actually using it are gonna use
it in a slightly different way.
I mean, however minor that is,
it still requires a
change of behavior.
Yep. Absolutely.
Alright.
And then, you know, we we
talked a little bit about,
you know, people being
a kind of key success
ingredient in here, you know,
having a good understanding
of their content and information.
And, you know, I think for for
organizations maybe where there
aren't a significant number of
those people because they are rare,
are there other things
that if people listening
are starting to think about
content migration from
whatever to whatever,
what are the things that you
would like them to think about
before connecting with Advania
UK or some other vendor to talk
about content migration?
What's gonna help
them make this better?
It's a hard question.
I
think it's sometimes just
getting the kick start of the
internal work as
in making you know,
leading the the company or
organization know that
there may be a shift to
more up to date technology,
and it's getting those
conversations flowing
internally, ahead of
us engaging, I think,
quite important because I
don't know about you Shannon,
but I've definitely been put in
front of customers before when
they don't even know what's
going on and yet we're asking
them about their content
and they don't know why.
And then we're sort of spending
our time explaining why this
change is needed,
but to them they just feel
like it's happening to them.
So any sort of front footing
they can do around like
internal comms I think
makes our life a bit easier.
And then also alongside that,
sometimes you know cleaning up
the content they have already.
So it is it helps cut
through the process of
us needing to work at a
later date what can be left behind,
any sort of front footing
they can do on that,
asking their staff to start
cleaning up their areas content
wise or prioritizing what they
need, I think, is important.
Shannon, any, any additional?
I don't think so.
But, yeah, I've definitely had
a lot of panicky conversations
with people from teams
where they go, oh,
when is this happening?
I need to look at my
data. Don't do it yet.
And you kind of go, no,
we're not doing it right now.
We're just trying to
have a conversation.
But yeah, clean up is important.
And I always, you
know, trying to avoid
naming conventions
that don't make sense,
or you're never gonna remember
what that document actually is.
Avoiding like the
duplicates as well.
You work on a document,
you download it,
you re upload a new one,
trying to avoid and just
get into that kind of best
practice when it
comes to file storage,
which can be difficult.
But I think the first step
is definitely just to say to
people in the organization,
go and have a look
at what you've got.
Is there anything you know
you definitely don't need?
And can you have a little
think about everything else?
And then it usually sets us up,
with a good initial
starting point.
So a bit of a bit
of internal comms,
a bit of priming to get people ready
that there's something gonna happen.
Yeah.
Not saying the pulse is racing,
but having a bit of
preloading to a bit of work.
I mean, it sounds like ultimately not
treating it as a technology project.
I think that that kind of feels
like a good summary based on
what you said there.
Yeah. I agree.
And maybe just to
add to that, well,
is more of at a high level.
Sometimes it's the
organization actually
forming a digital
strategy for themselves.
So, you know, migrating into the
cloud or SharePoint Online is just the
first piece of the puzzle.
But I think sometimes if they
can form a a broader picture of
their actual strategy and
where they want to go from from
there, I think it would make,
definitely their experience
and understanding of where they
could go in the future also
helps with that buy in and
Yeah.
On why they need to move up
to the cloud for all the other
benefits that could
come in the future.
Absolutely.
And, you know, I I
couldn't echo what you said
any harder about, you know,
making sure that people understand
the why on these things.
Right?
You know, you're being asked to do something
that is potentially pretty annoying.
It's gonna take time out of your day
that you don't really have anyway.
It's not a fun job digging
through the Christmas photos
that you that you stored
in your OneDrive somewhere.
But, you know, actually understanding
that there's a significant benefit
to user experience, to content,
to improving answers
through AI that, you know,
I think people people deserve
a bit of explanation as to why
some of these things
are happening.
Yeah.
Alright. Thank you so
much for your time today.
Really appreciate you joining
us and sharing your thoughts on
content migration.
Of course. Thank you.
Thanks for having us.