Copy Company from Production 1 to Production 2 (Cloud)

julkifli33

Hi all..
I have 2 production environment at the same tenant
Production 1 --> W1
Production 2 --> AU
I want to move some of the companies from Prod1 to Prod2.
how do i do that?

Please advise.
Thanks.

TallyHo

Can I export a company (administration) from dynamics 365 bc, and import it in another SaaS tenant?

No, you cannot directly export and import a company (administration) from one Dynamics 365 Business Central SaaS tenant to another in a simple manner. However, there are some methods you can use to achieve the same outcome, although they involve additional steps:

1. Data Export and Import Using Configuration Packages (RapidStart Services):

Export the Data: Use the "Configuration Packages" feature (part of RapidStart Services) to export the data from the first tenant.

Go to the configuration packages and select the tables or data you need to export.

Export the package to an Excel file or directly to a .rapidstart file.


Import the Data: In the destination tenant, you can then use the same "Configuration Packages" feature to import the data.

Upload the exported file and import the data into the new tenant.



Limitations:

This process does not transfer everything (e.g., customizations, permissions, and some settings).

Manual adjustments might be needed, especially with dependencies between tables.


2. Full Database Export and Import (Limited to On-Premise or Hybrid Scenarios):

If you have access to an on-premise or hybrid deployment, you can perform a full database backup in a non-SaaS environment.

This is not directly applicable in a SaaS-to-SaaS transfer since SaaS environments don't allow full access to the SQL database.


3. Replication with APIs or Extensions:

Use Business Central APIs or extensions to extract data from the source tenant and import it into the destination tenant.

This approach allows for more flexibility in selecting which data to migrate but requires development effort.


4. Manual Recreation of the Company:

In some cases, you may need to recreate the company manually by setting it up in the new tenant and migrating the master and transactional data through configuration packages or integration tools.


5. Use of Third-Party Tools:

Some third-party tools like Jet Reports, eOne SmartConnect, or Cosmo Consult offer data migration and integration features that can assist with this process, making it smoother compared to manual data transfer.


For SaaS tenants, Microsoft provides limited control over database-level access, making direct exports/imports difficult. Instead, the configuration package method and APIs are the most feasible for transferring data.

TallyHo

How to do this with jet reports?

Jet Reports is primarily a reporting and data analysis tool, and while it is excellent for extracting data from Dynamics 365 Business Central (BC), it is not designed for data migration between tenants. However, you can leverage Jet Reports in conjunction with other tools to assist in data migration between two Dynamics 365 BC SaaS tenants by exporting data in a structured manner. Here’s how you can approach this:

Steps for Using Jet Reports to Assist with Data Migration:

1. Set Up Jet Reports:

Install Jet Reports if it’s not already installed and ensure it is connected to your Dynamics 365 BC tenant.

Configure Jet Reports to access the tables and data you need to export from the source tenant.



2. Design the Data Export Reports:

Use Jet Reports to design custom reports that extract data from specific tables in Dynamics 365 BC. For migration purposes, you may want to focus on:

Master data (e.g., customers, vendors, items)

Transactions (e.g., invoices, orders, ledger entries)

Setup data (e.g., chart of accounts, dimensions)


The reports should generate data in Excel format, which can later be imported into the destination tenant.


Example Report Design:

Customer Master: Create a Jet Report that extracts all fields related to customer data from the Customer table (e.g., Customer Name, Address, Payment Terms, etc.).

General Ledger Entries: Extract the required fields from the G/L Entry table (e.g., Document No., Posting Date, Amount, etc.).



3. Run and Export Data:

Run the reports and export the data to Excel. Jet Reports will allow you to extract large volumes of data from your Business Central system, which is helpful for gathering information from multiple tables.



4. Prepare the Data for Import:

Once the data is exported to Excel, you may need to clean and format it according to the requirements of the RapidStart Services configuration package or API endpoints that you will use to import the data into the new tenant.

Ensure that any primary keys, foreign keys, and references between tables are maintained.

Remove any redundant or system-specific fields that should not be imported (e.g., auto-generated IDs).




5. Import Data into Destination Tenant:

Use the RapidStart Configuration Packages or APIs to import the cleaned and formatted data into the new SaaS tenant:

RapidStart Services: In Dynamics 365 BC, use the "Configuration Package" functionality to import the data from the Excel sheets generated by Jet Reports. Create a configuration package that matches the structure of the data you’ve extracted and then upload and apply the data.

