Migration Assistant Failures - And Solutions

Question

I used Migration Assistant to transfer my account from an Air to a new MacBook Pro.  I share the problems I ran into and the solutions I used in the hopes it helps someone else.
First failure:  the six digit confirmation number from the target (Mac Book Pro) would not display on the source (Air).  For some reason when I turned IPv6 on in Network preferences | WiFi | Advanced | TCP/IP | Configure IPv6 - to "Automatically" - the source displayed the confirmation number from the target.  The target already had IPv6 on Automatic - in fact all our OS X devices has it on Automatic - except for the Air for some odd reason.
The Migration Assistant took some time to finish the transfer - but, it did finish - or so I thought.
Second failure:  When I started the new user that was transferred - I got a number of errors.  In looking at the user home folder - I found that the library and other permissions were badly mangled.  Even OS X asked for permission to repair the library - I typed in my password as requested - clicked OK - but, it never worked.
The scenario 1 posted by Linc Davis fixed all the permissions immediately (see link and the part of the solution I successfully used below).
Linc DavisDec 25, 2014 9:40 PM Re: "The operation could not be completed" Creating an iMovie
Re: "The operation could not be completed" Creating an iMoviein response to patrickredsox
Back up all data before proceeding.
This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
Step 1
If you have more than one user, and the one in question is not an administrator, then go to Step 2.
Triple-click anywhere in the following line on this page to select it:
sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.

Answer 1

So I Found the issue.... It was stored in Private/var/zz/cleanup at startup
I found the profile name (home file) in the cleanup at startup folder and deleted it. System is working and now I have my disk space back.
I followed the directions that Linc Davis suggested in this post: How do I resolve 43+ GB of missing storage on the Macintosh HD?