Migrate existing .net application to Outsystem

Hello All,

I have existing .NET and SQL Server application and would like to migrate to Outsystem. is there any steps /approach to follow? Approach based on

1) keep existing database

2) Migrate to Outsystem cloud


Thanks,

Jaydeep




Hi Jaydeep,

1. OutSystems integrates with your existing external databases. Checkout the article Integrate with an External Database 

2. When you are building your OutSystems application, you've an option to choose the infrastructure on cloud or on-Prem or hybrid. For cloud specific this evaluation guide explains the PaaS setup Deploying OutSystems in the cloud


Additionally, you may also consider to create an extension to reuse most of what is already available as part of your current application.

Regards,

Swatantra

Hi Jaydeep,

Regarding the existing database, it's possible to create an extension to map your existing tables into Entities, which means that you could continue to use the same database tables. I'd consider this only if you have other dependencies using these tables - otherwise I'd make a clean break and create actual Entities. A SQL script is necessary to move existing data, but this would be a one time event. Essentially, there's two options:

a) Map tables with an Extension - you can continue reusing existing tables, great if you have dependencies besides your application using them. More overhead than using actual Entities;

b) Create Entities, move existing data from tables to Entities - you get a clean break from the previous data model. Only really feasible if those tables only serve your existing application. Would require a one time SQL script to move the data.

Your business logic would have to be evaluated on a case-by-case basis. If you have complex rules/logic that rely on dependencies, you can again resort to Extensions and encapsulate that existing code and invoke it within OutSystems. Otherwise this logic would have to be translated into OutSystems code.

Swatantra Kumar wrote:

Hi Jaydeep,

OutSystems integrates with your existing external databases. Checkout the article Integrate with an External Database 


Regards,

Swatantra

Screen need to redevelop right?


Jaydeep Kadam wrote:

Swatantra Kumar wrote:

Hi Jaydeep,

OutSystems integrates with your existing external databases. Checkout the article Integrate with an External Database 


Regards,

Swatantra

Screen need to redevelop right?



That's correct.

Swatantra Kumar wrote:

Jaydeep Kadam wrote:

Swatantra Kumar wrote:

Hi Jaydeep,

OutSystems integrates with your existing external databases. Checkout the article Integrate with an External Database 


Regards,

Swatantra

Screen need to redevelop right?


Thanks for reply...

That's correct.



Afonso Carvalho wrote:

Hi Jaydeep,

Regarding the existing database, it's possible to create an extension to map your existing tables into Entities, which means that you could continue to use the same database tables. I'd consider this only if you have other dependencies using these tables - otherwise I'd make a clean break and create actual Entities. A SQL script is necessary to move existing data, but this would be a one time event. Essentially, there's two options:

a) Map tables with an Extension - you can continue reusing existing tables, great if you have dependencies besides your application using them. More overhead than using actual Entities;

b) Create Entities, move existing data from tables to Entities - you get a clean break from the previous data model. Only really feasible if those tables only serve your existing application. Would require a one time SQL script to move the data.

Your business logic would have to be evaluated on a case-by-case basis. If you have complex rules/logic that rely on dependencies, you can again resort to Extensions and encapsulate that existing code and invoke it within OutSystems. Otherwise this logic would have to be translated into OutSystems code.


Thanks for detailed explanation..