Move AutoCAD Plotting Standards to BricsCAD: CTB, STB, DWG, Page Setup and PC3
BricsCAD reads DWG and supports familiar plotting concepts such as Layouts, Page Setups, CTB/STB and PC3, but a safe migration requires testing the parts that depend on product and operating system.
Beginner takeaway: Migrate the drawing standard first, then rebuild or validate environment-dependent printer configurations instead of assuming every AutoCAD plotting file is interchangeable.
What you need to understand first
The similarity between AutoCAD and BricsCAD makes migration fast, but it also creates overconfidence. DWG, CTB/STB and paper-space concepts transfer well; printer/PC3 deployment needs more care.
- BricsCAD is built around DWG workflows and familiar plotting concepts.
- BricsCAD supports CTB/STB plot styles.
- BricsCAD PC3 behavior differs from AutoCAD, and macOS/Linux physical printing is PDF-first.
Related guides: BricsCAD Printing & Plotting Guide, BricsCAD PC3 Files Explained: Important Differences for AutoCAD Users, and CTB vs STB for CAD Standards: Which Should You Use?.
Step-by-step workflow
Step 1 — Inventory AutoCAD standard
Where: Templates, CTB/STB, Page Setups, PC3, paper sizes
Do this: List what the office actually depends on.
Check: Migration scope is visible.
Step 2 — Open representative DWGs
Where: BricsCAD
Do this: Check Layouts, title blocks, viewport scales and plot-style model.
Check: Drawing-level behavior is intact.
Step 3 — Install plot styles
Where: BricsCAD PlotStyles path
Do this: Deploy CTB/STB and verify calibration sheet.
Check: Lineweight/color standard transfers correctly.
Step 4 — Rebuild/test output configs
Where: BricsCAD Page Setup/PC3 by platform
Do this: Map Windows printers or PDF-first macOS/Linux workflow.
Check: No AutoCAD-only PC3 assumption remains.
Step 5 — Pilot issue set
Where: Small real project
Do this: Publish/print several sheet types and compare with known-good AutoCAD output.
Check: Migration is accepted before broad rollout.
What usually goes wrong
| What you see | Likely layer | First check |
|---|---|---|
| DWG opens but PC3 missing | Environment-dependent config | Recreate/map BricsCAD output path. |
| CTB not visible | PlotStyles path | Deploy to BricsCAD path. |
| Mac/Linux physical printer absent | Platform difference | Use PDF-first workflow. |
| Lineweights differ | Style/device calibration | Compare same test sheet. |
Practical example
A company migrates a DWT containing A1/A3 Page Setups and a monochrome CTB. Keep the title blocks, Layouts and CTB logic, but build/test BricsCAD output configurations per platform. The goal is equivalent issued sheets, not identical internal configuration files.
What not to do
- Do not call the migration complete because the DWG opens without errors.
- Do not copy AutoCAD PC3 files blindly into every BricsCAD platform.
- Do not recalibrate CTB values until the same PDF is compared through both products.
Good office standard
Maintain a migration test matrix: DWG/Layout, CTB/STB, paper sizes, Page Setup, PDF, physical plotter and platform. Sign off the output, not just the file opening.
Quick verification before you move on
- Use one representative drawing or sheet, not a production batch.
- Verify page size, orientation and a known dimension.
- Compare Preview/PDF with the physical output when a printer is involved.
- Save the setting or set only after the result is repeatable.
Official references
Frequently asked questions
What usually transfers most easily?
DWG/Layout concepts and CTB/STB plotting logic are highly familiar, but always verify real output.
What needs the most caution?
PC3/device deployment and cross-platform physical printing.
Should I compare PDFs or only hardcopy?
Compare both. PDF isolates CAD output; hardcopy verifies the downstream device path.
Explore more in BricsCAD Printing & Plotting Guide.