Importing from svn when a 'non-standard' model is in use.

We do not follow the branch/tag structure presented in the SVN book. Instead the folder structure mirrors our development process. Our repository
looks like this
<pre>
component X\ &lt;-- code for component x
source\
release\ &lt;-- code for releases of x
1.0\ &lt;-- code based on release 1.0
iteration\ &lt;-- per iteration changes
1\ &lt;-- iteration 1's changes
2\
...
40\ &lt;-- iteration 40's changes
start\ &lt;-- mark start of iteration 40
build number\ &lt;-- mark build number X of patch 1
trunk\ &lt;-- trunk of iteration 40. Code for official builds of patch to release 1.0 come
from the iteration trunk. When a story ( see below ) is complete it is merged
into here.
start\ &lt;-- mark start of patch to release 1.0
story\ &lt;-- each bug fix or feature is in a folder under story
bug fix X\ &lt;-- For each bug fix ( or set of bug fixes ) and for each feature a developer creates
a story folder based off the current iteration trunk.
start\ &lt;-- Mark start of story
trunk\ &lt;-- trunk of story. When complete will be merged into iteration trunk.
trunk\ &lt;-- Everything under here is for next major release of component X. Same pattern as
under the folder 1.0 above.
binaries\ &lt;-- Builds of component X checked in here. Pattern is similar to what is under
source folder. However we only build from the iteration trunk so there are no story
folders.
</pre>

I don't see an easy way to import this into SVN while not losing history. And adding to difficulties are these wrinkles :
- Some components were split out from others
- The binaries of a couple of the core components are referenced by svn:externals in the source of dependent components.
- We are at about iteration 60. ( Each iteration is a 3 week period )

So what I looking for is recommendations on how this should be imported into RTC.

Thanks in advance.