Cleaning the client database in SIMLA CRM: phones, duplicates, cities

Budget: 15000 UAH Deadline: 5 days

Good day, Arthur!

I am ready to perform an audit and phased cleaning of the client database in SIMLA CRM via API v5.

In the first phase:

— I will analyze the structure of the database, duplicates, phone numbers, and cities;
— I will check the limits and capabilities of the API;
— I will generate a dry-run report without making changes;
— I will determine the rules for merging cards while preserving orders, correspondence, tags, and custom fields;
— I will prepare a list of risks, timelines, and an accurate estimate for the main phase.

After approval, I will implement:

— formatting phone numbers to the format +380XXXXXXXXX;
— splitting cards with multiple numbers;
— merging duplicates according to the rule "one number — one ID";
— normalizing cities through the official directory;
— a detailed log of all operations;
— a backup, the ability to roll back, and reprocessing of errors;
— automatic verification of new entries at the input.

I will not perform irreversible changes without prior approval. First, a dry-run, report, and approval of the list of operations.

The cost of the first phase is 15,000 UAH.
Timeline — up to 5 working days.

The main cleaning and background automation will be estimated separately after the audit and clarification of the actual volume of the database. Expand

Budget: 8500 UAH Deadline: 8 days

Good day.

I will conduct an audit of the database, prepare a report with problematic entries, and agree on all changes before execution. I will write a separate script in Node.js for working with the SIMLA API, which automates data standardization, merges duplicates, and protects the database from re-contamination. The cost of the audit is 1500 UAH, and the execution time is 1 day. The estimated time for all work is 7 days, with a cost of 7000 UAH. I am ready to discuss the details and start working. I would be happy to collaborate.

Budget: 8000 UAH Deadline: 7 days

Good day. I have done deduplication of databases through the RetailCRM/SIMLA API, I know the specifics of merging cards and request limits. I will start with an audit and a dry-run report, without making changes to the live database without your OK — we will do it for 8000/7 days. For the city directory, do you use the Nova Poshta API or KATOHTG?

Budget: 7600 UAH Deadline: 3 days

Good day, I have over 5 years of experience in development, having worked extensively with CRM automation and client data processing.

I will conduct an audit of the database and create scripts for normalizing phone numbers, cities, and merging duplicates with logs and a dry-run for approval - just as you described.

I estimate the first stage of the audit will take up to 3 days, and then it will proceed step by step. I will provide the exact cost after a few clarifications or in private messages.

Which version of the SIMLA/CRM API should be used, and is there a test database for checking the dry-run?

I look forward to your message in private!

Budget: 8000 UAH Deadline: 3 days

Hello, Arthur!

We are the Business Atlas team, this is a routine technical job for us: data extraction via API, normalization of phone numbers and cities, merging duplicates while preserving history.

Before merging, we will provide a CSV with the mapping "which card corresponds to which," you confirm, and only after that do we apply it. Unrecognized numbers will not be touched; they will be listed separately.

Just tell us one thing: do you have clients who legally share one number (wholesale, corporate, families)? This will determine whether we can implement the "one number = one client" rule throughout.

Budget: 8000 UAH Deadline: 7 days

😀 Hello! I have practical experience in developing Python scripts for integration with REST API CRM systems, data cleansing, normalization, and deduplication.

🛠 Here's how I will do it:
1. I will conduct an audit of the database via the SIMLA API (v5) and generate a detailed dry-run report with statistics before making any changes.
2. I will standardize phone numbers (+380...) and link localities and regions through the Nova Poshta / KATOHTG API with full logging.
3. I will perform deduplication while preserving order history, tags, and fields, and I will set up background checks for new records.

🎥 Portfolio: Freelancehunt

I am ready to discuss the details and start with the first stage of the audit!

Budget: 8000 UAH Deadline: 3 days

Hello, Arthur. After the selection, I will immediately start the first stage: auditing the database and a dry run without any live changes. For 8000 UAH and 3 days, I will prepare the audit structure and a control sample of anomalies on the first day. I work with Python, SQL, and API integrations for verifying data normalization. In the report, I will show issues with cards, phones, duplicates, and variations in city names, and I will add a list of planned changes and a safe rollback scheme. We will evaluate the live merge and ongoing monitoring of new data separately after the audit.

Budget: 12000 UAH Deadline: 3 days

In terms of lines and cost - the first stage of the audit is 3 working days, 12,000 UAH. A complete cleanup and protection against re-contamination should be accurately assessed after the audit, approximately another 7-12 working days depending on the number of cards and merging rules.

In SIMLA / RetailCRM v5, I would go through a managed scenario - full export, normalization in a separate change table, dry-run, report approval, then batch update via API with an operation log and rollback capability. For phone numbers - only unambiguous formatting to +380XXXXXXXXX, for disputed records - a separate list. For cities - the New Post or KATOHTG directory, but it needs to be agreed upon which is the main source.

Questions for accurate assessment
> how many customer cards and numbers are approximately in the database
> does SIMLA already have access to the API and the right to merge customer cards