APIs: If you have more complex data requirements, you can use APIs to push the data into the new tenant.




6. Validation:

Once the data is imported into the new tenant, validate that the records (e.g., customers, items, transactions) have been successfully migrated.

Run reports in the new tenant or use Jet Reports again to cross-check the data integrity between the old and new tenants.




Limitations of Jet Reports for Data Migration:

Manual Process: Jet Reports will only assist in data extraction, but it doesn't automate the full migration process like dedicated migration tools. After exporting the data with Jet Reports, you still need to manually prepare the data for import.

No Transaction-Level Migration: Jet Reports is not designed for migrating transactions with full audit trails. You will need to replicate transactional data via APIs or another integration method if needed.


Combining Jet Reports with Other Tools:

Jet Reports + RapidStart: Jet Reports can help extract large datasets from Business Central, and you can then import this data using RapidStart Services. This method is manual but reliable for simple data migrations.

Jet Reports + Custom Integration: If you have a more complex migration scenario, you can use Jet Reports to export the data and then rely on APIs or third-party tools (like SmartConnect or KingswaySoft) to handle the structured import of this data into the new tenant.


Conclusion:

While Jet Reports is not a full-fledged data migration tool, it can be part of your data migration strategy by helping you extract and prepare data from the source system. You'll need to combine it with tools like RapidStart Services or APIs to perform the actual data import into the destination tenant.

TallyHo

How to do this with eone?

eOne’s SmartConnect is a versatile data integration tool that can be used to migrate data between two Dynamics 365 Business Central (BC) SaaS tenants. Unlike Jet Reports, which focuses primarily on reporting, SmartConnect is designed to handle data migration, transformation, and integration scenarios, making it a better tool for transferring data between two Business Central environments.

Here’s a step-by-step guide on how to perform the migration using eOne SmartConnect:

Steps for Using eOne SmartConnect to Migrate Data Between Two Dynamics 365 BC SaaS Tenants


---

1. Set Up SmartConnect Environment

Install SmartConnect: Ensure that SmartConnect is installed and configured. If you’re using the cloud version, set up your environment through the SmartConnect portal.

Connect to Source Business Central Tenant:

Add a connection to your source Business Central tenant via Web Services or the API. SmartConnect provides pre-built connectors for Dynamics 365 BC.

You will need the tenant ID and proper authentication credentials (OAuth or Web Services).



2. Identify Data for Migration

Determine which data needs to be migrated:

Master Data: Customers, Vendors, Items, etc.

Transactional Data: Sales Invoices, Purchase Orders, Ledger Entries.

Setup Data: Chart of Accounts, Dimensions.


Assess the relationships between data entities to ensure that dependencies are maintained (e.g., Customer IDs in Sales Orders).


3. Create Data Maps in SmartConnect

Source Map Setup:

Create maps in SmartConnect to pull data from your source tenant. You’ll define these maps based on the tables you want to migrate (such as customers, vendors, transactions).

You can pull data using SOAP Web Services, ODATA, or API queries within SmartConnect.

For each map:

Define the source: Choose Dynamics 365 Business Central as the data source and specify which table or entity you want to extract data from.

Map the data fields: Ensure that all the fields you want to extract are selected (e.g., customer name, address, etc.).




Example Map:

Customer Master Data: Create a data map that extracts all fields from the Customer table (e.g., Customer ID, Name, Address, Payment Terms).


4. Apply Transformations (if needed)

If data needs to be transformed (e.g., changing data formats, renaming fields, removing invalid entries), use SmartConnect’s transformation features:

Data manipulation functions: Perform actions like trimming, concatenating fields, or converting data types.

Custom scripting: If more advanced transformations are needed, you can use C# or VB.NET scripting within SmartConnect.



Example Transformation:

If a particular field in the source tenant uses a different naming convention or format, you can use a transformation to convert the field before importing it into the destination tenant.


5. Set Up the Destination Tenant

Connect to the Destination Tenant:

Add a connection to your destination Dynamics 365 BC tenant using the same approach as with the source (Web Services or API).

Ensure you have the necessary permissions to write data to the destination.



6. Create Data Maps for Import

Destination Map Setup:

Create maps that will import the data into the destination tenant.

For each map, ensure that:

The data source is the output of your previous extraction map (e.g., an Excel file, direct BC data, or an intermediate table).

You map the source fields to the appropriate target fields in the destination tenant.

