Salesforce
Salesforce development and org cleanup
Apex, Lightning Web Components, Flow, and the permissions underneath. We build MokuBot for Salesforce on the same platform.
sales@mokuhub.com. We reply within 24 hours.
Starting points
What people bring us
- A Flow triggers Apex that triggers the Flow.
- Salesforce and NetSuite disagree about the same customer.
- An integration user with permissions nobody can explain.
- A migration that must keep history and ownership.
Scope
The work itself
Build and fix
- Apex: triggers, batch, queueable, REST
- Lightning Web Components
- Flow, and moving overgrown Flows into Apex
- Schema design
- Platform Events
Connect and move
- Integration users and permission sets
- Data migration with activity history
- Org-to-org sync
- NetSuite-to-Salesforce sync
Process
How an engagement runs
- 01
We map what exists
Automation, triggers and permissions, written down first.
- 02
You get a written scope
What changes, in what order, and the fallback for risky steps.
- 03
Work happens in a sandbox
Reviewable pieces with tests, through your release process.
- 04
Handover
Docs for admins and developers, plus a walkthrough.
FAQ
Common questions
Start with what is misbehaving
A few sentences are enough. We reply with what we would map first.
Describe the problemsales@mokuhub.com. We reply within 24 hours.