Similar works by Ingello
> https://business.ingello.com/forma-crm - CRM and business logic with roles, data, and processes
> https://business.ingello.com/forma-bpm - process automation, change control, and operational stability
> https://systems-fl.ingello.com/ua - Ingello Systems profile for FLH

An important point - I would not do this as a manual cleanup for 8,000 UAH, as the risk of ruining the order history is more expensive than the work itself. First, an audit and dry-run, then a live launch. A penny-wise person pays twice - this saying is very technical here =) Expand

Budget: 8000 UAH Deadline: 7 days

Hello, I did a similar database cleanup in RetailCRM/SIMLA v5: exporting cards via API, standardizing phone numbers to +380XXXXXXXXX, merging duplicates by the rule one number = one ID, while preserving order history, tags, and custom fields. I pulled city normalization through the Nova Poshta API with region autofill, so one filter would extract the entire region.

If you have many orders from the website forms, it's worth implementing phone validation and city suggestions at the input stage; this reduces the re-pollution of the database by about 60-70%.

How many cards are currently in the database, and is there access to a test SIMLA account for a dry run? And where do new entries come from, besides the website forms, are there external integrations?

I suggest we get in touch; I will also outline a normalization scheme and a dry run plan with a report on the planned changes for your database. I will clarify the timelines and costs after the audit.

Budget: 7900 UAH Deadline: 3 days

Worked with RetailCRM/SIMLA v5 API - exporting cards in batches considering request limits, updating and merging through customers/merge. I will start with an audit: how many cards, how many phone numbers out of format, how many duplicates by number, and how many unique city names - based on the results, I will provide a refined estimate for the remaining stages. I will format phone numbers to +380XXXXXXXXX using libphonenumber, and unrecognized ones will be listed separately without guessing; cities and regions will be based on the KATOOTG directory with verification through the Nova Poshta API, the region will always be filled. All changes will only be made after a complete backup and dry-run with a report for approval, each operation will be logged with the possibility of rollback. Additionally, I will normalize phone numbers and cities at the input and perform a background check on new entries to prevent the database from getting cluttered again.

Budget: 8000 UAH Deadline: 2 days

Hello, Arthur!

I will start with a separate audit of the CRM without changes to the database. I will export customer cards via API and prepare a report on the number of incorrect phone numbers, duplicates, unique city names, cards with a large number of numbers, and ambiguous matches.

The cost of the audit is 1000 UAH. The timeframe is up to 3 working days after receiving access. Based on the results, I will provide an accurate estimate for cleaning the database.

Budget: 7600 UAH Deadline: 2 days

Chat with Gemini
Reply!

Solution: Ready to execute the project on working with the SIMLA / RetailCRM (v5) API, deduplicating client cards according to the rule "1 phone number — 1 ID" while preserving history and normalizing Ukrainian address directories (Nova Poshta / KATOHTG). I will implement a full backup before changes, a dry-run mode with a report for approval, logging of all operations, and protection against re-contamination.

2 days because I have some groundwork.

Budget: 10000 UAH Deadline: 10 days

Good day. I am interested in your project.
I will be able to provide the exact cost and timeline after reviewing the examples and discussing all the details.

Feel free to write, I would be happy to collaborate! 🤝

======= Why choose me =======

✅ Extensive practical experience working with websites, marketplaces, and AI tools.
✅ Detail-oriented, results-driven, meet deadlines, and always available.
✅ If necessary, I offer better solutions if I see an opportunity to make the project more efficient.

======= Work Experience =======

🔹 CMS and builders: WordPress (Elementor, WooCommerce, ACF, Carbon Fields, Gutenberg, Bricks, UX Builder, WPBakery), OpenCart, ocStore, ModX, OkayCMS, Shopify, Webflow, Framer, Bubble.io, Wix, Weblium, Joomla, Magento, Drupal, PrestaShop, Bitrix, Khoroshop.
🔹 Marketplaces: Prom.ua, Rozetka (Pricecreator), OLX, Bigl, Etsy, AutoRIA, Avtobazar, RST, Besplatka, Kidstaff, Klubok, and others.
🔹 AI: ChatGPT, Gemini, Midjourney, Nano Banana, Leonardo AI, and others.
🔹 Tools: Google Workspace, Microsoft Office, FTP, hosting, RDP.
🔹 Graphics and multimedia: Photoshop, Lightroom, Premiere Pro, After Effects, Audition, Figma, FL Studio, Ableton.
🔹 Additionally: HTML, CSS, JavaScript, PHP, MySQL, basic and technical SEO, CRM.

⭐ Reviews: Freelancehunt
📁 Portfolio — I will provide in private messages. Expand

Budget: 10000 UAH Deadline: 3 days

Good day! The approach completely aligns with yours: only dry-run → approval → execution, full backup, operation log with rollback, nothing is deleted irreversibly.

Stage 1 (audit): 3,000 UAH, 2–3 days. I will export the database via API v5 (considering limits), report: number of cards, numbers out of format, duplicated IDs, unique city spellings, "hanging" cards. Based on the results — an accurate estimate for stages 2–6.

