From SITE to DYCE: your path to the cloud

No. The important thing is that you don't expect everything to work and look the same when you switch to DYCE. Dynamics 365 Business Central + DYCE is not the same as SITE, just in the cloud. The experience gained from over 25 years of SITE has been incorporated and further developed in our DYCE apps. That's why DYCE is similar in many ways, but not completely identical to SITE.

A certain familiarization and transition period should be planned for both possible routes to the cloud (new setup and transition packs).

We set up a completely new system in the cloud for you, as if you had previously used a third-party system and now want Microsoft Dynamics 365 Business Central and DYCE. This is tantamount to a new implementation project and requires a great deal of effort on the part of the customer. The customer is responsible for exports from the old system and imports into the new system, for data preparation and selection.

A new system is unencumbered by old data and long-outdated facilities, a green field, so to speak, on which processes can be completely redefined.

As a customer, you need to plan for a great deal of effort in order to obtain a functioning system. You have to reckon with a lot of time for manual inspection and, if necessary, for changing setup tables and for testing.
Even if you will recognize many things in DYCE, it is not SITE. There are significantly different data structures for contracts and creating new articles for services and contractual services.

In order to enter the necessary data, it must be determined, cleansed and modified several times. Deviating structures must be taken into account. In our experience, the time and personnel required for this on the customer side is often underestimated.

We call the second option "SITE2DYCE" and involves transferring the data. This gives you the opportunity to "migrate" an existing SITE solution to the cloud. As this is not a real "migration", but a technically supported system change, we use quotation marks here.

Before the cloud "migration", the data must be transferred to a Business Central and DYCE-compliant data structure (transition). Of course, the eventual conversion to a current BC version, the creation of new data (if necessary) and the transfer of the data also requires some capacity. But in fact, the new setup is much more time-consuming.

We put together various data packages for you that you can take with you from SITE into the cloud, so-called Transition Packs (TP). We distinguish between 3-4 TPs.

TP1 (base):

Setup data, master data, articles

Financial accounting with chart of accounts, G/L items, dimensions, etc.

Asset accounting

TP2 (contracts, optional):

Service facility

Accounts receivable and accounts payable contracts with service items and IB

Open contract items

TP3/TP4 (trade, optional).

New creation of DL articles from DL resources

Acceptance of DL documents as project tasks

Takeover of the sales and purchasing heads

Modification and transfer of sales lines (e.g. conversion to DL articles)

Takeover of the warehouse stock

All essential settings from SITE are transferred, such as accounting data, master data, transaction data and - if required - stock levels. Take advantage of this opportunity: the transition packs immediately transfer your data to a new table structure with new logic.

The preparations for this can be made during ongoing operations.

Incorrect and outdated settings and setup data are transferred. However, you can clean these up after the transition and cloud migration. The same applies to the transfer of any outdated master data.

Some data from SITE may not be displayed reliably in DYCE, e.g. contract lines without IB.

You yourself have less work, but higher costs for data migration and transition packs. You should also plan for higher storage requirements in the cloud, as more data will initially be transferred.

Some things can be transferred, e.g. predefined table packages, some things cannot, e.g. individual data records.

In principle, only data that can be used in Dynamics 365 Business Central and DYCE can be transferred. Unfortunately, this does not include the history.

In an additional project, we would be happy to introduce a professional ticket and support tool for you: namely Jira Service Management.
This allows you to work much more customer-centric and efficient than before! Take a look at the possibilities for yourself. Learn more about Jira

DYCE Time Tracking also provides you with a seamless connection between Jira and Business Central. This allows you to conveniently transfer time tracking from Jira for your billing.

We recommend Microsoft Dynamics 365 Sales for optimal customer loyalty, sales campaigns, etc. With this CRM tool, you benefit from AI-driven analyses and an optimized sales cycle. Find out more.

Our DYCE API Connector for Dataverse app connects Microsoft Dynamics 365 Sales with Business Central and you can access all data seamlessly in both your ERP and your CRM.