Category: Salesforce

What a Salesforce implementation actually involves

Implementing Salesforce means configuring the platform around how your business sells, serves and reports: objects and fields, sales stages, approval rules, automation, security, integrations and dashboards. Licences give you access to the software; the implementation decides whether people actually use it.

For UAE companies the core work is the same as anywhere else, but a few local factors shape the design early. The most common ones are where customer data is stored, which data protection regime applies to your entity, bilingual users, and the number of legal entities and currencies you operate.

Step 1: Discovery and requirements

Discovery turns “we need a CRM” into a written scope. Run short workshops with each team that will use Salesforce, and document:

• The current sales or service process, step by step, including where spreadsheets and WhatsApp threads fill the gaps
• The decisions managers need to make each week and the reports that would support them
• The systems Salesforce must exchange data with, such as an ERP, website forms, telephony or marketing tools
• Who should see which records, by team, region or entity
• What success looks like after go-live, in measurable terms the business already tracks

The output is a prioritised backlog: what must be live on day one, and what can follow in later releases.

Step 2: Make the UAE-specific design decisions

Data residency and Hyperforce

Salesforce offers Hyperforce in the UAE, which lets eligible customers store their Salesforce data locally. Salesforce’s UAE Hyperforce page lists Sales Cloud, Service Cloud and other Customer 360 apps, and notes that not every service is available in every location. If local storage matters to your board, regulator or customers, confirm product availability for your specific licences before you sign.

Which data protection law applies

Mainland UAE companies fall under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL), which has applied since 2 January 2022. Companies in the DIFC and ADGM follow their own data protection regimes instead, and health and banking data have sector-specific rules. Your legal adviser should confirm which applies; the implementation team then reflects it in field-level security, consent tracking and retention rules.

Languages, currencies and entities

Many UAE teams work in English but serve customers in Arabic. Salesforce supports translated labels and multiple languages for users, and multi-currency for pricing and reporting in AED, USD, SAR or EUR. Decide early whether you need one org for all entities or separate business units with shared reporting, because this affects the data model and sharing rules.

Step 3: Solution design

Solution design maps each requirement to a Salesforce feature, standard where possible and custom only when it adds clear value. A good design document covers the data model, record types, page layouts, automation (built in Flow), integration approach, security model and reporting. Keeping to standard objects and features lowers your long-term maintenance cost and makes upgrades smoother.

Step 4: Build in iterations

Build in short cycles and show working screens to the business every one or two weeks. This catches misunderstandings while they are cheap to fix. Use a sandbox for build and a separate one for testing, and keep changes in version control so deployments to production are repeatable.

Step 5: Data migration

Data migration is often underestimated. Clean, deduplicate and map your accounts, contacts, opportunities and history before loading them, and run at least one full trial load in a sandbox. Our Salesforce data migration checklist covers this stage in detail.

Step 6: Testing and user acceptance

Test three things: that each feature works (functional testing), that end-to-end processes work across teams and integrations (system testing), and that real users can complete their daily work (user acceptance testing). Give business users realistic scenarios rather than asking them to “have a look around”.

Step 7: Go-live and adoption

Adoption decides the return on your investment. Train each role on its own daily tasks, nominate internal champions, and make Salesforce the only place where pipeline or case numbers are reported. Plan a period of close support after go-live to fix issues quickly while habits are forming.

Typical timeline

Scope	What it usually includes	Indicative duration
Focused rollout	One cloud, one team, standard processes, light integration	6 to 10 weeks
Mid-sized implementation	Sales and Service, several teams, one or two integrations, data migration	3 to 5 months
Multi-entity programme	Several entities or countries, ERP integration, complex security, phased releases	6 months or more

These ranges are planning guides, not quotes. Your actual timeline depends on scope, data quality and how quickly decisions are made.

Common mistakes to avoid

• Copying old processes exactly. Use the project to simplify, not to rebuild every workaround in a new tool.
• Over-customising early. Start with standard features and add code only for proven needs.
• Leaving integrations to the end. ERP and website integrations shape the data model, so design them first.
• Treating training as a single session. Adoption needs follow-up, reports managers rely on, and quick fixes after go-live.

Where to start

