Sistership, by GTM Cloud · Close and renew · Early access

Clone records in Salesforce with related records, minus the baggage

Sistership is a custom clone button for Salesforce that applies your rules to the copy as it’s made: blank this, set that, protect the other. You choose which related records come along, and a log shows what changed.

You know this one

Tuesday’s pipeline review. Someone in sales ops spots a renewal on the list with a close date from last March and a stage of Closed Won. Nobody sold it. A rep cloned last year’s Opportunity, changed the name, and forgot the rest.

By Thursday you’ve found the others. One still has last year’s notes. One kept the old owner.

The Clone button did what it’s built to do: it copied everything. The fixing, field by field, was left to whoever clicked. Some reps remember all of it. Most remember most of it.

How to clone a record in Salesforce and have the copy come out ready to use

Sistership lets you clone records in Salesforce with related records and applies your rules to the copy as it’s created. A rule reads like a sentence: if the copy matches these conditions, then blank a field, set a value, copy one field into another, fill a date or the current user, build text from a template, or protect a field. Else, do something different.

You also choose which related records travel with the clone, for each set of rules. An Account’s Contacts, for example. Fields no rule mentions keep their copied value, so you only write rules for what needs changing.

A sistership is a ship built to the same plan as another. Same shape, new vessel.

See it first. Take it back. Keep the receipt.

PreviewUndoProve
Rules are written as If, Then and Else, so anyone can read what a clone will do.Not needed: a clone is a new record and the original is never touched.A clone log with every changed field, old value and new.

What you get

Copies that arrive clean

A rule can blank, set, copy, fill a date or the current user, build text from a template, or protect a field. Rule order decides which wins when two set the same field.

Related records, by your choice

For each set of rules, you pick which related records come along. The Contacts on an Account, say, and nothing else.

Three ways to start a clone

Start from a Flow action, a quick action on the page layout, or a button on the Lightning record page. Nothing is installed on any object.

A log that shows its work

The log lists each clone, the rule that ran, and every field it changed with the old value and the new one. You can set how long it’s kept.

The standard Clone button stays exactly as it is

Sistership is an extra action you place where you want it. The copy is made with the person’s own field access and sharing.

How it works

  1. Switch it on. On the Settings tab, make sure Enable Sistership is on.
  2. Write a rule. On the Rules tab, choose the object and write the rule in If, Then and Else.
  3. Give people a way to clone. Add the quick action, place the button, or use the Flow action.
  4. Clone and check. Clone a record, then check the copy and the log.

Two readers, two reasons

If you’re the admin

Retire the one-off Flow and the Apex class you keep for each object. One app covers many objects, and the rules are ones anyone on the team can read.

If you’re the one signing off

Renewals, repeat deals and follow-up cases start life as a copy. The ones nobody fixes go out with last year’s dates. With Sistership the copy arrives ready to use, and the log shows what each clone changed.

Today, and with Sistership

TodayWith Sistership
People must remember which fields to reset after each cloneRules clean the copy as it’s made
Copies go out with old dates, statuses and notesRelated records copied by your choice
A custom Flow or Apex class for every object that needs itOne app, one set of rules, many objects
No record of what a clone changedA log of every clone and every changed field

Where it’s strong, and what to know first

We’d rather you find the limits here than after you install.

Where Sistership is strong

  • Copies arrive clean: fields blanked, set, copied, filled or protected by your rules
  • You choose which related records come along, for each set of rules
  • Three ways to start a clone: a Flow action, a quick action or a page button
  • A log of every clone and every field it changed
  • The standard Clone button is left exactly as it is

Good to know before you install

  • This is a second way to clone. The standard Clone button still copies everything, so decide which one your page layouts offer.
  • There’s no undo, because a clone is a new record. If you didn’t want the copy, delete it.
  • People can clone only the objects they’re allowed to create records in.

Questions people ask

How do I clone a record with related records in Salesforce?

With Sistership, you pick the related records a clone copies when you write the rules for an object, an Account’s Contacts for example. People then clone from a Flow action, a quick action or a page button, and the copy arrives with those records and your field rules applied.

How do I stop the Clone button copying old dates and statuses?

The standard Clone button copies every field, so a stale status or an old date comes along with it. Sistership adds a second way to clone. Its rules blank or set those fields on the copy, or fill a date, while the standard button stays as it is.

Does it change the standard Clone button?

No. Nothing is installed on any object and the standard button keeps working. Sistership is an extra action you place where you want it. The standard button still copies everything, so decide which clone your page layouts offer.

What can a rule do?

A rule can blank a field, set a value, copy one field into another, fill a date or the current user, build text from a template, or protect a field. Fields no rule mentions keep their copied value, so you only write rules for what needs changing.

Can a clone give someone data they should not have?

No. The copy is made with the person’s own field access and sharing, so a clone follows the same access that person already has. People can also clone only the objects they’re allowed to create records in.

Can automation use the same rules?

Yes. The Flow action runs the same rules, so a clone made by automation matches a clone made by hand. You write the rules once, then start the clone from a Flow, a quick action or a page button, whichever suits the process.

Works well with

Sistership is part of the Close and renew stage of the lead-to-renewal map. Not sure how much stale data your copies are carrying? A Data Health Check will show you. Every app installs by itself. None needs another.

Built on the platform

  • Native to Salesforce. Rules are stored as Custom Metadata in your org.
  • Respects security. The copy is made with the person’s own field access and sharing.
  • Three permission sets: Admin, User and Read Only.
  • In-app guides for admins and users, in English, German, Spanish, French (Canada) and Portuguese (Brazil).

Tell us the record you clone most

Ask for early access and a walk-through with a rule for that object. Clone it, open the copy, and read the log of what changed.