In essence: phones — normalization to +380 with unidentified ones listed separately (no guessing); cities — mapping to KATOOTG/reference NP (I have worked with them); merging — one number = one client, history/email/tags/custom fields are preserved. Entry protection — webhook validation of new records + background check.

Honestly: I won't show the SIMLA case, profile — data processing and deduplication for e-commerce (filling and importing catalogs for Rozetka). I have studied API v5, I know the limitations.

The estimate for the full scope after the audit is 10,000–15,000 UAH depending on the size of the database.

Budget: 8000 UAH Deadline: 14 days

Your database in SIMLA has been compiled from various sources, so the phone numbers are recorded differently, one client exists under several IDs, and the cities and regions are filled unevenly. Because of this, the database is poorly segmented. I will start with a separate audit: how many cards, how many numbers are out of format, how many duplicates, and how many different spellings of cities. Based on these figures, I will clarify the estimate for the remaining work. Next, I will bring the phone numbers to the format +380XXXXXXXXX, questionable ones will be listed separately without guessing, I will merge duplicates by the rule of one number per client while preserving the order history, email, addresses, and tags. I will normalize cities and regions according to the Ukrainian directory, and at the input, I will add a check for new entries. I will work through a full backup, a dry run with a report for approval, and a log with rollback. I am ready to take on this work.

Budget: 8000 UAH Deadline: 2 days

Hello!
I have 2+ years of experience, including with various CRMs. The task is clear, I would be happy to discuss the details.
Timeline: from 7 days for all stages.
The cost depends on the amount of data and how dirty it is. Initially, from 16,000 for all stages. I set the rate according to the first stage.
Write to me, I will complete it quickly and efficiently!

Budget: 8000 UAH Deadline: 3 days

We have an almost ready solution for cleaning and normalizing client databases in CRM, which can be quickly adapted for SIMLA / RetailCRM v5 and launched with a dry-run before changes in the production database.
I’m available to discuss the details right now within the marketplace.

Regarding timelines and costs:
The first stage of the audit is 8000 UAH and 2-3 working days after access is granted.
After the audit, we will provide an accurate estimate for merging duplicates, normalizing cities, regions, background checks, and protection against re-contamination.

I see an important nuance - you cannot just clean the table and go have coffee, as a controlled procedure is needed:
- full backup
- data export via API considering limits
- dry-run with a report on each planned change
- a separate list of ambiguous phone numbers and cities
- merging by the rule one number - one client ID
- preserving order history, emails, addresses, tags, and custom fields
- operation log and rollback capability

For cities, I would suggest normalization using the Nova Poshta directory or KATOOTG, and for the entry of new data - verification at the level of forms, integrations, and background tasks.
A little automation with AI is appropriate here - not for making irreversible decisions, but for highlighting suspicious matches and cards with multiple numbers where human verification is needed.

Please clarify:
- approximately how many client cards are currently in SIMLA CRM
- is merging cards via API available in your plan, or does this need to be checked during the audit?

Relevant examples:
- https://business.ingello.com/forma-crm - CRM and business processes with roles, data, and operational logic
- https://business.ingello.com/forma-bpm - process automation and change control in the system
- https://business.ingello.com/iks - corporate accounting system where data quality and controlled logic are important

Main page of Ingello Systems for Freelancehunt:
https://systems-fl.ingello.com/ua Expand

Budget: 8000 UAH Deadline: 5 days

Good day, Arthur!

The technical specification is written correctly — a separate audit as the first step and the rule "do not guess unrecognized numbers" save a lot of nerves later.

One point I want to mention right away: merging duplicates in the live CRM is irreversible. If the rule "one number = one client" merges two different people who once shared a number, it will not be possible to roll this back in SIMLA. Therefore, I suggest working like this: first, I will provide the mapping "which card merges with which" in CSV for your approval, and only after your "okay" will I apply the changes via API.

I will not do the cities and regions manually, but by cross-referencing with the KATOHTG directory — then the region will be automatically pulled from the city, and different spellings in both languages will be consolidated into one record.

The audit costs 1200 UAH, one day. Based on its results, I will name the exact price for the remaining work, approximately 7–9 thousand depending on the volume.

Please tell me, how many cards are approximately in the database? Five thousand and two hundred thousand are different timelines.

Python, working with API and databases: github.com/kamedashe

Bogdan Expand

Budget: 8000 UAH Deadline: 5 days

Arthur, it seems you have accumulated quite a bit of technical debt in SIMLA, which is currently hindering marketing and accurate analytics. The main issue here is not just to remove duplicates, but to maintain the integrity of the order history when merging cards and to normalize the data to logistics standards.

I suggest starting with an audit to see the actual scale of the database and the number of critical errors. After that, I will prepare a script to standardize phone numbers into a single format, merge cards according to the rule you specify, and map cities through the Nova Poshta API for further convenient segmentation.

How many clients do you currently have in the database, and are there any cards among them without any specified phone numbers that need to be processed separately?