If you are planning a new rollout, a short discovery engagement gives you a scope, a phased plan and a realistic budget before you commit to a full build. You can read more about our Salesforce implementation services and Salesforce consulting, or see how similar projects were delivered in our Salesforce case studies.

Frequently asked questions

Related articles

Sources

• Salesforce: Hyperforce in the UAE
• Addleshaw Goddard: UAE Federal Data Protection Law 2021
• Business Dubai: UAE PDPL status in 2026

The three parts of Salesforce cost

When UAE businesses ask what Salesforce costs, they usually mean three different budgets:

1. Licences: the subscription you pay Salesforce for each user, plus any add-ons.
2. Implementation: the one-time work to configure, integrate, migrate data and train users.
3. Run and improve: administration, support, enhancements and new releases after go-live.

Looking only at the licence price is the most common budgeting mistake. A realistic business case includes all three over at least three years.

Licence costs

Salesforce lists its prices per user per month, billed annually, in US dollars. Published list prices for Sales Cloud in 2026, as tracked by licensing analysts, are below. Salesforce raised list prices for several editions in August 2025, so always confirm current prices and any discount with Salesforce directly.

Sales Cloud edition	Approximate list price (per user / month, billed annually)	Typical fit
Starter Suite	USD 25	Very small teams with simple needs
Pro Suite	USD 100	Small teams needing more customisation
Enterprise	About USD 175	Most mid-sized and growing companies
Unlimited	About USD 330	Larger teams needing premium support and sandboxes
Agentforce 1 Sales	USD 550	Teams adopting AI agents and Data 360 at scale

Other factors that change the licence bill:

• Mixed licence types. Not every user needs a full licence. Some only view dashboards or work in a single app, and lower-cost licence types may fit them.
• Add-ons. Extra sandboxes, storage, CPQ, Marketing Cloud, Data 360 or Agentforce are priced separately.
• AI usage. Agentforce can be licensed per user or consumed through Flex Credits, so usage-based costs need a forecast. See our Agentforce guide for how the models work.
• Contract terms. Term length, user commitments and renewal caps all affect what you actually pay.

Implementation costs

Implementation cost is driven by effort, so the useful question is what adds effort. These are the main drivers:

Cost driver	Lower effort	Higher effort
Teams and processes	One team, standard sales stages	Several teams, entities or countries with different processes
Integrations	Website forms, email, calendar	ERP, finance, telephony, custom APIs, real-time sync
Data migration	Clean spreadsheets, a few objects	Several legacy systems, duplicates, years of history
Customisation	Configuration and Flow	Apex code, Lightning Web Components, complex logic
Security and compliance	Simple roles	Field-level rules, data residency, audit needs
Change management	Small team, one location	Large user base, multiple languages and sites

Services are usually priced as a fixed scope, as time and materials, or as dedicated resources. Fixed scope gives budget certainty when requirements are clear. Time and materials suits evolving requirements. Dedicated developers or admins suit long programmes and ongoing improvement. IT Offshore publishes its engagement rates on the Salesforce implementation services page, with final pricing depending on scope.

Ongoing costs after go-live

Salesforce releases updates three times a year, users ask for improvements, and integrations need monitoring. Budget for one of the following:

• An internal Salesforce administrator
• A part-time or full-time external admin or developer
• A managed services arrangement covering support and enhancements

How to control Salesforce implementation cost

1. Phase the scope. Launch the processes with the highest value first, then add teams and features in later releases.
2. Prefer standard features. Every custom component has to be maintained and tested with each Salesforce release.
3. Clean data before migration. Data cleansing done by your team before the project is cheaper than fixing bad data in Salesforce.
4. Right-size licences. Match each user group to the licence it actually needs, and review usage before renewal.
5. Decide quickly. Slow sign-offs extend timelines, and time is the largest service cost.

A simple budgeting approach

Start with a short discovery phase that produces a written scope and estimate. Then compare three-year totals for licences, implementation and support across the options you are considering. For a second opinion on scope and licensing, talk to our Salesforce consulting team.

Frequently asked questions

Related articles

Sources

• Redress Compliance: Salesforce Sales Cloud list prices 2026
• Jitendra Zaa: Agentforce credits and cost model guide

