Logo for MovePlnr - the Best Residential Moving Company CRMMovePlnr
For owners and office admins

Share and copy templates across branches

When you run more than one location, you should not have to write the same estimate twice. This guide covers company templates that every branch shares, the wizard that copies one location's templates to another, and importing notifications from one template into another. Start with the video.

Before you start

  • Each kind of template needs its own add-on: Estimates, Contracts, Customer Waivers, Invoice Notifications, Review Collection or Lead Auto Follow-Up
Do this in MovePlnr

In this video

Tap a chapter to jump straight to it. Captions are on; turn them off with the CC button.

Three ways to reuse a template

MovePlnr keeps estimates, contracts, emails and texts per location. When you open a second branch, you have three ways to avoid starting from a blank page:

Company templates

Write a template once at the company level and turn it on at each location. Each branch fills in its own details, such as its phone number. Change the wording once and every branch gets it.

Do this: one copy, many branches.

Migrate templates

A step-by-step wizard copies one location’s estimate settings, emails and contract templates to another, so you can check and adjust each one before it is saved.

Do this: a new branch, set up in one sitting.

Import notifications

Bring the emails set up on one estimate or contract template into another, one email at a time.

Do this: emails from a template you trust.

Share one template with every location

Do this in MovePlnr

Open Company Templates in your company settings. Templates are grouped by kind. Each one shows where it is in use: Active in 1 location, or Not activated if no branch uses it yet.

The Company Templates page with an estimate template active in one location and a review email not activated
One estimate shared by your branches, and a review email waiting to be turned on.

Make a company template

A company template always starts from a template one of your locations already has.

  1. Click New company template.
  2. Under Template type, pick the kind of template, such as Estimate.
  3. Under Seed from location template, pick the location template to start from. Each one shows its location in brackets.
  4. Click Create. The new company template opens.
The New company template dialog with Estimate picked and the list of location templates open
Start from the best version you already have, at any branch.

The location template you started from stays where it is. The company template is a separate, shared copy.

Edit the shared wording

The Content tab holds the wording every branch sends: the name, the description your team sees, and the customer-facing text. For an estimate that is the document title, the opening and closing paragraphs, and the accept and decline pages. Click Save when you are done. The change reaches every location where the template is active.

The Content tab of a company estimate template, with location placeholders in the opening paragraph
Write once. The branch details come from placeholders.

Where the wording should differ by branch, use a location placeholder, written like {{location.branchPhone}}. Each location fills in its own value, and the customer sees that value in place of the placeholder.

For contracts and waivers, the Content tab edits the title and instructions. The PDF and its signature fields come from the location template you started from. To use a different PDF, make a new company template from a location template that has it.

Set up placeholders

Click Placeholders on the Company Templates page to see the Location Placeholders. Click New placeholder to add one.

The Location Placeholders page with Branch manager and Branch phone
Branch phone is required, so every branch must fill it in before it can use a template that has it.
  • The key is the name you type in the template, such as branchPhone. Once a template uses it, the key is locked; the label stays editable.
  • The label is what admins see when they fill in each branch’s value.
  • A placeholder marked Required must have a value at a location before that location can turn on a template that uses it.
  • A placeholder can be text, a percent or a currency amount, and can have a default.
  • Used in 1 tells you how many company templates use it.

Turn it on at each location

Open the template and click the Locations tab. Every active location has its own card, with a box for each placeholder the template uses.

  1. Fill in the branch’s values. Each one saves when you click out of the box.
  2. When the location shows Ready, flip Activate. It changes to Active.
  3. To make it the location’s first choice, flip Default. The switch appears once the template is active there.
The Locations tab with Calgary active and default, and Calgary South showing Missing values
Calgary is live. Calgary South still needs its branch phone.

A location with a required placeholder still empty shows Missing values and names what is missing, and its switch stays off until you fill it in.

Check the result before customers see it

