I am not sure what kind of help you are looking for... But let's see what options you have: 1) You leave you views, you create reports in iReport and deploy them in JS Pros: - the process is straight forward Cons: - you leave views -> maintenance and possibly inherited mess in queries - need to use iReport 2) You leave views, and create domains on top of them (threat them as tables) Pros: - all work in JS UI - may take advantages of domains (security, business view structure, data strategies, etc.) Cons: - you leave views -> maintenance and possibly inherited mess in queries 3) You create domains from scratch, and map all your views to derived table by just copying your view queries there Pros: - a single maintenance point (domain) - a possibility for incremental clean-up (you don't have to do everything at once) Cons: - some extra work is involved 4) You create domains from scratch, and create a new structure for your needs based on tables Pros: - a single maintenance point (domain) - you get it all fresh and clean Cons: - more extra work is involved As of best practice, it depends on your priorities. The quickest thing would probably be (2). The progressive thing with reduced risk would be (3). The getting it right (at expense of time and efforts) would be (4). And if you are not confortable with domains, (1) is there for you. Thanks, Andrew S.