Why integrate Salesforce with your ERP?

Salesforce manages customers and the sales process. Your ERP manages orders, inventory, invoicing and accounting. Without integration, staff copy data between the two, which causes delays, errors and arguments about whose numbers are right. Integration typically aims to:

• Turn closed opportunities into sales orders without re-keying
• Show order status, invoices and payments to account managers in Salesforce
• Keep customer, product and price data consistent across both systems
• Give leadership one view of pipeline, bookings and revenue

Step 1: Decide which system owns which data

Data	Usual system of record	Typical direction
Leads, opportunities, activities	Salesforce	Stays in Salesforce
Customer master (legal name, TRN, billing address)	Often the ERP, after the account is approved	Two-way with clear ownership per field
Products and price lists	ERP	ERP to Salesforce
Quotes	Salesforce (or CPQ)	Stays in Salesforce
Sales orders	ERP	Salesforce to ERP on close
Invoices, payments, credit limits	ERP	ERP to Salesforce for visibility

Agreeing this table with sales and finance before any build prevents most integration disputes later.

Step 2: Choose an integration pattern

• Real-time request and reply: Salesforce calls the ERP when a user needs live data, such as stock or credit status.
• Event-driven: a change in one system publishes an event that the other consumes, for example an order created on opportunity close.
• Scheduled batch: data syncs at set intervals, suitable for price lists or invoice history.
• Data virtualisation: Salesforce displays ERP data without storing it, useful for large invoice histories.

Most real projects combine several patterns.

Step 3: Choose the tools

Approach	When it fits	Trade-offs
Direct APIs (Apex callouts, ERP APIs)	One ERP, few data flows	Quick to start, harder to maintain as flows grow
Middleware or iPaaS (for example MuleSoft)	Several systems, complex mapping, monitoring needs	More setup and licence cost, much easier to scale and monitor
Pre-built connectors	Common ERPs with standard processes	Fast, but limited when processes are customised
Native ERP on Salesforce (for example Certinia)	Services businesses wanting CRM and finance on one platform	Removes CRM-ERP sync, but is an ERP decision in itself

Salesforce completed its acquisition of Informatica in November 2025, adding data integration, data quality and master data management capabilities alongside MuleSoft. These are worth considering for larger data programmes.

UAE e-invoicing: what it means for your integration

The UAE Ministry of Finance is introducing mandatory e-invoicing in phases. According to the timeline published in July 2026:

Phase	Who	Appoint an Accredited Service Provider by	Mandatory from
1	Businesses with annual revenue of AED 50 million or more	30 October 2026	1 January 2027
2	Businesses with annual revenue below AED 50 million	31 March 2027	1 July 2027
3	Government entities	31 March 2027	1 October 2027

E-invoices are issued in a structured format through Accredited Service Providers under a five-corner model. E-invoicing is usually handled by the ERP or finance system, not by Salesforce. But the data that flows from Salesforce into the ERP must be complete enough to produce a compliant invoice. In practice, review:

• Customer legal names, addresses and Tax Registration Numbers captured in Salesforce
• Product and tax codes on quote and order lines
• Validation rules that stop incomplete orders reaching the ERP
• How credit notes and amendments flow between systems

Confirm your obligations and dates with your tax adviser and the Ministry of Finance guidance, as details continue to be updated.

Testing and monitoring

• Test with realistic volumes and edge cases: partial deliveries, cancellations, credit notes, multi-currency orders.
• Log every integration error with a clear owner and alert.
• Build a reconciliation report comparing orders and invoices across both systems.

How we can help

Our Salesforce implementation team designs and builds integrations as part of rollouts, and our Salesforce developers can extend existing ones. If you are considering a Salesforce-native ERP, read what Certinia is and how it works, or see our Certinia and Salesforce case study.

Frequently asked questions

Related articles

Sources

• KPMG: UAE phased implementation of e-invoicing beginning 1 January 2027
• UAE Ministry of Finance: eInvoicing Programme update (June 2026)
• Salesforce: Salesforce completes acquisition of Informatica

What is Agentforce?

Agentforce is Salesforce’s platform for building and running AI agents. An agent can understand a request in natural language, look up information in Salesforce, and carry out defined actions, such as updating a record, creating a case or booking a meeting. Agents work for customers on your website or messaging channels, or for employees inside Salesforce and Slack.

