I'm not trying to be patronising at all here, it's just the way I come across some times.  I just want to make sure we're all on the same page here about how XDF's and defining files work; it might just be the way you worded it.

When you load your bin into whatever editor, be it TunerPro or WinOLS, you need to load in a suitable XDF or .kp to allow the software to understand what data is stored within that file.

Now, the file that you've put into the software is the original bin from your car; which is fantastic.  You cannot load in any other bin from any other car, because it does not match.  You need to stick with your bin, and your own XDF, which will need padded out due to not one existing.  Personally, I'd forget TunerPro and stick with WinOLS because it helps with defining maps not in your current mappack.  With the "Connect Windows" button, you can find patterns between binaries to help you further define your file.

So, say your file is a 1.8t ME7.5 file.  Load in a fully defined 1.8t ME7.5 file alongside it to allow for the connect windows option to work properly.  Now line the windows up (you'll need an offset, which is why using connect windows is good, because it allows you to see patterns between the windows).  Do it until your file lines up with the defined file.  You can now use WinOLS to transfer the map details across to your file.

At this stage, your mappack has a new map.  Your file has NOT been changed.  The software just understands what is now stored in that location. 

If you're comparing files, you must use similar ones, for obvious reasons.

The Stage 1 threads are good to give an understanding, but don't use the files within them if they're not suitable for your car.  The map names are usually consistent though.  Furthermore, use the Wiki, and have an A4 notepad beside you at all times for note taking; you'll need it a lot. 

The way you worded your original sentence (Found a stg 1 nefmoto xml map created last year in the community project thread above. Imported it into the one I am creating for my current build." makes it look like you've imported a 2.7 xml into your 1.8t file.  Correct me if I'm wrong, but that's the way it reads.  If that is what you've done, it WILL NOT WORK.  You need to suit XML's to their suitable files.  That, and the is peculiar to a specific bin (hence my offset things.  Although there is 10+ versions of 1.8t files, the data stored within are all at different locations.  You can't use one XML for one file on another.  They must match.

Probably too wordy, I just won't want you changing data where the XML points to the wrong address, that's all.

Awesome man, that clears that up.  Basically, read the Stage 1 files and understand the changes.  Stage 1 shouldn't take you more than a few hours to understand and edit. Only a few maps.

Personally, I found understanding ESKONF the hardest as a noob, maps are easy because its got units and axis.  Could probably get a thread up documenting what you're doing with your file and logs as you go.  It'll help you understand, and people are always good at helping you too (read: nyet, DD etc).

It is when you're not snowed under with every other map under the sun.  It fried my head at the start, but so did a lot of things.  Lots of notes helped.  The Wiki sucked back then too. :p

So, I am not finding maps that look similar to the ones I can, or should be modifying in the attached bin I used for my Corrado project last year, newer ecu. No maps for that build as it was all from within tunerpro that I worked last year.
What I'm trying to do is use the best of the Rado mapping as a starting point for the Audi, if possible.
If I can get some help highlighting what I can/should use, or not, to get the Audi up to 16/18 psi Boost, balanced, I can do the work, I think, or at least want to. All the maps seem there in OLS now, NMAX currently 6600, KFLF, currently 1.001, KFMIOP currently 91.006@4000rpm@160%load, etc.
I just don't know what to start with or what areas to tweak. I'm all about DIY, but to me it would still just be guessing at the start and that's no way to learn. The S4 wiki is not intuitive and I am not new to learning from technical text.
Thanks.

Appreciate the reply Nyet. I was under the impression that the community threads, being different ecu's and files would be non-applicable to me. I will take a look through the 1.8T thread in it's entirety.

Really, without changing my MAF housing, injectors or fuel delivery system at this point, I am focusing on boost, torque and timing.
Seems I should be focusing on 4 maps as per what I've read, but I am finding a boatload more than 4 in my BIN while scrolling through.. Not sure if I need to dive in to ESKONF or not at this point either.

To give some background, I am an Aircraft Engineer/Industrial Millwright by trade and have intimate knowledge of combustion engine design and applications, but nothing in the programming or Bosch world of ecu management. I know what a well tuned engine 'feels' like, and can maintain it as such, but damned if I know how to get there,,,yet.
Thanks again gentlemen.

Perusing the community thread and pulling the data out of the tables within that stg 1 file I have made a text file as attached.
If I am starting to 'get' it I need to input the data from this text file into my audi bin at the Audi bin's addresses as indicated? I have already added the map definitions from the attached kp file into OLS for my 018P ecu.
The 1.8t community build thread is an interesting read. thelastleroy seems to have walked a few miles in the shoes I'm trying to wear currently.
Thanks again gents.

There are north of 5000 maps in ME7

You can't copy them blindly. Their locations are different.