Initial Load and Reconcile of IdM accounts vs Resources. Any advices?

Question

Hellos.
Time is now to begin the initial startup of Idm where target resources already have entries.
Is there anywhere an idiots guide explaining to a novice IdM user the steps involved in loading and linking IdM accounts for the first time? I have to stress the guide has to be designed to meet novices needs i.e. those doing it for the first time.
We are fairly confident in running IdM from day 1. What I am unsure about is the best techniques to employ on day 0 so that the first FF Async run on day 1 will update IdM accounts rather than attempt to reinsert them.
We have 3 target resources: 1 AD 2 LDAP and 1 input FF Async source (plus a form for manual adds/mods)
The targets hold a mix of contract staff and employees. The FF source holds just employees, the contactor's data is entered by hand.
Am I being stupid if I do the following:
1. Load IdM Accounts from latest FF source (employees)
2. reconcile matching AD accounts by name.
3. reconcile matching LDAP1 accounts by name.
4. reconcile matching LDAP2 accounts by name.
5. from unmatched AD accounts since an AD account must exist for current staff make 2nd load file for contractors and load these accounts into IdM.
6. reconcile matching AD accounts by name
7. reconcile matching LDAP1 accounts by name
8. reconcile matching LDAP2 accounts by name
9 examine the leftovers and manually correct the mispelt or erroneous ones treating the rest as ghosts.
I am unsure just what the reconciliation is doing, I hope it builds the links between IdM and the resource.
What I am trying to achieve is a situation where I end up at the end of day0 where I have all the Idm accounts in my repository and are correctly linked to resource accounts so that the FF async can manage the bulk of them
I believe this has to be done for every IdM implementation. What I am after is advice and pointers to guidance from those who have had the experience of going though the implementation cycle at least once.

Answer 1

I had a similar problem although I was doing a load from file and I was linking the account to the resource.
I noticed you had:
<Field name='accounts[ISA].created'>
<Default>
<s>true</s>
</Default>
</Field>
Try using the following instead:
<Field name='waveset.accounts[GrandSlamXML].created'>
<Expansion>
<Boolean>true</Boolean>
</Expansion>
</Field>     
That is what worked for me.