Salesforce launched Agentforce in late 2024 and has expanded it since. At Dreamforce 2025 it introduced Agentforce 360 as the umbrella for its agent platform, and renamed Data Cloud to Data 360, the data layer agents use to work with unified customer data.

How an Agentforce agent works

Each agent is configured from a few building blocks:

• Topics: the jobs the agent handles, such as “order status” or “appointment booking”.
• Instructions: plain-language rules about how to handle each topic and what to avoid.
• Actions: what the agent can do, built from Flows, Apex, prompt templates or API calls.
• Data: the Salesforce records and knowledge articles the agent can use to ground its answers.
• Guardrails: permissions, escalation rules and the Einstein Trust Layer, which governs how data is handled when it is sent to the AI model.

The practical lesson is that an agent is only as good as the processes and data behind it. If your Flows are unreliable or your knowledge base is out of date, the agent will repeat those problems faster.

Practical use cases

Area	Example agent task	What it needs
Customer service	Answer order, booking or policy questions and create a case when it cannot help	Accurate knowledge articles, case routing, escalation rules
Sales	Respond to inbound enquiries, qualify leads and book meetings	Lead data, qualification criteria, calendar integration
Internal productivity	Summarise an account, draft follow-up emails, prepare meeting notes	Well-structured account and activity data
Field and operations	Check appointment status or reschedule visits	Scheduling data and clear rules

For UAE businesses serving customers in Arabic and English, test both languages early with real customer phrasing, including mixed-language messages, and keep a clear handover to a human.

How Agentforce pricing works

Salesforce has offered several pricing models since launch. Based on published analyses of Salesforce’s pricing in 2026:

• Flex Credits: a consumption model introduced in May 2025. Each standard agent action consumes credits; analysts report a list price of USD 500 per 100,000 credits, which works out to around USD 0.10 per standard action.
• Per-conversation pricing: the original model at launch, at USD 2 per conversation.
• Per-user add-ons: Agentforce add-ons for Sales, Service and other clouds, listed at about USD 125 per user per month for internal use.
• Agentforce 1 editions: top-tier bundles listed from USD 550 per user per month that include Agentforce, Data 360 credits and other features.

Prices and included allowances change, so confirm current terms with Salesforce before you build a business case. The bigger budgeting question is usage: estimate how many conversations or actions you expect each month, and test that estimate during a pilot.

A four-step plan to start

1. Pick one narrow use case. Choose a high-volume, low-risk task where answers are already documented.
2. Fix the foundations. Clean the relevant data, update knowledge articles and make sure the underlying Flows work reliably.
3. Pilot with guardrails. Limit topics and actions, define escalation to a human, and review conversations every week.
4. Measure and expand. Track resolution rate, handover rate and customer feedback, then add topics one at a time.

Data and compliance considerations

Before you connect customer data to an AI agent, check which data protection regime applies to your entity, what data the agent can access, and how conversations are stored. In the UAE, mainland companies are covered by the federal PDPL, while DIFC and ADGM entities follow their own rules. Apply least-privilege permissions to agent users, as you would to any staff member.

Getting help

Our Salesforce consulting team can help you choose a first use case, prepare the data and processes, and design a pilot. If you need hands-on build capacity, you can also hire a Salesforce developer to build the Flows and actions behind your agents.

Frequently asked questions

Related articles

Sources

• Salesforce Ben: Data Cloud renamed Data 360 as part of Agentforce 360
• Jitendra Zaa: Agentforce credits and cost model guide
• Redress Compliance: Salesforce Sales Cloud list prices 2026

Why this migration matters now

Salesforce announced that Workflow Rules and Process Builder would no longer be supported after 31 December 2025. In practice, that means existing automation built with these tools no longer receives Salesforce support or bug fixes. If a process breaks or behaves unexpectedly, you are on your own.

Many UAE orgs that went live several years ago still run a mix of Workflow Rules, Process Builders, Flows and Apex triggers on the same objects. That mix makes the order of execution hard to predict and changes risky. Moving to Flow is a chance to make your automation simpler and easier to maintain.

What Flow can do

