diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index a330e665..649fb45e 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -71,18 +71,28 @@ BIZ OBJECT STUBBING
 
 todo: 
 	remove duplicates to get to one list, go through each at a time, check if retained or renamed then add to the Make these list.
+	go through all and check which ones need to be uniquified by checking db schema of v7 or biz rules maybe
+
 	go through all objects below in cases to see if they will be renamed or dropped or etc so don't create pointless objects
 	Consider making one of each of *all* Corebiz root object types but start with these ones first
 
+Note: "Files" refers to wiki embedded as well as, optionally exported, Assigned docs
+Note: Uniquify is required for porting some objects that in v7 didn't enforce unique names
 
-PORT these objects to  RAVEN:
-	
+* PORT these objects to  RAVEN:
+	Client -> Customer (wiki, files, custom fields)
+	Contract (wiki, files, custom fields)
+	HeadOffice (wiki, files, custom fields)
+	LoanItem -> LoanUnit (to better reflect what it actually will be with new features)(wiki, files, custom fields)
+	Part
+	Project  Uniquify + (wiki, files, custom fields)
+	PurchaseOrder (wiki, files NO ASSIGNED DOCS, custom fields )
 
-MIGRATE these deprecated things off of a USER object created just to host their stuff (user because only biz admin has full rights to user)
+* MIGRATE these deprecated things off of a USER object created just to host their stuff (user because only biz admin has full rights to user)
 Put them in an INACTIVE, NO RIGHTS User with the following naming scheme: "V7_REGION_REPOSITORY_regionNameHere" "V7_GLOBAL_REPOSITORY" etc
 
 	Global - wiki, files -> User "V7_GLOBAL_REPOSITORY"
-
+	
 
 Basic class:
      	public long Id { get; set; }
@@ -109,16 +119,8 @@ CANDIDATE OBJECTS:
 Note: in some cases object is gone or has changed, maybe need a token object of some kind that is created to accept wiki and docs from now defunct things?
 (like Region becomes a customer named "V7_REGION_REPOSITORY_regionNameHere"?)
 
-V7 WIKIABLE
-  GLOBAL
-  Client
-  Contract
-  USER PERSONAL WIKI
-  HeadOffice
-  LoanItem
-  Part
-  Project
-  PurchaseOrder
+V7 WIKIABLE    
+  
   Region
   Unit
   UnitModel
@@ -128,28 +130,15 @@ V7 WIKIABLE
 
   
 V7 ASSIGNED DOCUMENTS ABLE:
-Client
-Contract
-HeadOffice
-LoanItem
-Part
-Project
+
 Unit
 UnitModel
 User
 Vendor
 Workorder
 
-
 V7 CUSTOM FIELDS ABLE:
 
-Client
-Contract
-HeadOffice
-LoanItem
-Part
-Project
-PurchaseOrder
 Unit
 UnitModel
 User