When using AssetDatabase.CreateFolder from an AssetPostprocessor callback, the folder is created and although its GUID is immediately accessible, no asset can be moved to this folder because it is not immediately added to the asset database.
In the attached project, the goal of the CustomAssetPostprocessor is to move a "linked" asset whenever a "source" asset is moved.

Bug Reproduction Steps:
1. Import attached project.
2. In Project, delete the "Assets/DestinationFolder/Linked" folder.
3. Manually move the asset at "Assets/OriginFolder/Source/some_texture.pvr" to "Assets/DestinationFolder/Source/some_texture.pvr".

Expected result: File "Assets/OriginFolder/Linked/some_texture.pvr" is moved to the "AssetsDestinationFolder/Linked" folder.
Actual result: The "AssetsDestinationFolder/Linked" folder was successfully created but the "Assets/OriginFolder/Linked/some_texture.pvr" was not moved as a result. In the console, this error appears:
"Parent directory is not in asset database"

Notes:
-If the "Assets/DestinationFolder/Linked" folder is not deleted, the file is transferred succesfully.
-The user has also created the menu "Bug Report/Move Asset", which uses the exact same code the CustomAssetPostprocessor uses to move the "linked" assets but not from an AssetPostprocessor callback. Simply selecting it automatically transfers the files without any errors.

Reproducible with: 5.4.5p3, 5.5.3p4, 5.6.1p2, 2017.1.0b8, 2017.2.0a3