Handle primary keys and foreign keys carefully to avoid data duplication or mismatches.




Example Map:

Customer Master Data (Import): In this map, ensure that each field from the source (Customer ID, Name, Address) is mapped to the correct field in the destination tenant’s Customer table.


7. Schedule or Run the Migration

Run the migration maps:

You can run the data maps manually or schedule them to run at a specific time.

Monitor the process to ensure the data is being transferred correctly.



Incremental Migration: If the migration needs to happen in stages (e.g., first master data, then transactions), SmartConnect allows you to run these processes in sequence or on a schedule.

8. Validation and Error Handling

Validation:

After the migration, validate the data in the destination tenant. Check that all records (customers, vendors, transactions) have been successfully imported.

Use reports or queries in the destination tenant to compare the migrated data with the source data.


Error Handling:

If any errors occur during the migration, SmartConnect will provide error logs and notifications.

Review these logs, resolve issues (e.g., missing fields, data mismatches), and re-run the affected maps.



9. Post-Migration Adjustments

Once the data is successfully migrated, perform any post-migration cleanups or manual adjustments that might be required in the destination tenant.

Re-create workflows or customizations that were in the source tenant, as these will not be automatically transferred during data migration.



---

Key Features of SmartConnect for BC Data Migration:

1. Pre-built Connectors: Direct integration with Dynamics 365 Business Central makes the setup process easier.


2. Complex Data Handling: Ability to handle complex data migrations, including relationships between entities.


3. Transformations: Built-in transformations to manipulate data as needed during migration.


4. Error Logging: Built-in logging and error reporting to ensure successful migration.


5. Scheduling: Ability to automate or schedule migration tasks.



Limitations:

Customization and Extensions: You will still need to manually transfer any customizations, extensions, or permissions not covered by the data migration.

Setup Required: Although SmartConnect simplifies data migration, setting up the maps and transformations requires knowledge of the data structure and SmartConnect itself.


Conclusion:

eOne’s SmartConnect provides a robust solution for migrating data between two Dynamics 365 BC SaaS tenants. By leveraging SmartConnect’s connectors, data mapping capabilities, and transformation tools, you can extract, transform, and load data into a new tenant efficiently. This method allows for greater control over the migration process compared to manual methods like Jet Reports or RapidStart Services.

TallyHo

How to do this with cosmo consult?

Cosmo Consult offers several solutions for migrating data between Dynamics 365 Business Central (BC) environments. While they have different products and services, one of their main tools for data migration is the Cosmo Data Integration Framework (DIF). This tool is built to help companies move data between Business Central environments, automate data import/export, and manage data transformations.

Here's how you can perform data migration between two Dynamics 365 BC SaaS tenants using Cosmo Consult’s Data Integration Framework (DIF) or similar migration tools from Cosmo Consult.

Steps for Using Cosmo Data Integration Framework (DIF) for Data Migration:


---

1. Set Up the Cosmo Data Integration Framework (DIF)

Install DIF: Ensure the Cosmo Data Integration Framework is installed in both the source and destination tenants of Dynamics 365 Business Central. DIF works as an extension for BC and helps integrate external data sources.

Connect to Source and Destination Tenants:

In DIF, configure connections to both your source tenant (the tenant from which you're exporting data) and your destination tenant (the tenant where you'll import data).

DIF supports connections through BC web services, APIs, and other data sources like XML, CSV, Excel, etc.



2. Identify and Define Data to Migrate

Master Data: Define the master data entities you want to migrate (e.g., customers, vendors, items, chart of accounts).

Transactional Data: Define which transactional data needs to be migrated, such as sales invoices, purchase orders, or ledger entries.

Configuration/Setup Data: Identify any additional configuration or setup data like dimensions, posting groups, etc.


3. Create Data Mappings in DIF

Source and Target Mappings:

In DIF, create mappings for each data entity that needs to be migrated. A mapping defines the source data fields and their corresponding target data fields.

The source fields will be drawn from the source tenant’s tables (for example, Customer, Item, or Sales Invoice tables), and you will map these fields to their counterparts in the destination tenant.



Example Mapping:

Customer Data: Map fields from the Customer table in the source tenant (Customer No., Name, Address, etc.) to the corresponding Customer table in the destination tenant.

Transformations: If necessary, use DIF’s transformation capabilities to adjust data during the migration. For instance:

Data type transformations (e.g., converting a string to an integer).

