Yes, we did so a few years ago. Our Sparx data model was configured very similarly to the core fact sheets we started with in LeanIX: Capabilities, Technology Categories, Applications, and IT Components. We created stored procs on our database tables (SQLServer) and extracted data into spreadsheets that we formatted to match the import configuration for LeanIX fact sheets. Then, did the same to update relationships between the fact sheets. 

There’s probably a more streamlined way to do this now, but this was a relatively easy way to establish our core inventory.

Hi, great questions. While we currently do not have documentation for tool specific migrations, we do have the feature sets to make transitions very easy. For example, with the inventory builder & import/export features it's now easier than ever. In addition to the basic factsheet configurations, and extensions our Professional Services offers a wide range of expertise in tool migrations. You can reach out directly to your Customer Success Manager to learn more. 

Our approach to onboarding to LeanIX was similar to the approach ​@Barbara Watts described. We were not on Sparx most recently (we had migrated from Sparx to iServer a number of years earlier, so we were migrating from iServer), but we were able to extract data from the legacy DB and formatted into LeanIX import spreadsheets. Our data model for LeanIX also was a close match to what we had in Sparx and iServer.

I think if we were doing the migration again, I would have had our teams spend more time on data cleanup and ensuring we had appropriate people marked as Accountable on all our fact sheets out of the gate.

If I was doing this today, I would consider using Inventory Builder to process all our iServer diagrams to help pick up additional fact sheets and relations, but that was not an option at the time (and I am not sure Inventory Builder is entirely ready for that level of complexity given the quality of our diagrams).