[NoOne]

you export the players from both leagues, then re-use their playerIDs while copying over the rest.

keys for this to be easy -- same named teams in same order, so same divisions and everyrthing same initially... you can change them after import... teamID will be different, so you likely have to exclude that in the pasting or fixing it before copying. also, you need too ensure at least as many players exist in the destination league. easy to create many new players in bulk. just go to free agent screen and it's in availabel actions or somewhere in gui. can enter "354" new players to create etc...

About team id -- may need some tricks there. ie sort by team name may help, but probably already that way and by division. team ids are incremental and unique. so, if team A in division A starts with team id of "31" in one league and "55" in destination leauge, then you have to add 24 to all team id's as you copy/paste etc... simply make a temp column of data that says "=a1+14" then appl that in a series to last row. (faster than click and drag when it is this many rows... look up last row# first. it will auto increment a1, a2 , a3 in the equation... then copy/paste "special" only numeric values and no formulas.... all fixed.)

you know this because even though team id may shift, it still will order things i nteh same way.... all the way down to the mil teams. so, if you name things the same way, even though team id may shift, it's a simply +/- funciton to fix them to new leauge's values. with a spreadsheet, you can do all these things in a matter of minutes or even seconds if you are familiar with the process.. .do it once and fumble through it and the next time will be easier and so on. even if oyu don't know what you are doing now, it won't take long to learn it.

best to use a spreadhseet rather than a word processor for this. make sure to export with column headers tomake it easier to see playerID and Team ID.

the idea here is that you cannot create players through an import of a league player list. playerid's are a special case in a this database. they are a primary key. if they are not incremental and unique it won't work properly. if they don't exist, they cannot work. these must be created by the system. they are invovled in more than one table -- rDB. just because it's output in 1 file does not mean all that info comes from one table.

so, if you copy a playerID over that does not exist, it throws a wrench in the clockwork. as long as you replace everything else and re-import, it'll be fine. (team id is a unique key too with similar repercussions)

anything that is used as unique identification will work this way. (not names or addresses, dob, ratings etc... these are not unique. they are meant to be able to change. stick to those and you are fine)


EDIT:

does 15 have all the same ratings? if not you will have to manufacture some. e.g. if personality didn't exist you'd have to create that data... again, very easy to do in bulk with a spreadsheet. can either give everyone 100/200 or even Random(0:200) etc etc... throw in some "if" statements.. like if potential > X rand(100:200) to make those guys better etc etc...

impossible to recreate the ootp info. so you ahve to fill in the blanks for any 'new' column of data that didn't exist in 2015. also, ensure order is of columns is exactly the same. if they change that, it's an effort to prevent this or some spring cleaning thing of the db's etc etc. easy way to prevent those with less technical knowledge from doing this.