Data formatting (e.g., adjusting date formats or renaming certain fields).

Filtering: DIF allows you to filter the data before migrating, such as excluding inactive customers or certain historical transactions.



4. Data Export from Source Tenant

Extract Data from Source Tenant:

Once mappings are created, use DIF to extract the data from the source BC tenant. You can export data directly from BC web services or APIs into a variety of formats like Excel, XML, CSV, or a direct-to-BC web service integration.

The exported data is typically stored in staging tables or exported files that can then be reviewed and validated before being imported into the destination tenant.



Export Example:

Export the customer master data, sales orders, or ledger entries as CSV or Excel files if you're using a file-based export, or directly map the data via web services if the source tenant is directly connected.


5. Prepare Data for Import

Data Cleanup and Transformation:

Review the extracted data and clean it if necessary. You may need to format certain fields, remove any unnecessary data, or perform additional transformations to ensure the data matches the target structure of the destination tenant.

DIF provides data transformation rules and validation mechanisms to ensure that the data adheres to the destination tenant’s format.



6. Data Import to Destination Tenant

Create Import Mappings:

In the destination tenant, create import mappings in DIF that match the source tenant’s data fields with the appropriate target tables.

If you're importing data directly from files (e.g., CSV or Excel), map the columns in the file to the corresponding fields in the destination tenant's tables.

If you're using direct web service connections between the two tenants, ensure that the source data is flowing correctly into the destination tenant.



Import Example:

For importing customer data, map the fields like Customer ID, Name, Payment Terms, etc., from the exported file or the source system directly to the destination tenant's Customer table.


7. Perform the Data Migration

Run the Data Migration:

Once the mappings are set up and the data has been cleaned and prepared, execute the data import into the destination tenant using DIF.

DIF can handle both one-time migrations (all data at once) or incremental migrations (data transferred over multiple sessions).



Scheduling:

If you need to run the migration at specific times, DIF supports scheduling the migration processes. This can be useful if you need to migrate the data during off-hours or want to break it up into smaller batches.


8. Validation and Error Handling

Validation:

After the data migration is complete, validate the imported data in the destination tenant to ensure accuracy. This includes checking master data (e.g., customers, vendors) and transactional data (e.g., sales orders, invoices).

Run validation reports or queries to cross-check the data migrated from the source tenant.


Error Logs and Resolution:

DIF provides detailed logs for any errors or issues encountered during migration (e.g., missing fields, duplicate entries).

Review these logs, fix the identified issues, and re-run the failed import jobs.



9. Post-Migration Adjustments

Post-Migration Cleanup:

After the migration, perform any additional tasks like recreating workflows, adjusting user roles, and configuring system settings in the destination tenant that were not migrated.

Ensure that all references (such as relationships between entities) are intact in the destination system.




---

Key Features of Cosmo Data Integration Framework (DIF) for Data Migration:

1. Flexible Data Sources: Supports multiple data formats (e.g., CSV, XML, Excel) and direct integrations with Business Central web services or APIs.


2. Data Transformation: Built-in transformation capabilities to adjust the data format, clean it, and ensure compatibility with the destination environment.


3. Error Handling: Detailed error logging and validation options help resolve issues during migration.


4. Incremental Migration: Ability to schedule and perform migrations in phases or handle ongoing data integration scenarios.


5. Data Mapping: Powerful data mapping features allow precise control over how source data is transferred to the target environment.



Limitations:

Complex Setup for Large Migrations: Depending on the volume of data and complexity of relationships between data entities, setting up the mappings and transformations in DIF might require time and expertise.

Customizations and Extensions: Like other tools, DIF does not migrate customizations, extensions, or user settings — you will need to handle those separately.


Conclusion:

Cosmo Consult's Data Integration Framework (DIF) is a powerful and flexible tool for migrating data between Dynamics 365 Business Central tenants. It simplifies data migration by providing direct connections to BC web services, built-in data transformation, and scheduling capabilities. DIF is ideal for handling complex data migrations, especially when you need to map and transform large datasets. While setup may require some expertise, the tool provides a comprehensive solution for moving data between BC environments.

TallyHo

Sorry, I will not make a habit of this. But ChatGPT's answers are quite impressive! A service level you will never find the 'old' way.

julkifli33

hi @TallyHo thanks for your answer
actually i am doing method 2.
export Prod 1 to BacPac.
restore it to SQL Server
and then Cloud Migration to Prod 2.

thanks by the way