• Record-triggered Flows: run when a record is created, updated or deleted, before or after save.
• Scheduled Flows: run on a schedule, for example nightly reminders or renewals.
• Screen Flows: guided forms for users, such as onboarding or approval requests.
• Autolaunched Flows: reusable logic called from other Flows, Apex, APIs or Agentforce actions.

Flow also supports error handling paths, subflows and debugging tools that the older tools lacked. And because Agentforce actions can be built from Flows, a clean Flow layer prepares your org for AI agents too.

A five-step migration approach

1. Inventory every automation

List all active Workflow Rules, Process Builders, Flows and Apex triggers by object. Record what each does, when it fires, and who owns the business rule. Salesforce’s setup pages and the Migrate to Flow tool help identify what exists.

2. Remove what is no longer needed

Older orgs often contain automation for teams, products or fields that no longer exist. Confirm with business owners and retire anything unused. Every rule removed is one less thing to migrate and test.

3. Redesign, do not just convert

The Migrate to Flow tool can convert many Workflow Rules and some Process Builders, but a one-to-one conversion keeps old problems. A better pattern is:

• One before-save Flow per object for fast field updates
• One or a small number of after-save Flows per object for related records, emails and integrations
• Clear entry criteria so each Flow runs only when needed
• Subflows for logic used in several places

4. Test with realistic data

Test in a full or partial copy sandbox with realistic data. Include bulk updates, such as a data load of several thousand records, because automation that works for one record can hit governor limits in bulk.

5. Deploy and switch over carefully

Deploy the new Flows inactive, then activate them and deactivate the old automation in the same release window. Monitor errors closely for the first weeks and keep a rollback plan.

Workflow Rule and Process Builder actions in Flow

Old action	Flow equivalent
Field update on the same record	Before-save record-triggered Flow (fastest option)
Email alert	Send Email Alert action in an after-save Flow
Create or update related records	After-save Flow with Create or Update Records elements
Time-based workflow	Scheduled paths in a record-triggered Flow
Outbound message	Outbound message action, or a platform event or HTTP callout
Invoke another process	Subflow

When to use Apex instead

Flow handles most business automation, but Apex is still the better choice for very high-volume processing, complex calculations or logic that must run asynchronously in batches. In one of our case studies, the project combined a Flow migration with an Apex Batch class for bulk lead conversion, because the volume was too high for a single transaction.

Common pitfalls

• Converting everything without checking whether it is still used
• Creating many small Flows on the same object with overlapping entry criteria
• Forgetting fault paths, so users see generic errors
• Testing only single-record edits, not bulk updates or integrations
• Leaving old rules active alongside new Flows, which causes duplicate updates

Need help with the migration?

A migration is a good fit for a short assessment followed by phased delivery, object by object. Our Salesforce managed services team can audit your current automation and deliver the migration alongside day-to-day support. If you need extra build capacity, you can hire a Salesforce developer or hire a Salesforce admin.

Frequently asked questions

Related articles

Sources

• Salesforce Ben: End of support for Workflow Rules and Process Builder

The short answer

Choose Sales Cloud if your main challenge is finding, tracking and closing new business. Choose Service Cloud if your main challenge is handling customer requests, complaints and after-sales support. If both teams work with the same customers, using both on one Salesforce org gives everyone a single view of each account.

What Sales Cloud does

Sales Cloud is Salesforce’s CRM for sales teams. Its core features include:

• Lead capture and qualification from your website, events and campaigns
• Accounts, contacts and opportunities with configurable sales stages
• Activity tracking for calls, meetings and emails
• Pipeline management and sales forecasting
• Products, price books and quotes
• Reports and dashboards for sales managers

Typical users are sales representatives, sales managers, business development teams and leadership who need pipeline visibility.

What Service Cloud does

Service Cloud is Salesforce’s customer service application. Its core features include:

• Case management with queues, assignment and escalation rules
• Omni-channel routing across email, web forms, chat, messaging and phone
• Knowledge base articles for agents and customers
• Service level agreements and entitlement tracking
• Customer self-service portals through Experience Cloud
• Service dashboards for response times, backlog and satisfaction

Typical users are support agents, service managers and operations teams.

Side-by-side comparison

