By LAC Webadmin on Thursday, 30 April 2015
Replies 5
Likes 0
Views 1.7K
Votes 0
Hi There,

I'm helping a friend to migrate Jomsocial Data to EasySocial and a question came out if the migration tool is capable of migrating just the remainder of data that has not been migrated? The reason for that is we're planning to recreate a J2.5 live website to J3.4.1. So while on J3.4.1 is under dev we'll migrate the data but when it's done we will have to run a final migration of the current data in J2.5.x to J3.4.x.

Thanks,

Jackson
Hello Jackson,

Yes, you can add more fields to it if you want to
·
Saturday, 02 May 2015 03:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi LAC Infosys,

During migration EasySocial does check every data that has been migrated or not.
You can continue back the remaining part of the data that hasn't been migrated.
It's advisable and safer to have a backup before running migration.

You're welcome
·
Thursday, 30 April 2015 12:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ethan,

Cool! Good to know!

Another question that I forgot to ask. Does the migrator ask for a profile where it should migrate the data to? Or does it create its own profile automatically? If the migrator has the option to map the fields then I guess it is just logical for it ask for a Profile instead of creating its own, unless of course there's nothing selected.

Thanks,

Jackson
·
Friday, 01 May 2015 00:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Jackson,

I am really sorry for the delay of this reply as it is a public holiday for us here. It's actually a long weekend

The migrator would automatically create a new profile type on EasySocial and those users that are migrated would sit under that new profile type.
·
Friday, 01 May 2015 15:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,

Got it, so I cannot rename the profile migrator creates until I run the final migration. Will it be safe to add new custom fields, change settings on the profile created by the migrator?

Thanks,

Jackson
·
Saturday, 02 May 2015 01:07
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post