> How RestoreCord's Consistent and Batching pull styles space out a migration, which plans include them, and how to pause, resume or stop a move in progress.

Source: https://restorecord.services/consistent-vs-batching

# Consistent vs Batching: pacing a Discord migration

When a RestoreCord migration starts, you choose how additions are spaced out. Here's what each pull style does, which plans have it and when to pick which.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Consistent adds members one after another with a delay between each attempt and is available on every plan. Batching, the Enterprise grouping style, adds members in groups with a pause between groups. Use Consistent for speed and Batching to spread a big move over time.

## Consistent

Members are added **one after another** with a delay between each attempt. On Free the delay is fixed. On Premium, Business and Enterprise you can set a **delay range**, so the gaps vary between a minimum and a maximum.

### Choose Consistent when

* You want the move done as fast as Discord's rate limits allow.
* The destination is ready and staff are around to welcome people.
* It's a recovery after an incident and every hour counts.

## Batching

Members are added in **groups**, with a pause between each group. You choose how many members go into a group and how many hours to wait before the next one. In the dashboard this is the **Grouping** pull style, available on Enterprise.

### Choose Batching when

* You're moving a very large community and want arrivals spread over days.
* Staff should settle each wave before the next one lands.
* You want to see how a wave behaves before sending more.

## Consistent and Batching compared

|               | Consistent                       | Batching                            |
| ------------- | -------------------------------- | ----------------------------------- |
| Plans         | All plans                        | Enterprise                          |
| Rhythm        | Steady, one at a time            | Bursts with pauses                  |
| Delay control | Fixed on Free, range on Premium+ | Group size and hours between groups |
| Finishes      | As soon as rate limits allow     | Later, by design                    |
| Best for      | Recoveries, ready destinations   | Huge moves, staged launches         |

## Two example setups

### A same-day recovery

A server was lost and the replacement is ready. Pick Consistent, a delay range on Premium or above, no filters and start immediately. Staff watch the first few minutes and then let it run.

### A week-long relaunch

A large community moves to a rebranded server. On Enterprise, pick Batching with groups sized so moderators can greet each wave, a few hours between groups and a start time that matches the announcement.

## Rate limits set the real speed

Whichever style you pick, Discord's API limits decide the true pace. RestoreCord adds no pull cooldown on any plan, but large migrations still take time, and rate limits are a normal part of that. Neither style promises a fixed finish time. For big moves, start with conservative delays and increase throughput only after the first batch looks healthy.

### A safe way to tune the delay

1. 1Start with a wider delay range than you think you need.
2. 2Watch the live queue for the first few dozen attempts.
3. 3If pulls succeed cleanly and staff keep up, start the next migration with a tighter range.
4. 4If Discord starts limiting the server, pause, wait and resume rather than stopping.

## Combine with a start time

On Premium and above, either style can be scheduled. Set the start for the moment you announce the move. Enterprise can also choose to start immediately even when scheduling controls are on.

## Steering a running migration

You can **pause**, **resume** or **stop** a migration while it runs. Stopping is final, so pause if you only need a moment. The live queue shows how many members were pulled, skipped and failed.

Token imports are different: an import can't be stopped or paused once it starts. Treat it as a one-way operation.

## Measure the result

On Business and Enterprise, migration analytics include per-migration activity graphs, and member event tracking records leaves. A spike of leaves right after a wave usually means people weren't told about the move. Read [how to plan a move](https://restorecord.services/plan-a-community-move), [how to merge two servers](https://restorecord.services/merge-two-discord-servers) or [how to read migration results](https://restorecord.services/migration-results-explained), or return to [RestoreCord Migration](https://restorecord.services/).

## Pull style questions

### 

### 

### 

## Set the pace of your move

Pick Consistent or Batching in RestoreCord and steer every migration live, from first member to last.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
