Odoo Migration from Community V12 to Enterprise V17

398.0 EUR

398.0 EUR peopleperhour Technology & Programming Overseas
80 days ago

Description

Odoo Migration from Community Version 12 to Enterprise Version 17: A migration of all data from an existing ten user instance of Odoo Community version 12 to Odoo Enterprise version 17 is required. The migration must include all data such as production records, inventory traces, serial numbers, as well as any files attached to documents. A complete transfer of all information is absolutely essential as the instance contains sensitive healthcare data and functions as an integral all-in-one system. Any missing or lost data during migration is unacceptable. Extensive experience with Odoo's lower-level programming architecture is necessary to properly perform the migration. The ideal candidate will be an independent freelancer able to meticulously migrate every piece of data from one version to the next to ensure uninterrupted use of the fully functional system.
We hope to see your proposals for this project.
It’s absolutely mandatory for accepting the work to check before the viability of the server for upgrade it.
Last worker makes me to lose 1 month, before post a offer be absolutely sure that you will be able to do in terms offered.

关注公众号,不定期副业成功案例分享
Follow WeChat

Success story sharing

Want to stay one step ahead of the latest teleworks?

Subscribe Now

Similar Teleworks

OBJECTIVE: Develop a Python script for the Zapier Code Module to dynamically generate and output an HTML template using provided input variables. The script must be robust, handling missing or malformed data gracefully. REQURIEMENTS: Input Variables: - Dynamic variables provided as comma-separated strings: {Meta_Data_Artist_Name} (e.g., "Artist A,Artist B") {Meta_Data_Artist_Image_Url} (e.g., "https://example.com/a.jpg,https://example.com/b.jpg") {Meta_Data_Artist_Thank_You_Msg} (e.g., "|||Thank you for your support|||,|||We appreciate your kindness|||,|||Grateful for you|||") {Meta_Data_Artist_Slug} (e.g., "artist-a,artist-b") - Variables are aligned by index: the first entry corresponds to the first artist, the second to the second artist, and so on. - Duplicate entries may exist where multiple products by the same artist are bought. Duplicate entries should be handled to ignore so that only unique HTML blocks for unique artists within the input strings are ajoined and output. HTML Output: - Generate one HTML block for each unique artist. - Join the HTML blocks into a single output for all artists. - For {Meta_Data_Artist_Thank_You_Msg}, use only the content enclosed by ||| ignoring other commas which might otherwise cause a conflict. Name Parsing: - Parse the artist's name from {Meta_Data_Artist_Name} as follows: - If the name contains more than one word, use only the first word. - If the name is a single word, use that word. - Capitalize the first letter of the word (e.g., "john smith" becomes "John"). Error Handling: - If any error occurs (e.g., malformed input or missing data); - Output a fallback HTML block (attached) - Log a meaningful error message in a separate defined output. - Handle missing inputs or null values gracefully. - Trim whitespace and sanitize special characters in the input strings to avoid unintended behaviour or injection attacks. Zapier Integration: - Ensure output is compatible with Zapier’s requirements (e.g., JSON structure like {"html": "", "error": ""}), and output requirements. - Confirm multi-line output compatibility. - Optimised code to reduce errors, conflicts and ease of debugging. Familiarity with Zapier preferred. Flexibility in solution allowed to meet the desired outcome. Acceptance of follow-up changes or troubleshooting is key.
12.0 GBP Technology & Programming peopleperhour Overseas
1 days ago