How Particle works

From source data to load files, withreview at the decisions that matter.

Particle carries the conversion forward, proposes its work with evidence, and pauses when your team needs to decide.

Who does what

Particle reads the source, proposes extracts and mappings, checks claims against the data, and builds load files.

Your team resolves questions that require business judgment and reviews the evidence supporting the proposal.

The run resumes from the step where it paused, carrying the recorded decision into the next stage.

Source examples

Target examples

Approvals are answered in

Which sources can Particle work with?: Particle supports any source. SAP ECC, Oracle EBS and JD Edwards are examples, not a complete list.
Which targets can Particle load into?: Any target. SAP S/4HANA, Workday, Salesforce, NetSuite and Oracle Fusion are examples, not a complete list. A target Particle has not loaded before is agreed up front and built in.
Does Particle write back to the source?: No. Source access is read-only.
Where do approvals happen?: Approval questions can be handled in Microsoft Teams, Slack, or Jira.
Does a paused run start over?: No. It resumes from the step where it paused.
Where does Particle run?: Particle is self-hosted in your own cloud tenant. The workflow and the conversion data sit inside your boundary rather than ours.
How is network access controlled?: Particle runs inside your tenant, so ingress and egress are governed by the controls you already operate there.
Where do extracts, mappings and load files end up?: In your own store, alongside the run that produced them.
Can you revoke Particle’s access?: Yes. Particle authenticates as a read-only role you create, and you can revoke it at any time.

Work with the founders

Tell us your source, scope, and timeline.