Click Preview on a location’s card. MovePlnr shows the wording with that branch’s values and a sample move filled in. If any placeholder has no value at that location, the preview lists it, so a blank never reaches a customer unnoticed.

Preview of the shared estimate at the Calgary location
The branch manager and phone are filled in from the Calgary card.

Where your branches see it

A location’s own settings page shows the company templates active there, under Company templates active here, with a link back. They are read-only on that page: change them from Company Templates.

Estimate Settings for Calgary with the Company templates active here notice
The shared estimate is the default at Calgary, next to the location's own templates.

To retire a company template, turn it off at every location, then click the archive icon on its row.

Copy a location’s templates to another

Do this in MovePlnr

Use the Migrate Templates wizard when a new branch should start with what another branch already has.

  1. Open Admin, then Locations.
  2. Click the three dots on the row of the location you are copying to, and choose Migrate Templates.
  3. Under Source Location, pick the branch to copy from, then click Start Migration.
The actions menu on the Calgary South row with Migrate Templates
Start from the branch that needs the templates.
The Migrate Templates dialog with Calgary as the source location
Pick the branch to copy from.

Work through the wizard

The wizard lists everything the source branch has, in groups: contract templates, estimate settings, estimate emails, review emails, the system emails (such as reminders and schedules) and campaign emails. It opens on the first one.

The template migration wizard copying Calgary's Standard Move Estimate to Calgary South
One template at a time, filled in from the source branch. The bar counts what is done.
  1. Read the template. It is filled in from the source branch, so check anything that should be different here: the address, the phone number, the wording.
  2. Click Save & Next to save it to the new location, or Skip to leave it out.
  3. Repeat until the bar is full. Click any template in the list on the left to jump to it.

Estimate settings, emails and contract templates are added to the new location as new templates. System emails replace the new location’s own version. If the new location already has a template with the same name, the wizard warns you so you can rename it first.

When you finish, the wizard shows how many templates you saved and skipped. If you reload the page partway through, it keeps your place in that browser tab.

The Create Location form with Copy Templates From
Copy Templates From starts the wizard as soon as the location exists.

Import notifications from another template

Do this in MovePlnr

Every estimate template and contract template has its own emails: the one that sends the estimate, the reminders, the confirmation. If another location already has good ones, import them instead of writing them again.

  1. Open Estimate Settings (or Contract Settings for a contract) at the location you are importing into.
  2. Click the three dots on the template’s row and choose Import Notifications.
  3. Pick the Source Location, then the template there to import from, and click Start Import.
  4. For each email, the source is on the left and this template’s version on the right. Click Copy Over to bring the source wording across, then adjust it if you need to.
  5. Click Save & Next to keep it, or Skip to keep this template’s own version. The last one saves and finishes.
Import Notifications showing the source email on the left and the copied wording on the right
Copy Over brings the wording across. Nothing is saved until you click Save & Next.

When the import is done, MovePlnr shows how many emails were saved and how many were skipped.

Questions admins ask

Which should I use: a company template or the migration wizard?
Use a company template when every branch should send the same wording and you want one place to change it. Use the wizard when a new branch should start from another branch’s templates and then go its own way. After the wizard, each branch’s copy is its own.
If I edit a company template, do my branches get the change?
Yes. Every location where the template is active uses the new wording as soon as you save.
Why can't I turn a company template on at a location?
The location has a required placeholder with no value. Fill it in on the Locations tab and the switch becomes available.
Can a branch manager edit a company template from their location settings?
No. Location settings show the company templates active there, read-only. Company admins edit them under Company Templates.
Why is a kind of template missing from Company Templates?
Each kind needs its add-on. Waivers, for example, only appear when Customer Waivers is on.
Does the wizard change anything at the branch I copy from?
No. It only reads the source branch. Everything it saves goes to the location you are copying to.

Updated October 16, 2026, captured on MovePlnr v3.2.0