We essentially take a full SQL backup of the on-prem database and restore it into Flexera One. There are some transformative steps involved on our end (converting from single-tenant to multi-tenant schema, cleaning up old inventory and history records older than 90 days, consolidating data files if applicable, migrating operator accounts from Windows-based logins to email-based logins, and shrinking the database), but all important data and configurations are retained. As for customizations, the only thing we remove are custom reports that use a SQL exec statement, as we don't allow custom code/stored procs to be run in Flexera One. Since you won't have direct database access in Flexera One, you may need to refactor some things to leverage our available REST and SOAP APIs for data extraction. Any business adapters that are running against the database will need to be modified to use a staging DB on the beacon. These are all things that Flexera Services (or Flexera's partners) will review with you at the beginning of a migration engagement. I'll email you a copy of the pre-migration checklist slides, but they may not be overly useful without the discussion that usually happens along with them during the planning and design workshop.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
