Connected as the wrong Salesforce user
Cloudingo filters only see fields the connected user can edit. Connect with a profile that lacks field permissions and the fields you need to match on simply do not appear.
Salesforce · Cloudingo Implementation
Cloudingo implementation services that merge safely from day one
A Cloudingo implementation connects Cloudingo to your Salesforce org and sets it up to find, merge and prevent duplicates on a schedule your team controls: the right plan for your objects, a connected user with the right permissions, filters and merge rules your data owners agreed, a tested pilot, and automation that runs without anyone babysitting it. Twopir Consulting assesses, configures, tests and hands it over. Reports before merges, and merges before automation.
12+
500+
250+
40+
Trusted by 500+ organizations — including sales, marketing and service teams that depend on one clean customer record in Salesforce.
What We Implement
- Salesforce Partner
- Dedupe Filters
- Merge Rules
- Automation Jobs
- Real-Time Merge
- Rapid Import
- Undo & Restore
- Cloudingo Intelligence
Most bad merges are configured before the first run
Connecting Cloudingo to Salesforce is quick. The problems that show up later, such as a contact merged into the wrong account, a field nobody can match on or a nightly job that quietly stopped, were almost always set during setup. These are the six we see most often.
Plan bought before the scope was known
Merging Opportunities, Cases or custom objects needs the Professional or Enterprise plan, and so does real-time merge. Teams that license first find the gap when the object they most needed is out of reach.
Fuzzy filters switched on first
Cloudingo's own guidance is to start with tight exact-match filters and loosen gradually. Starting loose produces duplicate groups that are not duplicates, and once merged, they are a clean-up job of their own.
Default merge rules left in place
Every object ships with a default rule for the master record and field values. Nobody asked sales, marketing or finance which record should survive, so the oldest record wins and the newest phone number is lost.
Org automation never tested against a merge
Merges run through your triggers, flows and validation rules, and Salesforce limits apply. Cloudingo states it cannot troubleshoot customer automation, so a merge that fails on your validation rule is yours to solve.
Automation scheduled with no owner
A daily job keeps running after the person who built it leaves. Filters drift from how the business defines a duplicate, skipped groups pile up, and nobody reads the job results until a rep complains.
Definition
Cloudingo implementation, defined
A Cloudingo implementation is the project that connects Cloudingo, a deduplication and data-management application for Salesforce, to your org and configures it to find, merge and prevent duplicate records in a way your team can run and trust. It covers assessing the Salesforce environment, choosing the Cloudingo plan, installing and connecting it, setting users and permissions, configuring filters and merge rules, testing merges against your org's automation, scheduling automation jobs, and handing the whole setup over with a runbook.
Three parties are involved, and it helps to keep them apart. Cloudingo, published by Symphonic Source, licenses the product, supports it and runs in the cloud, outside Salesforce: it connects to your org over the Salesforce API through an OAuth connection and, by its own account, neither stores nor caches your data, with the exception of the backups behind Undo & Restore. Salesforce holds your records and applies its own limits, automation and permissions to every merge. Twopir Consulting does the implementation in between: the assessment, configuration, testing and handover on this page. Product behaviour is documented in the Cloudingo help centre.
Do you need a partner to set it up? An experienced admin can connect Cloudingo and run a template filter in an afternoon. Outside help earns its place when the decisions carry risk: several teams who disagree on which record should survive, custom objects in scope, heavy automation in the org, record volumes that change the plan, or imports and integrations that keep creating new duplicates. A merge is easy to start and slow to reverse at volume, so the rules deserve more care than the install.
New to the product? Our getting-started guide to Cloudingo walks through the basics. Still comparing tools? We also implement Duplicate Check for Salesforce, and we will tell you which fits your org.
Assess the org first, then choose the plan
Cloudingo's plans differ in which objects you can merge, how many people can log in, and whether merging can happen in real time. We map what your org needs against those gates before anything is bought or renewed, because the plan sets the ceiling for the whole implementation.
| What your implementation needs | What Cloudingo requires | Why we check it first |
|---|---|---|
| A supported Salesforce edition | Cloudingo works with Salesforce Professional, Enterprise, Unlimited and Performance editions. | It confirms the org can connect at all before anyone signs an order. |
| Leads, Contacts, Accounts and Person Accounts | Every plan. Standard covers these objects with mass merge, convert, update and delete, scheduled automation jobs and one user. | Most first implementations start here, and many never need more. |
| Opportunities, Cases, Campaign Members or custom objects | Professional (up to three objects) or Enterprise (unlimited). Cloudingo enables custom-object merging on request. | Cloudingo counts any object Salesforce cannot merge natively as a custom object, so this is the gate teams underestimate. |
| Real-time merge | Professional or Enterprise. One real-time filter per object, on Leads, Contacts, Accounts and Person Accounts only. | Real-time merging acts on records as they arrive, so it needs a filter you already trust. |
| Undo & Restore | Listed from the Professional plan. Backups are kept up to 45 days on Cloudingo storage, longer on your own AWS or Azure storage. | It is the safety net for the first large merge runs, and the storage location is a security decision. |
| Rapid Import and automated deduplicated imports | Professional or Enterprise. Standard includes the standard import. | Recurring list loads are where new duplicates come from after the backlog is cleared. |
| Incoming data checked through an API | Enterprise, which passes incoming data through your filters. | Integrations that create records need prevention at the source, not a nightly clean-up. |
| More than one person running Cloudingo | One user on Standard, three on Professional, eight on Enterprise, each with permission-based roles. | Who may merge, import or delete is part of the design, not an afterthought. |
| Large record volumes | Above 300,000 records across Leads, Contacts, Accounts, Person Accounts and custom objects, Cloudingo adds a charge per 100,000 records. | Record counts change the quote and the run times, so we count them in the assessment. |
What we configure in Cloudingo and Salesforce
Six workstreams run once the plan and design are agreed. Half of the work sits in Cloudingo; the other half sits in Salesforce, where permissions, automation and limits decide whether a merge goes through.
Connection, Users & Permissions
Cloudingo connected to the org through OAuth as a Salesforce user whose profile can see and edit every field you will match and merge on.
- Connected-user profile and field permissions
- Cloudingo seats and permission-based roles
- Connected-app access reviewed with your security team
- Cloudingo Intelligence alerts for logins and changes
- Undo backup storage location agreed
Dedupe Filters
The filters that decide what counts as a duplicate, starting from Cloudingo's templates and tightened to your data before anything merges.
- Template filters per object as the starting point
- Exact-match filters first, looser matching later
- Lead-to-contact and lead-to-account sets
- Naming and ownership for every filter
- Filter results reviewed as reports
Merge Rules & Field Rules
Which record survives and which values carry over, agreed with the people who own the data and written into Cloudingo's rules.
- Master-record rule per object
- Field-level rules for values that must win
- Field groups so addresses stay whole
- Owner mapping for inactive users and queues
- Related-record rules for custom objects
Automation & Scheduling
Automation jobs that run a whole filter daily, weekly or on demand, without anyone logged in, once the filter and its rules have proved themselves.
- Job schedule per filter and object
- Exceptions that stop specific records auto-merging
- Real-time merge where the plan includes it
- Automation preview reports before a job goes live
- A named owner who reads every job result
Imports & New-Record Prevention
The import route checks each CSV row against existing records, merges the matches and inserts only what is new, so a list load does not undo the clean-up.
- Import wizard setup for each object in scope
- Shared Rapid Import templates and import-only users
- Automated deduplicated imports where licensed
- API integration routing on Enterprise
- File handling: CSV, 10MB per file
Org Safety & Recovery
The Salesforce side of every merge: the automation it fires, the limits it hits and the way back if a group merged wrongly.
- Triggers, flows and validation rules reviewed
- Merge batches sized for Salesforce limits
- Pre-merge and post-merge reports kept
- Undo & Restore tested on a real group
- Your own backup kept separate from undo
Filters and merge rules are set up here to a first working standard. Designing matching logic, master-record strategy and cross-object merging in depth is its own project, covered by our Cloudingo Salesforce deduplication services.
Six phases from assessment to a running schedule
How long it takes depends on the objects in scope, the record volume and how much automation every merge has to pass through. We scope it after the assessment, once we have seen the org, rather than guessing before.
Environment Assessment
Salesforce edition, objects and record counts, the duplicate picture Cloudingo's dashboard shows, the automation that fires on merge, and who owns which data. Need a scored baseline first? Start with a Cloudingo Salesforce data quality audit.
DeliverableAssessment and object-by-object scope
Plan Fit & Design
The Cloudingo plan, seats and objects confirmed, then the merge order, master-record rules and field rules agreed with your data owners and written down.
DeliverablePlan recommendation and rule design
Install & Connect
The AppExchange package installed, the OAuth connection made as the right Salesforce user, Cloudingo roles assigned and the undo backup storage set.
DeliverableConnected, permissioned environment
Configure
Filters, merge rules, field groups, owner mapping, exceptions and import templates, built to the design and reviewed with the people who will live with the results.
DeliverableConfigured filters and rules, reviewed
Test & Pilot
Filters run as reports, pre-merge reports checked, a pilot group merged by hand and then in bulk, an undo tested, and org automation watched throughout.
DeliverableSigned-off pilot results
Schedule & Hand Over
Automation jobs scheduled, real-time merge switched on where licensed, then a runbook, admin training and a named owner for every job.
DeliverableRunning schedule, runbook, trained admins
How we prove a merge is safe before automation runs
Cloudingo filters behave like reports and change nothing until a merge is submitted, which makes careful testing cheap. We use that: every filter and rule is checked on real data before it is allowed to merge anything on a schedule.
| Test | What it has to prove |
|---|---|
| Filter results as a report | The duplicate groups match what your data owners call a duplicate, with no false matches in a reviewed sample. |
| Pre-merge report | The master record and every winning field value are the ones the rules intend, before a single record changes. |
| Field groups | Addresses and other grouped values come from one record, never a city from one and a postcode from another. |
| Related records | Notes, attachments and relationships stay with the master, and custom-object related records move, copy or stay as designed. |
| Org automation | Triggers, flows and validation rules let the merge through without errors or side effects, inside Salesforce limits. |
| Owner mapping | Records owned by inactive users or queues land with the right owner after the merge. |
| Undo & Restore | A merged pilot group can be unmerged and its related data reattached, where the plan includes it. |
| Import check | A sample CSV merges into existing records where it should and inserts only genuinely new ones. |
What changes the size of the project
The work grows with the number of objects, owners and automations a merge touches, not with the size of the duplicate count. These are the factors we scope in the assessment, and how each one changes the plan.
| Scope factor | Why it adds work | How we handle it |
|---|---|---|
| Standard objects only | The smallest setup: Leads, Contacts and Accounts, template filters tightened, default rules replaced. | Often the first phase, with merge order designed for the objects that come next. |
| Custom objects in scope | Each needs enabling, its own filters, and rules for what happens to its related records. | Confirmed against the plan in design, then piloted object by object. |
| Several teams owning the data | Sales, marketing and finance often want different records and values to survive. | Rules agreed in one working session per object and recorded with the reasoning. |
| Heavy org automation | Every merge runs triggers, flows and validation rules, and Salesforce limits apply. | Automation reviewed before the pilot, merge batches sized to stay inside limits. |
| Large record volumes | Longer runs, more groups to review, and pricing above 300,000 records. | Counted in the assessment so the quote and the run plan match. |
| Imports and integrations | New duplicates keep arriving through list loads or connected systems. | Import templates, deduplicated imports or API routing, depending on the plan. |
| An inherited Cloudingo setup | Existing filters, rules and jobs that nobody can explain still run. | Every filter, rule and schedule reviewed, kept, fixed or retired. |
| More than one Salesforce org | Cloudingo is priced per org, and rules have to stay consistent across them. | Rules shared to each connected environment through Cloudingo's rule library. |
Standardising values, filling gaps and clearing stale records is a cleansing programme rather than setup, and we scope it separately as Cloudingo data cleansing services. Not sure which rows apply to you? Bring your object list and record counts to the first call, and we will tell you.
Six starting points, six different plans
A first-time install and a rescue of an inherited setup use the same product and need very different projects. These are the situations we are most often brought into, and where each plan puts its effort.
First-Time Install
A new licence and a duplicate backlog nobody has measured yet.
- Focus
- Plan fit, the connected user, template filters tightened
- First merge
- One object, exact match, a pilot group by hand
- Automation
- A scheduled job once the pilot results hold
Inherited or Stalled Setup
Cloudingo is licensed and running, but nobody remembers why the filters look the way they do.
- Focus
- Every filter, rule and job reviewed against today's process
- First merge
- Only after the rules are re-agreed
- Automation
- Rescheduled, each job with a named owner
After a Migration or Merger
Two sources of the same customers landed in one org without being cleaned first.
- Focus
- Merge order across objects, accounts before people
- First merge
- The overlap between the two sources
- Automation
- Once the backlog is down to the daily trickle
Lead-Heavy Marketing Org
Events, forms and list buys keep creating leads for people who are already contacts.
- Focus
- Lead-to-contact and lead-to-account matching, bulk conversion
- First merge
- Leads against leads, then against contacts
- Automation
- Deduplicated imports and a recurring lead job
Duplicates From an Integration
A connected app or system creates a new record where it should update an existing one.
- Focus
- Fixing the source, then account filters
- First merge
- The account sprawl the integration left behind
- Automation
- Real-time merge or API routing, by plan
Custom Objects in Scope
Opportunities, Cases or your own objects carry duplicates that Salesforce cannot merge natively.
- Focus
- Plan confirmed, objects enabled, related-record rules set
- First merge
- One custom object, with its child records checked
- Automation
- Scheduled jobs per object; real-time is standard objects only
What your team runs after handover
A Cloudingo setup stays useful only if someone keeps it aligned with how the business works. The runbook we hand over covers these eight habits, each assigned to a named person on your team.
Read every job result
The Cloudingo dashboard shows duplicate counts, the last job runs and recent activity. A job nobody reads is a job nobody notices failing.
Work the skipped groups
Groups held back by an exception or left for review need a person on a set cadence, or they become the next backlog.
Change filters one step at a time
Loosen matching gradually and preview the results before the scheduled job picks up the change.
Keep owner mapping current
When people leave or queues change, update the mapping so merged records keep landing with an active owner.
Load lists through templates
Routine imports go through shared templates and import users, so every list is checked against existing records first.
Review roles and seats
Check who can merge, import or delete in Cloudingo, and that the connected Salesforce user still has the field access filters rely on.
Know the undo window
Undo backups last up to 45 days on Cloudingo storage and restore one group at a time. Cloudingo says undo is not a backup, so keep your own.
Retest after org changes
A new flow or validation rule can block merges. Retest the pilot group after major changes, and watch Cloudingo Intelligence alerts on permissions and system changes.
The product, its support and its own services
Cloudingo licenses and supports the application: self-service and email support on Standard, personalised onboarding on Professional, a dedicated customer success manager on Enterprise. It also sells its own data cleansing, migration and Salesforce org-split services.
Product questions and plan changes go to Cloudingo.
The Salesforce side, and the process around it
We work on the org Cloudingo connects to: its permissions, automation, limits and data owners, and the operating routine that keeps the setup aligned with the business.
For ownership, governance and an ongoing data-quality programme, see our Cloudingo Salesforce data quality consulting.
What a scheduled operation looks like in practice
Both customer stories below are published by Cloudingo, and the figures are Cloudingo's, not Twopir results. They are here because each one shows an implementation decision this page is about: how often to run, and what to merge first. Next to each, the lesson we build into our own plans.
Implementation Lesson
A daily schedule works when it is small, stable and owned. In this story the automation runs every day on a settled set of filters, and a person reviews what did not merge once a month. We put that review into the runbook at handover, with a name next to it.
Twopir Consulting Our reading of a customer story published by Cloudingo
Hotze Health & Wellness Center
Moved to Salesforce from Microsoft Dynamics without cleaning first, then put deduplication on a daily schedule.
Daily Cloudingo run cadence
~12 Filters in the daily run
Monthly Review of unmerged records
Implementation Lesson
Fix the source, then merge in order. Here an outside app created an account per transaction, so the plan cleaned accounts first, then leads, then contacts, then leads against contacts. Order matters because every merge changes what the next filter finds.
Twopir Consulting Our reading of a customer story published by Cloudingo
Docker, Inc.
Account duplicates created by a credit-card app, cleaned object by object in a set order.
60 Accounts found for one company
4 Clean-up steps in sequence
$50K–$1M Yearly cost of bad data, per the story
An implementation team that knows the whole org
Cloudingo decides which records look alike. Salesforce decides whether a merge goes through, and your teams decide which record is right. An implementation has to get all three working together.
We are Salesforce architects first
Every merge passes through the flows, triggers, validation rules and sharing in your org. We review those before the pilot rather than discovering them in a failed automation job.
Reports before merges, every time
Filters run as reports, pre-merge reports get read, a pilot merges by hand, and only then does anything run on a schedule. It is slower on day one and much faster than unpicking a bad run.
Your data owners set the rules
Which record survives and which values win are business decisions. We get sales, marketing and finance to agree them, then write the reasoning down so the next admin can follow it.
We size the plan to the scope
If Standard covers your objects, we say so. If custom objects or real-time merge are the point, we show you why before the licence is bought, not after the build has started.
We hand over what we build
You get documented filters, rules and schedules, a runbook and trained admins, not a setup only we understand. When you want us to stay, ongoing Salesforce support is a standing offer.
Cloudingo implementation questions, answered plainly
It depends on the objects in scope, the record volume and how much automation every merge has to pass through, so Twopir scopes it after the environment assessment rather than before. A setup limited to Leads, Contacts and Accounts in an org with light automation is the shortest. Custom objects, several teams agreeing merge rules, large record volumes, imports and integrations, or an inherited setup to review all add work.
An assessment of your Salesforce environment and the right Cloudingo plan, then installation and the OAuth connection, users and permissions, filters, merge rules, field groups, owner mapping and import templates. After that come testing and a pilot merge, an undo test, scheduled automation jobs, a runbook and admin training. Connecting Cloudingo is the smallest part of it.
It depends on what you need to merge and how. Standard covers Leads, Contacts, Accounts and Person Accounts with mass merge and scheduled automation for one user. Merging Opportunities, Cases, Campaign Members or custom objects needs Professional (up to three objects) or Enterprise (unlimited), as do real-time merge and Rapid Import. API integration is an Enterprise feature. Cloudingo publishes current plan details on its pricing page, and we confirm the fit during the assessment.
Yes, because the product is built for it. Cloudingo filters behave like reports and change nothing until a merge is submitted, pre-merge reports show which records will merge into which master, and Undo & Restore, from the Professional plan, can unmerge a group and reattach its related data. We pilot on a small group by hand before anything runs in bulk or on a schedule. Cloudingo's pricing FAQ addresses sandbox use; we confirm what your plan allows with Cloudingo during plan fit.
Merges made in Cloudingo can be reversed with Undo & Restore, which unmerges the records and reattaches related data. Backups are kept for up to 45 days on Cloudingo storage, or longer on your own AWS or Azure storage, and restores run one group at a time. Cloudingo states that undo is not a substitute for a backup, so we keep your own Salesforce backup in the plan.
Cloudingo runs in the cloud and connects to Salesforce through an OAuth connection over the API. It states that customer data is neither stored nor cached, with one exception: the backups behind Undo & Restore, which are kept on Cloudingo's U.S. servers by default or on storage you own. Cloudingo also lists SOC 2 Type II compliance and 256-bit SSL encryption, and we review the connection with your security team as part of setup.
They can. Every merge runs through the automation in your org and Salesforce limits apply, and Cloudingo states it cannot troubleshoot customer flows, triggers or validation rules. That is why we review that automation during the assessment, size merge batches to stay inside limits, and watch it through the pilot before anything is scheduled.
Next Step
Name the duplicates, we will plan the rest
A first conversation covers the objects you need to clean, rough record counts, the automation in your org and who owns the data: enough to say which Cloudingo plan fits and what the implementation would actually take. No obligation to proceed.
Talk to a Salesforce architect who implements Cloudingo