Area	Sales Cloud	Service Cloud
Main goal	Win and grow revenue	Resolve customer issues efficiently
Core record	Lead and opportunity	Case
Key measures	Pipeline, win rate, forecast accuracy	Response time, resolution time, backlog, satisfaction
Channels	Email, calls, meetings	Email, web, messaging, chat, phone
Typical users	Sales reps and managers	Support agents and service managers
AI examples	Lead qualification, opportunity insights, email drafting	Case summaries, reply suggestions, self-service agents

When you need both

Many UAE businesses benefit from both clouds because sales and service share the same customers. Examples include:

• Real estate developers and brokers: sales teams manage enquiries and bookings, while customer care handles handover, snagging and service requests.
• B2B distributors: account managers track opportunities, while support teams manage orders, returns and warranty claims.
• Education and training providers: admissions teams handle enquiries, while student services manage requests after enrolment.
• Professional services firms: business development tracks proposals, while delivery and support teams handle client requests.

With both on one org, a salesperson can see open cases before a renewal call, and a support agent can see the customer’s contract and account owner.

How to decide

1. List the three biggest problems your teams face with customers today.
2. Check whether they sit in the path to purchase (Sales Cloud) or after purchase (Service Cloud).
3. Estimate how many users need each product. Licence counts drive cost, so not everyone needs both.
4. Plan a phased rollout: start where the problem is biggest, then add the second cloud on the same data model.

Edition choice matters too. Higher editions add automation capacity, sandboxes and advanced features. Our Salesforce cost guide explains the licence factors, and our Salesforce consultants can map your requirements to the right products and editions.

Real-world example

In one of our published case studies, a performance marketing company used both Sales Cloud and Service Cloud, with ongoing support covering automation, bulk lead conversion and dashboards for both teams.

Frequently asked questions

Related articles

Sources

• Redress Compliance: Salesforce Sales Cloud list prices 2026

Why data migration deserves its own plan

Users judge a new CRM on the first day by whether their customers, deals and history look right. If they find duplicates, missing contacts or broken ownership, trust drops quickly and old spreadsheets come back. A planned migration avoids that.

This checklist covers moving data into Salesforce from spreadsheets, an older CRM, an ERP or another Salesforce org.

1. Scope what to migrate

• List every source system and the objects it holds: accounts, contacts, leads, opportunities, cases, activities, products, files.
• Agree a cut-off for history. Many teams migrate open records plus two or three years of closed records and archive the rest.
• Identify data that must not be migrated, such as personal data you no longer have a reason to keep. In the UAE, check which data protection regime applies to your entity before you copy personal data into a new system.
• Note dependencies. Accounts must load before contacts, and contacts before opportunities and cases.

2. Profile and clean the source data

• Find duplicates in companies and contacts, including spelling variants of the same company name in English and transliterated Arabic.
• Standardise formats for phone numbers (for example +971), emails, countries, emirates and currencies.
• Fill or flag missing mandatory values.
• Agree a “golden record” rule for duplicates: which source wins for each field.
• Remove test data, inactive users’ junk records and obsolete picklist values.

Cleaning in the source or in a staging area is usually faster than fixing records after they reach Salesforce.

3. Map fields and values

• Create a mapping document for each object: source field, target field, transformation rule, default value.
• Map picklist values explicitly, such as old sales stages to new ones.
• Plan record ownership. Map old users to new Salesforce users, and decide where records of departed staff should go.
• Add an external ID field to each object to hold the source system ID. This makes relationships, reloads and reconciliation much easier.

4. Choose the right tool

Tool	Best for	Notes
Data Import Wizard	Simple loads of fewer than 50,000 records into supported objects	Browser-based, built-in duplicate matching for some objects
Data Loader	Loads of up to 5 million records, unsupported objects, repeatable loads	Desktop or command-line tool; supports upsert with external IDs
ETL or integration tools	Complex transformations, multiple sources, ongoing sync	Examples include MuleSoft and third-party ETL tools

Salesforce’s own documentation recommends Data Loader for larger, scheduled or complex loads, and suggests involving a partner or specialist tools beyond 5 million records.

5. Prepare the target org

