| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
| Lines of code | 1227 |
| Technical Name |
us_website_migration |
| License | OPL-1 |
| Website | https://unitsoft.com.ua/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Website (website)
• Discuss (mail) |
| Lines of code | 1227 |
| Technical Name |
us_website_migration |
| License | OPL-1 |
| Website | https://unitsoft.com.ua/ |
Website Page Migration
A convenient and fast way to import content of website pages, blog posts and product pages from other Odoo databases
Key Features
Multiple Page Types
Import content from website pages, blog posts, and product pages. Make the process of importing pages simple.
Cross-Version Compatibility
Import pages from different Odoo versions (16, 17, 18). Seamlessly migrate content regardless of version differences between source and target systems.
Multi-language Import
Import pages with all their translations intact. Preserve multilingual content and maintain language consistency across different Odoo databases.
SEO Optimization Transfer
Keep your SEO settings when migrating pages. Import meta titles, descriptions, keywords and all SEO configurations to maintain search rankings.
How to Use - Simple 3-Step Process
Step 1
Connect to Source Database
Configure XML-RPC connection to your source Odoo database. Enter the server URL, database name, username, and API Key to establish secure connection.
Step 2
Select Content Types
Choose which types of pages to import: Website Pages, Blog Posts, or Product Pages. Configure filters and selection criteria for targeted migration.
Step 3
Import to Current Database
Execute the import process. All selected pages will be transferred with their content, translations, SEO settings, and media files preserved.
Example Of Importing A Website Page
Module Configuration Guide
1. Module Activation
After installing the module, navigate to Apps menu and search for "Website Page Migration". Click Activate to activate the module in your Odoo instance.
2. Accessing the Migration Tool
Once installed, you can access the migration tool through:
- Website → Configuration → Website Migration
After opening the Website Migration menu, a list of connected databases will be displayed. If the module has just been installed, the list will be empty, so you can immediately click the New button in the upper left corner of the screen to create a new entry
3. Database Connection Settings
In the newly created form, let's take a closer look at the part called Connection Settings.
The base URL of the remote Odoo instance you want to connect to. It should include the protocol (http or https) and the domain. Example: https://example.odoo.com
The name of the database in the remote Odoo instance. You can find it in the upper right corner of the screen by turning on developer mode or in the Odoo configuration file (odoo.conf).
The username of a user with access to the remote database. Make sure the user has sufficient rights to read the needed models. Usually, this is the user's email address that you specify when logging into the database. Example: admin@example.com
The API Key or password of the remote user. To create a new API key, go to: Preferences → Account Security → New API Key. Alternatively, you can use a user password, but we strongly recommend working through an API key for better protection of user data.
4. Source Database Settings
Let's fill in the part for configuring Source Database Settings. There are two important fields here, the Page Type field is a drop-down list with a choice of the type of page we want to load into our database and the Page Domain field, which allows you to specify the specific pages you want to get from the source database.
Page Types:
Import static website pages.
Import blog posts with categories, tags, and the blog to which the post belongs.
Imports the product description on the page. Please note that we do not create products in the current database during import, but find product variants that have the same Internal Reference field in both databases.
The domain allows you to retrieve specific pages from the source database based on the criteria you define. Within the domain, you can choose which fields to use for identifying the page. For example, for a Website Page, the most suitable field is Page URL; for a Blog Page, it's the Title field; and for Product Pages, it's the Name field. Of course, other fields can also be used depending on your needs.
In the next sections, we'll show you how to set up automatic page imports from another database to run once a day. In this case, pages will be retrieved using the specified domain. That's why it's important to configure this field correctly if you plan to use the Scheduled Import option.
5. Destination Database Settings
We have almost completely set up the import of pages, so let's take a look at some of the remaining settings.
Specify the website in the current database to which the imported pages will belong.
This option automatically imports pages once a day for the specified domain. Please note that if this option is enabled and the Page Domain field is empty, all pages from the source base will be automatically imported.
6. Starting the Import Process
To start importing pages, click the Import Pages button in the upper corner of the form where we made all the settings. A window should appear with a list of pages that have been found for the specified domain in the source database.
At this stage, you can remove unnecessary pages and leave the ones you want to import, then click the Import Pages button. After that, the pages will be imported in the background.
After the import is complete, you may see a pop-up notification with the number of pages created or updated. After that, you can see the imported pages in your database.
Product Page Import
When importing Product Pages, it's important to understand that we do not create new products in the current database during import. Instead, we find product variants that have the same Internal Reference field in both databases and import the page description content.
The system searches for products in your current database that have the same Internal Reference as products in the source database. If a match is found, only the page content (description, images, blocks) is imported.
7. Some Important Information
In some cases, elements on pages may look different, let's figure out why this may happen:
The Odoo system can identify blocks that have been migrated from databases that have a different version of Odoo. In this case, a message will be displayed with two options to choose from. In the first case, replace with a new block, in which case the data of this block will be lost, or leave the current block. This usually applies to blocks with complex designs or major changes from the previous version. For most simple blocks, you won't be asked to make any changes.
In the Theme section, you can set up colors, buttons, indents, and styles that will be used for all pages of the site. When importing a page, we transfer only the content that is relevant to this page, but do not transfer the theme settings so as not to change all the other pages that are already in your database. Due to the difference in theme settings, the appearance of some elements of the imported page may differ from this page in the source database.
If you're importing pages that include dynamic blocks like Products or Blogs, and those blocks appear empty after import, open the page in edit mode, click on the empty area where the block should be, and check whether all the fields are filled in correctly. These blocks often won't display if they're not configured properly. For example, the block with products is not displayed in the picture because the Filter field was empty.
Support
We provide free bug fixes and updates for all our modules for 1 year after purchase.
The warranty is for a clean installation of Odoo.
If you need help, please submit a request through our Support Portal at https://unitsoft.com.ua/support. Our support team, which consists of the developers who created the product, is always ready to help you.
We will not provide support (for free) if our modules do not work on your server or conflict with other modules.
We are ready to consider your requests regarding the functionality of our modules, and if they prove useful, we can take them into account when releasing new versions.
We also provide all types of Odoo support services, such as installing Odoo on your server, maintaining your Odoo server, custom development.
We invite you to familiarize yourself with our support packages here: https://unitsoft.com.ua/services-plan
Our Odoo Apps
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module