Copy Module Layout lets a super administrator copy a module's complete field and layout setup — fields, sections, picklist values, and related settings — from one CRM instance into another. Instead of rebuilding dozens of custom fields by hand when a new instance is set up, you pick a source, a target, and a module, preview the changes, and let the system apply them in the background.
Contents
1. Before You Start
2. Open Copy Module Layout
3. Choose What to Copy
4. Preview the Changes
5. Run the Copy
6. Track Your Copy Jobs
7. What Gets Copied
8. Frequently Asked Questions
1. Before You Start
You will need:
A super administrator account on the admin instance (only the sysadmin or admin user can open this tool).
The names of the source instance (the one whose module setup you want to copy) and the target instance (the one that should receive it).
A target module that is new or nearly empty — Full Replace mode is only allowed when the target module has 10 or fewer records.
Access requirements: The tool lives on the admin instance only. On any other instance the page will not open, and other user accounts cannot see the menu entry.
If you do not see Copy Module Layout in the menu, you are either not on the admin instance or not signed in as a super administrator — contact Dazos support if you believe you should have access.
2. Open Copy Module Layout
From the CRM, navigate to Settings → CRM Settings → Module Management → Copy Module Layout.
The screen has two areas:
Area | What it shows |
Copy Module Layout | The form where you pick the source instance, target instance, module, and mode. |
Recent Copy Jobs | A searchable history of past and pending copy jobs with their status and results. |
3. Choose What to Copy
Fill in the four selections at the top of the screen:
Field | Description | Example |
Source Instance | The instance to copy FROM. | yourclinic(insightstx) |
Target Instance | The instance to copy INTO. Must be different from the source. | newclinic(insightstx) |
Module | The module whose fields and layout will be copied. The list only offers modules available on both instances; if the module is missing or inactive on the target, an error appears. | UR Authorization |
Mode | How the copy behaves — see below. | Full Replace |
Choosing a mode:
Mode | What it does |
Full Replace | Makes the target module exactly match the source: adds missing fields, recreates fields whose definition differs, and removes fields the source does not have. Removing a field deletes any data stored in it, so this mode is only allowed when the target module has 10 or fewer records. |
Merge (add only) | Only adds fields that are missing on the target. Nothing is removed or changed, making it safe for instances that already hold data. |
Tip: Use Full Replace when standing up a brand-new instance that should mirror an existing one. Use Merge when you only want to bring a few new fields across without touching anything else.
4. Preview the Changes
Click Preview. The system compares the two instances live — without changing anything — and shows four counters:
Counter | Meaning |
Already matching | Fields that are identical on both sides. They are left untouched. |
To create | Fields that exist on the source but not on the target. They will be added. |
To alter (recreate) | Fields that exist on both sides but differ (type, length, or settings). They will be rebuilt to match the source. |
To remove | Fields on the target that the source does not have. Removed only in Full Replace mode. |
The preview also surfaces warnings — for example, a field about to be removed that is still used by a workflow or by Lead Conversion mapping — so you can review the impact before committing.
5. Run the Copy
1. Click Clone.
2. Read the confirmation message carefully. Full Replace warns you that fields missing from the source will be deleted along with their data.
3. Click Yes to queue the copy, or No to cancel.
The copy does not run instantly — it is queued and processed in the background within about 30 minutes. You can keep working; the job's progress appears in Recent Copy Jobs.
Important: If records were added to the target module after you previewed, the 10-record safety limit is re-checked when the job actually runs. A target that grew past the limit fails the job safely with an explanation instead of deleting data.
6. Track Your Copy Jobs
Every copy request appears in the Recent Copy Jobs table with its source, target, module, mode, status, and a one-line result summary. The table is searchable and paginated, so older jobs stay easy to find.
Status | Meaning |
pending | Queued and waiting for the next background run. |
running | Currently being applied to the target. |
completed | Finished successfully — the result column summarizes what changed. |
failed | Stopped safely — the result column explains why. |
Click the Details button on any row to see the full breakdown: which fields and sections were created or removed, which items were skipped and why, plus any warnings.
7. What Gets Copied
The copy reproduces the source module's setup as completely as possible:
Fields — every custom field, with its type, length, and settings such as Quick Create, Mass Edit, read-only, and hidden flags.
Sections (blocks) — including special Sub Module Reference sections, which are recreated as true sub-module sections on the target (only when the referenced sub-module exists there).
Layout order — fields keep their order within each section, and sections keep their order on the page.
Picklists — all values, including inactive ones, in the same order and with the same colors; role based visibility is copied too. Fields that follow a shared (global) picklist are linked to the same shared list on the target.
Reference fields — fields that pull a value from a related record are copied only when the referenced field also exists on the target; otherwise they are skipped with a note in the job details.
Duplicate Prevention — the module's duplicate-check fields and settings, including the webform duplicate options.
Field Dependencies — show/hide rules between fields, re-pointed at the target's own fields.
What is not copied: standard system fields are never deleted, and a few special field types cannot be recreated automatically — these appear under Skipped in the job details so nothing disappears silently.
8. Frequently Asked Questions
Q: Why is the copy blocked with a message about the record count? Full Replace deletes columns, which destroys any data stored in them. As a safety measure it only runs when the target module holds 10 or fewer records. Use Merge mode for instances that already contain data.
Q: Can I undo a completed Full Replace? No. Fields removed by a completed Full Replace are gone along with their data. If a job fails partway, the system automatically rolls back what it changed during that run. Always review the Preview and the confirmation message first.
Q: The module I need is not in the Module list. Why? The list only shows modules that exist and are active on both instances. Activate or create the module on the target first, then reload the page.
Q: How long does a copy take? Jobs are processed in the background within about 30 minutes of clicking Clone. Most modules finish in under a minute once the job starts.
Q: Is it safe to run the same copy twice? Yes. A repeat run finds everything already matching and makes no changes — the job details will show zero items created or removed.
Q: What happens to a section or field the target has but the source doesn't? In Full Replace it is removed (custom fields only — standard fields are kept and flagged with a warning). In Merge it is left untouched.
Q: Who can use this tool? Only super administrators ( sysadmin / admin ) signed in on the admin instance. For everyone else the menu entry is hidden and the page refuses access.
Need Help?
If you run into issues:
1. Open the job's Details window — failed jobs include the reason, and skipped items are listed with an explanation.
2. Re-run Preview to confirm both instances are reachable and the module is active on the target. 3. Contact Dazos support with the job number and result details, and reference CRM-3321.