• Temporarily review validation rules, duplicate rules and automation that could block or slow the load, and document every change you make.
• Check storage limits for data and files.
• Create users, roles and record types before loading records that depend on them.
• Decide whether audit fields such as original created dates need to be preserved, and enable that setting if so.

6. Run trial loads in a sandbox

Do at least one full trial load into a sandbox with production-like settings. Record load times, error counts and fixes. Repeat until the load runs cleanly. This also tells you how long the production cutover will take.

7. Validate with the business

• Compare record counts per object between source and target.
• Check totals, such as pipeline value by stage or open cases by team.
• Ask key users to spot-check accounts they know well.
• Confirm that relationships, owners and attachments are correct.

8. Plan the cutover

• Agree a freeze period when the old system is read-only.
• Run a final delta load for records changed since the trial load.
• Re-enable validation rules and automation, and test them.
• Keep the old system available read-only for a defined period for reference.

Org-to-org migrations

Merging several Salesforce orgs adds schema conflicts, duplicate users and overlapping automation. In our org consolidation case study, three orgs were mapped to one standard data model, with deduplication rules applied before and during migration.

Get support for your migration

Data migration is usually part of a wider rollout. See our Salesforce implementation services, or read our step-by-step implementation guide for how migration fits into the overall plan.

Frequently asked questions

Related articles

Sources

• Salesforce Developers: When to use Data Loader

What does a Salesforce developer do?

A Salesforce developer builds what configuration alone cannot. Typical work includes Apex classes and triggers, Lightning Web Components, integrations with ERPs and other systems, complex Flows, batch jobs, and deployment pipelines. This is different from a Salesforce administrator, who manages users, configuration, reports and declarative automation. Many teams need both.

The three main hiring models

In-house employee

A permanent developer on your payroll, usually based in your office. You get full control, deep business knowledge over time, and someone available during your working hours. The trade-offs are recruitment time, salary and benefits, visa and onboarding costs, and the risk of a single point of failure if that person leaves.

Freelancer or contractor

An independent developer engaged for a project or by the hour. This is flexible and fast to start for a defined task. The trade-offs are availability, continuity, documentation and the fact that one person rarely covers every skill.

Offshore dedicated developer

A developer employed by a services company who works full-time or part-time on your Salesforce org. You direct the work, and the provider handles employment, equipment and continuity. The trade-offs are time zone overlap, communication discipline and the need to choose a provider with real Salesforce depth.

Comparison at a glance

Factor	In-house	Freelance	Offshore dedicated
Time to start	Slow (recruitment)	Fast	Usually fast
Cost structure	Fixed salary and benefits	Hourly or project rate	Monthly or hourly rate
Control over priorities	High	Medium	High
Continuity if someone leaves	Low	Low	Higher, provider can replace
Access to wider skills	Limited to the hire	Limited to the individual	Often access to a wider team
Best for	Large, long-term programmes	Short, defined tasks	Ongoing development and support

Time zones and working hours

For UAE businesses, an offshore team in South Asia typically works with a small time difference, which allows good overlap with the UAE working day. Agree core overlap hours, response times and a daily or weekly check-in from the start.

How to evaluate a Salesforce developer

• Technical skills: Apex, SOQL, Lightning Web Components, Flow, governor limits, asynchronous processing and integrations.
• Delivery practices: sandboxes, version control, code review, test coverage and deployment tools.
• Relevant experience: similar clouds and integrations to yours, such as Sales Cloud, Service Cloud, CPQ or Certinia.
• Communication: can they explain a technical trade-off clearly to a business user?
• Certifications: useful as a baseline, but verify them on Salesforce’s credential verification site and test practical skills too.

A short paid trial task on a sandbox is one of the most reliable ways to judge real skill.

What to put in the engagement agreement

• Scope of work and reporting line
• Working hours, overlap and response times
• Access controls and data protection obligations
• Ownership of code and documentation
• Replacement and notice terms

IT Offshore’s engagement models

IT Offshore offers hourly, part-time and full-time engagement models for Salesforce developers, admins and consultants, with rates published on our Hire a Salesforce Developer page. Final scope is confirmed with our team. You can also hire a Salesforce admin or hire a Salesforce consultant if the role you need is broader than development.

Frequently asked questions

Related articles