ShareGate:

SharePoint migration:

Copy (navigation)

copy structure and content

copy content

source and destination

provide authentication as current user or other user.

For other user(provide login credentials)

Click on run pre check.

We have sub options to copy

lists/libraries alone,content type alone,

site columns, permisson groups, workflows, manage metadata.

For example copy list or lists, click on List, select the source list or multiple list.

On top right corner - Options

click on it.

Options:

General:

Action to perform:

copy as subsite of "parent site name"

or 

merge with 'parent site name' it self.

Configrations:

check mark options default selected. But we can add more.

Permissions, List views, webparts, Required features

customize list forms( eg: Nintex forms).

Workflows (Nintex or Designer or out of the box)

List content

Limit to (5) latest versions( which is max versions to copy)

site navigation,

subsites,

Required features,

Modern experience (All lists will be come as modern experience).

Start copy: start copy the migration

Run-Pre check: what are the errors and warnings.

Generates a report in excel.

Copy content only:

select source and destination.

select items what content from source need to copy to destination.

example: Pages folder

copy 4 items from source to desitnation

default.aspx, allfaq.aspx etc..

click on start copy, since there are many versions, we see all versions coping.

DMOaspx shows error. Page layout 'plans department page layout.aspx' could not found.

It is very common error.

since this layout is not available in target.

Click on Options:

Metadata section:

It will show you what all the metadata available in the source.

Click on Article page:

Page Layout: 

Set mapped value : which means what ever in the source layout we have to map to target.

In our case with error, layout is not availabe in the target.

now change it to 'set custom value'.

Then immediatly in right side dropdown it shows out of the box page layouts from sharepoint online.

Now select any one. Example (Welcome page) Welcome page with webpart zones. which is good choice to close match with source mostly.

But one thing to keeep it in mind, since we choose out of the box page layout, the webpart positions might be copied to different places.

Before start migration. Ask questions to the client.

1. which site from source to destination.

2. Migrate structure or with content.

If we start migration, meanwhile the migration happening, the fresh content will come up to the site, then in this case, we have to deal with delta migration.

To avoid this, migrate the structure and copy the content at a go sepeatly.

3. Uncheck workflow or copy workflows

4. Map unresolve users to system account, domain users to everyone.

5. Map source site tempate to team site with No M365 group.

User mapping:

Source unresolved user to system account, 

CLick on Mapping:

Source:

Unresolved users or groups: should be mapped to System Account.

Domain users mapped to distributed.

Now check in pre-check report, you can see few warnings pmclp\domain users

, plains\domain users, plainsna\domain users.

These three groups, source map with every one.

In Modern experience, Map source site template to Team site with No M365 group.

How to check Source site Template.

In Migration, check source site template before migrating.

Open the site in browser.

Right click on it, view page source.

Search for STS#0, If you found then you can confirm it as a team site.

If not found, then search for "SiteTemplateId" then if it has 'CMSPUBLISHING#0' then you can confirm it as publishing site.

If we don't map this site template in destination site means, In target also it will create a publishing site. since source site is publishing site.

If client wants modern experience means, you have to make sure choose team site in destination in mapping then only modern experience will work. Make sure choose No office 365 groups.

Click on Mappings in sharegate tool.

Go to Site templates mapping.

in Destination: choose Team Site (no M365 group).

Under source: Publishing Site, just hover then you can see black colour overlay shows "CMSPublishing#0" then you can confirm source is using same template.

Now in destination drag and drop Team Site (no M365 group).

Finally: Source is Publishing Site, and destination is Team Site (no M365 group).

After migration, In sharepoint online team site or not we can right click on the view page source of our home page

Search for "STS#3" then you can confirm as Team Site.